lnp-bp/nodes

Complete LNP/BP protocol daemons suite

LNP/BP nodes integration

The repo provides integration packages for LNP/BP node suit, which includes

• BP Node,
• LNP Node,
• RGB Node,
• Storm Node, and
• Store Service, which usually shipped separately from the Storm node.

Installing all nodes locally:

rustup update nightly
cargo +nightly install lnpbp_nodes -Z bindeps

Installing just command-line tools:

rustup update nightly
cargo +nightly install lnpbp-cli -Z bindeps

Using RPC API in another project Cargo.toml:

[dependecies]
lnpbp_rpc = "0.8.0"

Integration architecture

nodes's Issues

Error: FundingWallet(Electrum("Connection refused (os error 111)"))

After I run the command: lnpd -vvv --network testnet init, while I have gave the two testnet addresses some coins, I get the error:

Funding wallet 'funding.wallet' ... found
[2022-11-28T15:00:11Z INFO lnp_node::lnpd::funding] Opening funding wallet at '/home/rgbalice/.lnp_node/testnet/funding.wallet'
[2022-11-28T15:00:11Z INFO lnp_node::lnpd::funding] Connecting Electrum server at pandora.network:60001
Error: FundingWallet(Electrum("Connection refused (os error 111)"))

Unable to run RGB Demo

Hi,

I tried installing the latest packages as mentioned in the demo-rgb.sh, however I get this error while trying to use the installed CLI.

'rgb20 binary not found: Os { code: 2, kind: NotFound, message: "No such file or directory" }'

Can you help me understand why this is happening? I can see the binaries under /.cargo/bin but maybe it's not installed correctly?

Thank you

payload data are not strictly encoded

Following the steps I stuck in the registration step of a contract.

I have the command:
rgb-cli -n testnet contract register rgbc1qxz4y02gr3q3flnxvuh6ufyczx9ngcsk3vzd9fstcjzr8cggyyvvydfps3c85z6exq0xz3ess5jgffqta9pqc5dc70qv9slnlj53g2mdgjc9qsgyrvduzhcs0ugpr4mekwac5g8v9neum7lmm6dhn7cshux9s68fjjhhxm58x3srpxzgw7u4jgyjrzz26gedstdrx3kqfymdttkt90sptqs3gkuucdd2c2g9qf572ag9q7cs9qgj6q22re74egafx9ljzsmtsrh3wdqwdg96625dg9rdlfunljqpq085q3k8af22vszlyg42zwwtana0442pp5rh5cuq8qd4zna04pvf3tmge6qv5wdrj9nx94wecst52yjv9zn3rs3hc4wycsm7s9j7m7xe99hrlnapw4lwwn6semrqwh4d0hxfena0pa7ln8jd8akx55nne6ek0n5da7kf7q8u6ta79c0al7lnmyaz3hj7nx0junmul94llk9gr93fkrats0ryh3unrk8tck2mt4jk43vqdnk5hadxaqrdhtq7dq6g9g2jaejt47gk6g4vsn46kfx5639g0yvenue7hfvrhfpe3zks435z08vntu0vlx43v6kndcxaafyjwmt0n99nxw0wwjy6y9vrgdm4gkcasj35dgup0am38ykc4j2cgddk07tdl0ymkjd8487dscnmg7vlrlv9gl7jlx6wh5rjka7lm7sf0l9087wtq7nxhv3hdnrz2l2hx3hy39c

Which gives as result:

error: Invalid value "rgbc1qxz4y02gr3q3flnxvuh6ufyczx9ngcsk3vzd9fstcjzr8cggyyvvydfps3c85z6exq0xz3ess5jgffqta9pqc5dc70qv9slnlj53g2mdgjc9qsgyrvduzhcs0ugpr4mekwac5g8v9neum7lmm6dhn7cshux9s68fjjhhxm58x3srpxzgw7u4jgyjrzz26gedstdrx3kqfymdttkt90sptqs3gkuucdd2c2g9qf572ag9q7cs9qgj6q22re74egafx9ljzsmtsrh3wdqwdg96625dg9rdlfunljqpq085q3k8af22vszlyg42zwwtana0442pp5rh5cuq8qd4zna04pvf3tmge6qv5wdrj9nx94wecst52yjv9zn3rs3hc4wycsm7s9j7m7xe99hrlnapw4lwwn6semrqwh4d0hxfena0pa7ln8jd8akx55nne6ek0n5da7kf7q8u6ta79c0al7lnmyaz3hj7nx0junmul94llk9gr93fkrats0ryh3unrk8tck2mt4jk43vqdnk5hadxaqrdhtq7dq6g9g2jaejt47gk6g4vsn46kfx5639g0yvenue7hfvrhfpe3zks435z08vntu0vlx43v6kndcxaafyjwmt0n99nxw0wwjy6y9vrgdm4gkcasj35dgup0am38ykc4j2cgddk07tdl0ymkjd8487dscnmg7vlrlv9gl7jlx6wh5rjka7lm7sf0l9087wtq7nxhv3hdnrz2l2hx3hy39c" for '': payload data are not strictly encoded - An unsupported value TypeRef for enum TypeRef encountered during decode operation

Any idea what goes wrong here?

Broadcasted witness tx has different txId than the one specified as anchor in consignment.

Hello, I have an issue when following the demo-rgb.sh.

When I finish creating the consignment, with the transfer finalized by executing:
rgb-cli -n testnet transfer finalize --endseal ${TXOB} ${PSBT} ${CONSIGNMENT}
And then I sign and finalize the transaction:

btc-hot sign ${PSBT} ${DIR}/testnet
btc-cold finalize --publish testnet ${PSBT}

The resulting txId is different than the one specified in consignment, so the consignment never validates. Any idea why that might be the case?

Tx is broadcasted and mined on testnet here: https://blockstream.info/testnet/tx/6796b0ef9cd3128c43159081dd6bf11ff1afe474bb6bf3e96aa33b038f5af6b0
+ attaching the consignment, transfer, and psbt in a zip file. rgb-tx.zip

Looking forward to your reply!

Vec OutpointValue is not an iterator

Trying to make use of the contrub/install.sh The following warning comes by:

Compiling rgb20 v0.8.0-rc.4
error[E0599]: Vec<OutpointValue> is not an iterator
--> /home/rgbalice/.cargo/registry/src/github.com-1ecc6299db9ec823/rgb20-0.8.0-rc.4/src/create.rs:63:41
|
63 | let issued_supply = allocations.sum();
| ^^^ Vec<OutpointValue> is not an iterator; try calling .into_iter() or .iter()
|
= note: the following trait bounds were not satisfied:
Vec<OutpointValue>: Iterator
which is required by &mut Vec<OutpointValue>: Iterator
[OutpointValue]: Iterator
which is required by &mut [OutpointValue]: Iterator

error[E0599]: no method named into_assignments found for struct BTreeMap in the current scope
--> /home/rgbalice/.cargo/registry/src/github.com-1ecc6299db9ec823/rgb20-0.8.0-rc.4/src/create.rs:81:27
|
81 | inflation.into_assignments(),
| ^^^^^^^^^^^^^^^^ method not found in BTreeMap<OutPoint, u64>

For more information about this error, try rustc --explain E0599.
error: could not compile rgb20 due to 2 previous errors
error: failed to compile rgb20 v0.8.0-rc.4, intermediate artifacts can be found at /tmp/cargo-install8qHU5P
Downloaded bp-cli v0.8.0-alpha.2

an argument of type `std::option::Option<Reveal>` is missing

A second warning comes by after running ./install.sh
Compiling rgb-cli v0.8.0-rc.1
error[E0061]: this function takes 4 arguments but 3 arguments were supplied
--> /home/rgbalice/.cargo/registry/src/github.com-1ecc6299db9ec823/rgb-cli-0.8.0-rc.1/src/command.rs:279:41
|
279 | let status = client.consume_transfer(consignment, force, progress)?;
| ^^^^^^^^^^^^^^^^ -------- an argument of type std::option::Option<Reveal> is missing
|
note: associated function defined here
--> /home/rgbalice/.cargo/registry/src/github.com-1ecc6299db9ec823/rgb_rpc-0.8.1/src/client.rs:260:12
|
260 | pub fn consume_transfer(
| ^^^^^^^^^^^^^^^^
help: provide the argument
|
279 | let status = client.consume_transfer(consignment, force, /* std::option::Option */, progress)?;
| ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

For more information about this error, try rustc --explain E0061.
error: could not compile rgb-cli due to previous error
error: failed to compile rgb-cli v0.8.0-rc.1, intermediate artifacts can be found at /tmp/cargo-install6AIY4I
Downloaded storm-cli v0.8.0

error: could not find `lnpbp_nodes` in registry `crates-io` with version `*`

Doing:
cd repos
git clone https://github.com/LNP-BP/nodes.git
rustup update nightly
cargo +nightly install lnpbp_nodes -Z bindeps

Gives the error:
error: could not find lnpbp_nodes in registry crates-io with version *

Update nodes in install script to 0.9

The nodes in the install script, found here, are all using 0.8, which is out of date:

https://github.com/LNP-BP/nodes/blob/master/contrib/install.sh

Also, maybe a note should be added to the README as a reminder to update the install script on new RGB node releases. It doesn't need to be done on patch releases necessarily, but definitely when we go up a minor version.

@dr-orlovsky Not sure if I have access to do so, please tag this as "good first issue" and maybe someone in the RGB community can step up and take care of that for us 😸

Example for transfer accept

Currently in the demo script, the BLINDING factor on the other machine isn't used, nor is any form of accept transfer command is called (on the other machine). It would help to have an example of how this is done.