trezor-firmware

Commit Graph

Author	SHA1	Message	Date
grdddj	3e11e8bba2	chore(tests): update Bitcoin test cases to use valid prevtxes	3 years ago
JoeGruff	e3ea32a986	multi: Add decred staking. Add two new input and four output script types. Decred ticket purchases consist of a stake submission, op returns, and change addresses. Although change addresses are allowed by consensus, they are no longer used in practice and so have been given the restrictions of a null pubkey and no value. Stake scripts are almost identical to p2pkh or p2sh except for an extra opcode in front. Inputs are currently only used in the form of one input three outputs with the first output, or stake submission, paying to a public key hash, or with two inputs and five outputs with the stake submission paying to a multisig script hash. The op returns are directed to the user in the case of one and the voting service provider and user in the case of two. One of the sstx commitment for a ticket must pay back to the trezor wallet. This is checked and an error is thrown if we don't find the expected public key hash. Because this adds the ability to create new types of outputs once the ticket votes, two new input script types are also needed. A successful vote will lead to a stake generation script that must be spent, and an unsuccessful vote will lead to a revocation script that must be spent. If we allowed stake change scripts to have a valid pubkey, that too would require another op code, but we disallow those for output.	4 years ago
matejcik	5cd7c72353	tests: rework tx cache The cache will no longer add new txes transparently. To add a transaction, see: ./tests/tx_cache.py --help	5 years ago

Author

SHA1

Message

Date

grdddj

3e11e8bba2

chore(tests): update Bitcoin test cases to use valid prevtxes

JoeGruff

e3ea32a986

multi: Add decred staking.

Add two new input and four output script types.

Decred ticket purchases consist of a stake submission, op returns, and
change addresses. Although change addresses are allowed by consensus,
they are no longer used in practice and so have been given the
restrictions of a null pubkey and no value. Stake scripts are almost
identical to p2pkh or p2sh except for an extra opcode in front. Inputs
are currently only used in the form of one input three outputs with the
first output, or stake submission, paying to a public key hash, or with
two inputs and five outputs with the stake submission paying to a
multisig script hash. The op returns are directed to the user in the
case of one and the voting service provider and user in the case of two.

One of the sstx commitment for a ticket must pay back to the trezor
wallet. This is checked and an error is thrown if we don't find the
expected public key hash.

Because this adds the ability to create new types of outputs once the
ticket votes, two new input script types are also needed. A successful
vote will lead to a stake generation script that must be spent, and an
unsuccessful vote will lead to a revocation script that must be spent.
If we allowed stake change scripts to have a valid pubkey, that too
would require another op code, but we disallow those for output.

matejcik

5cd7c72353

tests: rework tx cache

The cache will no longer add new txes transparently.
To add a transaction, see: ./tests/tx_cache.py --help

3 Commits (1882cc3a803b959642434f15b13e9d5008643f7c)