cardano-wallet VS rippled

It's definitely possible to pass this cost on to the buyer, I would personally start by getting the cardano-wallet stack running. If you're familiar with docker/docker-compose this is quite easy: https://github.com/input-output-hk/cardano-wallet/blob/master/docker-compose.yml

pkgname=cardano-wallet _version=2021-09-09 pkgver=20210909 pkgrel=1 pkgdesc='HTTP server & command-line for managing UTxOs and HD wallets in Cardano.' license=('Apache') arch=('any') url='https://github.com/input-output-hk/cardano-wallet' makedepends=('cabal-install-bin' 'ghc') source=("https://github.com/input-output-hk/${pkgname}/archive/v${_version}.zip") sha256sums=('868247f4a628d0d53ebfcd11bb0969ac2f22aa5579349484b1f3907497d11200')

It's not so bad. I wrote an IRC tipping bot for Cardano, was thinking it's gonna be extremely complicated, because I don't know any haskell, but it was actually pretty easy. Low level tools like cardano-cli and cardano-wallet allows you to build pretty much anything around them and all you need is to parse JSON and process HTTP requests, but it has its catches - for e-commerce I think biggest issue right now is inability to generate "unlimited" amount of receiving addresses via cardano-wallet - https://github.com/input-output-hk/cardano-wallet/issues/2921 it could be worked out by using transaction metadata, but then that's something that most wallets doesn't support right now.

I've looked at cardano-wallet but I think it's for only making transactions that are made on your server?(sorry if this isn't correct). Is there a service where they can take the address of one wallet and send to another wallet that wasn't made on your server? Or is that what the new smart contract roll outs are for? Thanks

Bitcoin (BTC) - https://github.com/bitcoin/bitcoin/pulse/monthly Ethereum (ETH) - https://github.com/ethereum/go-ethereum/pulse/monthly Stellar (XLM) - https://github.com/stellar/stellar-core/pulse Cardano NODE (ADA) https://github.com/input-output-hk/cardano-node/pulse/monthly Cardano WALLET https://github.com/input-output-hk/cardano-wallet/pulse/monthly DogeCoin (DOGE) https://github.com/dogecoin/dogecoin/pulse/monthly XRP (XRP) https://github.com/ripple/rippled/pulse/monthly Litecoin (LTC) https://github.com/litecoin-project/litecoin/pulse/monthly Chainlink (LINK) https://github.com/smartcontractkit/chainlink/pulse/monthly Solana (SOL) - https://github.com/solana-labs/solana/pulse/monthly

You can have a look at their compose setup for inspiration: https://github.com/input-output-hk/cardano-wallet/blob/master/docker-compose.yml

The bug occurred when a multi-path payment interacted with an AMM synthetic offer, and the synthetic offer required to fulfill the payment exceeded the AMM pool size. In this case, the payment engine attempted to use the single-path strategy to back-out the maximum liquidity available to swap against the pool. Although this condition was properly detected, there was an error on how the payment engine resized the synthetic offer to consume liquidity only up to the AMM size. Instead of using the actual swap rate, which represents the cost of fully swapping one side of an AMM pool, the new synthetic offer’s exchange rate was incorrectly set to the spot exchange rate of the AMM (that is, the rate it takes to execute an infinitesimally sized order). Consequently, an AMM operation that should have been expensive became relatively cheap, effectively violating the constant-product invariant of the pool. In this state, another user could deposit funds into the drained side of the pool, generating a large number of LP tokens and taking ownership of the pool. Now that the fix amendment is active, the team has opened a PR with a unit test demonstrating this behavior.

Explore the XRPL Developers Discord, the XRP Ledger Learning Portal, and the extensive documentation available on XRPL.org. You can also participate in XRPL Community Events and Hackathons to engage with like-minded individuals and stay abreast of the latest developments in the XRPL ecosystem.

fixDisallowIncomingV1: Fixes an issue that occurs with authorized trustlines and the “lsfDisallowIncomingTrustline” flag.

It’s good news for the builders who have been working round the clock. Tools such as AI chatbots will enable developers to quickly receive answers to their queries, speeding up the process from concept to application. AI Chatbots have already become a part of RippleX’s commitment to making blockchain development on the XRP Ledger more accessible and less time-consuming, especially for those new to the field. This approach will not only foster increased innovation on blockchains but could also enhance financial inclusion, making tools more accessible globally.

Currently Rippled 2.0.0 is scheduled to release December 18th, 2023: https://github.com/XRPLF/rippled/milestone/8

The XRPL Accelerator, a program dedicated to nurturing innovation and development on the XRP Ledger, is back with its second cohort of groundbreaking projects. After the success of the inaugural cohort, the Accelerator continues to support entrepreneurs and builders looking to scale their projects on the XRP Ledger.

The third annual Apex Developer Summit was the biggest yet. Held in collaboration with the XRP Ledger Foundation, this event brought together an impressive gathering of over 400 blockchain developers, validators, and XRPL community members in the heart of Amsterdam at the Leonardo Royal Hotel.

Explore the XRPL Developers Discord, the XRP Ledger Learning Portal, and the extensive documentation available on xrpl.org. You can also participate in XRPL Community Events and Hackathons to engage with like-minded individuals and stay abreast of the latest developments in the XRPL ecosystem.

As developers and contributors to the decentralized, open-source XRP Ledger (XRPL), the RippleX engineering team is excited to announce a major breakthrough in the XRPL ecosystem that will revolutionize the way developers build decentralized applications (dApps).