Comments (2)
I like the Atomic approach 👍
from rippled.
This kind of problem, unfortunately, has existed for a while with other features where the owner directory has to be empty. Fortunately, people haven't seemed to be too interested in doing it, I think partly because the reserve requirements can get expensive pretty quickly.
A problem with only checking the balance of a trust line is that it may not be sufficient. I think we'd also need to check the limit, because the limit is saying that the user already trusts the issuer for that amount, and changing parameters when trust has already been extended is not great. But if the limit is zero, then the only way to have a non-default trust line is with flags or quality, and what does that say about the user creating the trust line?
Another possible solution is the proposed Atomic
transaction. One could fund the issuing account, then set all the flags in one atomic transaction. That would solve this entire class of problems.
Clearly the documentation needs to be updated, regardless of how this is addressed.
from rippled.
Related Issues (20)
- Cannot determine which is the AMM Pool on the trustline between the AMM Pool and the token issuer. HOT 6
- temREDUNDANT when swapping Gatehub USD with Bistamp USD (Version: 2.1.1) HOT 8
- [Node stopped syncing after reset] (Version: [2.1.1])
- [get_aggregate_price] with malformed oracle_document_id value returns different error on Clio compared to rippled.
- Raise test coverage of AMM to 100%
- `NFTokenOffers` Vector256 is not mapped directly to a specific Hash256
- Feature: API for AMM trade price
- [ledger_entry of oracle with non numeric input of oracle_document_id do not return an error] (Version: ["2.2.0-b2"]) HOT 6
- Negative LPTokenValue following AMMWithdraw transaction HOT 1
- Compilation error in STAmount.cpp: expected nested-name-specifier before 'enum HOT 1
- ./rippled --unittest failed output HOT 4
- Peer crawler port field type inconsistency HOT 1
- [XRP EscrowCreate] (Version: [2.1.1]) HOT 1
- Sometimes, after a service restart, my full history Ripple server shows an incorrect complete ledger range. Version: 2.2.0-b3
- Invalid "success" response from book_changes (possible race condition)
- book_changes API method doesn't follow standard ledger selection rules
- book_changes is missing `"validated": true` field in JSON-RPC response
- book_changes takes a long time querying full-history servers
- Add SHAMap to libxrpl
- Feature request: Object transaction history RPC
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from rippled.