elements icon indicating copy to clipboard operation
elements copied to clipboard

Open Source implementation of advanced blockchain features extending the Bitcoin protocol

Results 161 elements issues
Sort by recently updated
recently updated
newest added

Currently (tested in 0.18.1.9 and 0.18.11): If I set `chain=whatever`, `con_has_parent_chain=0` or `parentgenesisblockhash=Null` in elements.conf I can still call getpeginaddress from a connected client without error and get a `mainchain_address`...

Version 0.18.1.9 As I understand it the fallbackfee that is set within code is actually ignored (inherited from Bitcoin Core). I think this was done to avoid users getting txs...

Instead of RPC_VERIFY_ERROR when the block is already in the chain. Fixes https://github.com/ElementsProject/elements/issues/927.

Pass in a ValidationState object to CheckProof and friends, so that we can provide helpful error messages when validation fails. @stevenroose This came out of the time I spent figuring...

elements 0.18.1.9 rawissueasset doesn't allow asset_amount of zero: ``` Invalid parameter, asset_amount must be positive ``` Whereas this is ok using `issueasset`. If you use `issueasset 0 1` you get...

There is some discussion about this in various places (#935, #964), but I wanted to make a dedicated issue to propose things I'm running into while reviewing merges in #935....

Currently for explicit outputs gettransaction shows this: ```     "details": [         {             "category": "generate",             "amount": 0.00104720,             "amountblinder": "0000000000000000000000000000000000000000000000000000000000000000",             "asset": "0a8e7509f0ab8b750909e378b51af66158464430b88d8efb0627b0b6226f91ea",             "assetblinder": "0000000000000000000000000000000000000000000000000000000000000000",             "vout": 0         } ``` It's probably better to just...

This document describes: * A brief history of Elements asset contracts * A new format for user-supplied asset contracts, based on the RFC 7049 CBOR standard * Some other tools...

test_bitcoin and bench bitcoin should be named test_elements and bench_elements (or similar) to avoid potential conflict

In the elements tutorial covering block signing in a strong federation (i.e. not using generate to create blocks) it uses a 1of1 block signing model and disables dynafed using `con_dyna_deploy_start=9999999999999`....