Comments (6)
This information can be pruned since we deterministicaly know this transaction id as transaction spending one of outputs containing the asset, i.e given the whole proofs history and original issuing contract this can be reconstructed from the blockchain information
from spec.
Related: #102
from spec.
Ok, but in the case of multiple consecutive based UTXO-based transfers, say from some_vout
-> utxo_1
-> utxo_2
the proof for some_vout
-> utxo_1
is committed too in the transaction spending some_vout
, which is retrievable from the blockchain info if some_vout
is known. This proof only shows utxo_1
in its serialised form, which is not sufficient to retrieve it on chain.
Then the proof for utxo_1
-> utxo_2
will be committed to in the transaction spending utxo_1
. But if commitment_txid
is pruned from the proof at a later point, this transaction can no longer be inferred from the proof history and the commitment cannot be verified, since utxo_1
is entirely separated on chain from both some_vout
and utxo_2
and only associated in the RGB proof.
If all subsequent commitment_txid
s are pruned as well, then none of the subsequent commitments may be found either since the chain of spending can not be inferred.
from spec.
No, this works differently.
Initially, you have an issuing contract, defining the UTXO containing the issued assets. You know that UTXO. And when the UTXO is spend, you know that from Bitcoin blockchain β as well as you know the transaction which spends it. This transaction contains the commitment to the proof, and the proof points next UTXO(s) holding assets βΒ and so on and on. There is no need to storing commitment_txid at all! It's just a performance booster for Bitcoin Core index.
from spec.
Please check this image for the details: https://raw.githubusercontent.com/rgb-org/spec/rgb-0.5/assets/rgb_overview.png
from spec.
Copying here my explanations from Slack for some future references:
It's important to have a right intuition on how you look to the system. Its not proofs referencing transactions or previous proofs, it is transactions referencing proofs in a very indirect way.
So blockchain is the primary source on the structure of proofs DAG. Each asset is assigned to some TxOut. Transaction spending this TxOut must contain the commitment to the proof showing where the assets will go next (to which TxOut) - and this constitutes the links between proofs. Proofs are not directly reference previous proofs, inputs or commitment transactions, since it is not necessary. Proofs only reference TxOuts holding asset assignments.
In order to validate a proof you need to be provided with a complete proof history up to an issuance contract - and then you start validation process from the root (issuance) to the proof you are validating.
So, if Alice wats to send Bob some assets and Bob wants to pay Alice for the assets some bitcoins,
- Alice provides Bob with the full proof history up to the issuance contract with a new draft proof
- Bob validates the history and creates a new tx and a new proof, where tx (a) spends some outputs from the last proof provided by Alice, (b) contains acommitment to the new proof, and (c) the proof assigns assets to some outputs of the new transaction - or some other(s) UTXO(s) owned by Bob
- Bob provides Alice with both unpublished tx and the proof
- If Alice ok she signs the tx and publishes it to bitcoin network
This gives necessary atomicity and escrow guarantees.
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
- 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.