Comments (6)
Seems like I found an answer: for some contract blueprints (like Crowdsale) there might be multiple type of assets issued under the same contract. Thus, asset id field is required. However, in this case, it is unclear from the spec how different asset ids are assigned and supported.
from spec.
The send to utxo feature enables to send different asset types to a utxo
from spec.
@giacomozucco can you pls confirm my understanding of the issue?
from spec.
Yes, I can confirm:
- as you said, a single contract could be used to issue multiple asset types,
- as @inaltoasinistra said, a single UTXO could receive different asset types.
Furthermore, there are some (still very speculative) ideas to improve privacy and compactability of proves in multi-asset scenarios, by aggregating the parts of the proof which are not strictly needed to verify the absence of double-spending on one specific asset (for example the proofs about other unrelated assets) in a MMR-like structure. In general, I would say the triplets are not redundant.
from spec.
How different assets issued by under the same RGB contract should be identified? It's clearly not the hash of the contract itself (since it is constant), and there are no fields in the issuance contract to identify the issued assets
from spec.
Replaced by #85
from spec.
Related Issues (20)
- Proofs must be commited only to the TX spending colored UTXO, not the arbitrary one
- Possible double-spend with double-commitment HOT 12
- Improve spec on contract deployment HOT 2
- Depreciate OP_RETURN commitments for contract deployments
- Improve single use seals mechanism for contract reissuing HOT 1
- Preserve some space in proofs by using RIPMD160 hashes HOT 1
- Can commitment_txid be pruned in UTXO-based transfers? HOT 6
- Inflation txout naming HOT 1
- Version upgrade proofs must spend only inputs with the same version number
- Add reference and link to LNPBP repo? HOT 3
- https://rgb.network is down / not resolving HOT 4
- Why we use addition instead of multiplication in public key tweaking HOT 10
- Nested proof structure results in very large proofs for transfers with multiple inputs HOT 4
- How to deterministically define output containing the tweaked key for P2C schemes HOT 12
- Increasing asset safety by combining commitment output with asset binding output HOT 6
- No support for spending single RGB output from the proof HOT 2
- Proposed Spectrum tx structure HOT 3
- Add versioning to RGB protocol
- Update proof structure separating commitment and prunable parts
- Do we need to verify that P2C commitment tx is not older than asset-binding tx? HOT 1
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 spec.