The rgb-core from rgb-wg

Before introduction of simplicity some specific complex forms of validation (like zk-validation for confidential amounts ensuring that the sum of inputs is always equal to the sum of outputs) is made with embedded rust procedures, which are the part of this library. However, to cover all initial schemata functionality we need to implement more (this is an incomplete list):

Fungible assets
- Primary issuance
- Asset transfer
- Secondary issuance
- Burn verification for asset burning
- Replacement (re-issuance after burn)
- On-chain bitcoin lock verification (for decentralized issuance)
Non-fungible assets
- Primary issuance
- Asset transfer
  ...
Reputation
...
Audit logs
...

Data Container implementation and related updates

https://github.com/rgb-org/rgb-core/blob/4e29b8082c0a69cc906fa8d4f604f2980dad17f5/rgb20/src/schema.rs#L137

https://github.com/rgb-org/rgb-core/blob/4e29b8082c0a69cc906fa8d4f604f2980dad17f5/rgb20/src/schema.rs#L307

https://github.com/rgb-org/rgb-core/blob/4e29b8082c0a69cc906fa8d4f604f2980dad17f5/rgb20/src/schema.rs#L364-L367

https://github.com/rgb-org/rgb-core/blob/4e29b8082c0a69cc906fa8d4f604f2980dad17f5/rgb20/src/schema.rs#L511

https://github.com/rgb-org/rgb-core/blob/4e29b8082c0a69cc906fa8d4f604f2980dad17f5/rgb21/src/schema.rs#L241

https://github.com/rgb-org/rgb-core/blob/4e29b8082c0a69cc906fa8d4f604f2980dad17f5/rgb21/src/schema.rs#L245

https://github.com/rgb-org/rgb-core/blob/4e29b8082c0a69cc906fa8d4f604f2980dad17f5/rgb21/src/schema.rs#L278

https://github.com/rgb-org/rgb-core/blob/4e29b8082c0a69cc906fa8d4f604f2980dad17f5/rgb21/src/schema.rs#L291-L292

https://github.com/rgb-org/rgb-core/blob/4e29b8082c0a69cc906fa8d4f604f2980dad17f5/src/schema/state.rs#L111

https://github.com/rgb-org/rgb-core/blob/4e29b8082c0a69cc906fa8d4f604f2980dad17f5/rgb22/src/schema.rs#L63

https://github.com/rgb-org/rgb-core/blob/4e29b8082c0a69cc906fa8d4f604f2980dad17f5/rgb23/src/schema.rs#L59

https://github.com/rgb-org/rgb-core/blob/4e29b8082c0a69cc906fa8d4f604f2980dad17f5/rgb23/src/schema.rs#L63-L64

https://github.com/rgb-org/rgb-core/blob/4e29b8082c0a69cc906fa8d4f604f2980dad17f5/rgb24/src/schema.rs#L74

Add suppoert for Renomination, Burn and Replacement in Asset

https://github.com/rgb-org/rgb-core/blob/4e29b8082c0a69cc906fa8d4f604f2980dad17f5/rgb20/src/asset.rs#L48

Implement RGB disclosure procedure

Upgrade with Simplicity Support

https://github.com/rgb-org/rgb-core/blob/4e29b8082c0a69cc906fa8d4f604f2980dad17f5/src/schema/schema.rs#L132

Refactor multimessage commitments

https://github.com/rgb-org/rgb-core/blob/4e29b8082c0a69cc906fa8d4f604f2980dad17f5/src/stash/anchor.rs#L357

Implement default bech32 serde encoding for id types

with

#[wrapper(FromStr)]
pub struct NodeId(
    #[serde(with = "bech32::serde")]
    sha256t::Hash<NodeIdTag>
);

This will be a breaking change for RGB Node

Use BtreeSet for MetaData

https://github.com/rgb-org/rgb-core/blob/4e29b8082c0a69cc906fa8d4f604f2980dad17f5/src/contract/metadata.rs#L28-L31

Support for 128-bit Pedersen commitments and bulletproofs

This requires changes to Pedersen and bulletproofs implementations, so clearly an upstream dependency.

256-bits can't be supported, since Secp256k1 curve has less than 2^256 points. This can be done only with an option of failing to commit to the top of 256-bit unint range.

https://github.com/LNP-BP/rust-lnpbp/blob/6010402f8e49fd05ad23f8c0e93ffe079d33d378/src/rgb/schema/state.rs#L853-L855

https://github.com/LNP-BP/rust-lnpbp/blob/6010402f8e49fd05ad23f8c0e93ffe079d33d378/src/rgb/schema/state.rs#L891-L900

Upodate data formats in RGB24

https://github.com/rgb-org/rgb-core/blob/4e29b8082c0a69cc906fa8d4f604f2980dad17f5/rgb24/src/schema.rs#L66

https://github.com/rgb-org/rgb-core/blob/4e29b8082c0a69cc906fa8d4f604f2980dad17f5/rgb24/src/schema.rs#L85

Refactor witness input validation

https://github.com/rgb-org/rgb-core/blob/4e29b8082c0a69cc906fa8d4f604f2980dad17f5/src/validation.rs#L648

Upgrade strict encoding of consignment data to support more than 2^16 operations in the history

https://github.com/rgb-org/rgb-core/blob/4e29b8082c0a69cc906fa8d4f604f2980dad17f5/src/stash/consignment.rs#L35-L39

Asset state transition node ID mutability

During my tests and investigation of RGB node's internals, I have noticed a particular behavior that does not seem to be there by design but rather to be an undesirable side effect: the fact that the node ID of an asset state transition data structure will mutate as its internal assignments are concealed/revealed.

As observed, the aforementioned behavior contributes for some data inconsistencies, one of which has already ben reported as an issue (#130) and for which a pull request (#131) with a proposed fix has already been opened. Another one of such data inconsistencies is described below.

During the accept phase of an asset transfer operation, the state transition added to the receiving RGB node's stash has a node ID (which is shown as its filename) different from the node ID of the new entry added to the known_allocations field of the asset data structure maintained in the RGB node's cache (which can be retrieved by means of the fungible list -l command), even though they refer to the same asset state transition.

This particular data inconsistency is due to the fact that the asset state transition extracted from the consignment data structure has the seal of the assignment used to allocate the transferred assets to the receiving endpoint revealed before the state transition is added to the stash. In contrast, the original state transition (with the concealed seal) is used when adding the new asset allocation to the asset data structured maintained in the cache.

That same misbehavior seems to apply to asset state extensions, even though there are no evidences to confirm it as that functionality does not seem to be fully implemented.

rust-bitcoin/rust-secp256k1#237 Add bip340 schnorr

https://github.com/rgb-org/rgb-core/blob/4e29b8082c0a69cc906fa8d4f604f2980dad17f5/src/contract/data.rs#L112

https://github.com/rgb-org/rgb-core/blob/4e29b8082c0a69cc906fa8d4f604f2980dad17f5/src/schema/state.rs#L140-L141

https://github.com/rgb-org/rgb-core/blob/4e29b8082c0a69cc906fa8d4f604f2980dad17f5/src/schema/state.rs#L167-L168

https://github.com/rgb-org/rgb-core/blob/4e29b8082c0a69cc906fa8d4f604f2980dad17f5/src/schema/types.rs#L109-L110

https://github.com/rgb-org/rgb-core/blob/4e29b8082c0a69cc906fa8d4f604f2980dad17f5/rgb21/src/schema.rs#L278

https://github.com/rgb-org/rgb-core/blob/4e29b8082c0a69cc906fa8d4f604f2980dad17f5/rgb21/src/schema.rs#L291-L292

Implement Display via YAML for validation Status

https://github.com/rgb-org/rgb-core/blob/4e29b8082c0a69cc906fa8d4f604f2980dad17f5/src/validation.rs#L45

Use secp256k1-zkp for bulletproofs & Pedersen commitments

Tracking PRs:

get it merged
do rust bindings
get new version released to crates.io

OUTDATED:

~~Using BlockstreamResearch/secp256k1-zkp#23~~

Comment by Nickler from #secp256k1": what this PR doesn't include yet is a great way to import/export circuits and assignments. For purify I didn't do this very methodically either (https://github.com/sipa/purify/pull/2/files#diff-95a4fca4441ac563d430a430c9b3b07aR410).

Add support for 128 and 256 bit data in RGB Schema and Contracts

Once rust-bitcoin will have u128 native support – or, alternatively, using bitcoin bigint (from bitcoin_num crate)

Locations:

https://github.com/LNP-BP/rust-lnpbp/blob/6010402f8e49fd05ad23f8c0e93ffe079d33d378/src/rgb/schema/types.rs#L93-L95

https://github.com/LNP-BP/rust-lnpbp/blob/6010402f8e49fd05ad23f8c0e93ffe079d33d378/src/rgb/schema/state.rs#L105-L108

https://github.com/LNP-BP/rust-lnpbp/blob/6010402f8e49fd05ad23f8c0e93ffe079d33d378/src/rgb/schema/state.rs#L128-L133

https://github.com/LNP-BP/rust-lnpbp/blob/6010402f8e49fd05ad23f8c0e93ffe079d33d378/src/rgb/contract/data.rs#L52-L61

Verify that contract node script parameters match schema requirements

MIME type implementation in all schemas

https://github.com/rgb-org/rgb-core/blob/4e29b8082c0a69cc906fa8d4f604f2980dad17f5/rgb21/src/schema.rs#L250

https://github.com/rgb-org/rgb-core/blob/4e29b8082c0a69cc906fa8d4f604f2980dad17f5/src/schema/mod.rs#L83

https://github.com/rgb-org/rgb-core/blob/2a9f61c69c25b2f93e6961e3317b340c452c68ac/rgb22/src/schema.rs#L60

https://github.com/rgb-org/rgb-core/blob/4e29b8082c0a69cc906fa8d4f604f2980dad17f5/rgb23/src/schema.rs#L61

https://github.com/rgb-org/rgb-core/blob/4e29b8082c0a69cc906fa8d4f604f2980dad17f5/src/validation.rs#L257

 Finished dev [unoptimized + debuginfo] target(s) in 6.83s
+ cargo check --verbose --features=lnp --all-targets
error: Package `rgb-core v0.4.0-beta (/home/raj/github-repo/rgb-core)` does not have the feature `lnp`

// TODO: Add contracts and state transition proprietary keys

Alternative approach: #74

rgb-wg / rgb-core Goto Github PK

rgb-core's Introduction

RGB Core Library

Contributing

License

rgb-core's People

Contributors

Stargazers

Watchers

Forkers

rgb-core's Issues

Recommend Projects

Recommend Topics

Recommend Org