3
0
mirror of https://github.com/Qortal/altcoinj.git synced 2025-02-13 10:45:51 +00:00

20 Commits

Author SHA1 Message Date
Andreas Schildbach
9aed8ea0a5 For watching wallets, store the key creation time always in the watching key rather than the
DeterministicKeyChain. Creation times in the DeterministicKeyChain can't be persisted to protobuf,
as that structure has no full-blown protobuf equivalent.

This means a couple of DeterministicKeyChain, KeyChainGroup and Wallet factory method variants
that take creation dates have been removed. On the other hand, a convenient
Wallet.fromWatchingKeyB58(params, xpub, creationDate) has been added.

Also adds a test for protobuf-roundtripping watching wallets.

Supposed to fix issue #1209.
2016-03-11 10:08:42 +01:00
Andreas Schildbach
38848cd1cd TransactionConfidence: Add lastBroadcastedAt, the time a transaction was last announced to us.
The idea of this new field is that if a pending transaction was not announced for a longer time,
it is unlikely to confirm. Thus, the user should be warned and maybe the transaction removed from
the wallet at some point.
2016-02-16 14:09:21 +01:00
Andreas Schildbach
ee1aa05460 Remove comments about sequence numbers being disabled.
As of Bitcoin Core 0.12, sequence numbers are used for the infamous opt-in full replace-by-fee feature.
2016-01-26 16:07:04 +01:00
Andreas Schildbach
6b95012d1f wallet.proto: Add IN_CONFLICT transaction confidence state. 2015-11-29 11:33:16 +01:00
Andreas Schildbach
df5c4091c7 Wallet protobuf serialization for RAISE_FEE transaction purpose. 2015-07-14 10:51:38 +02:00
Andreas Schildbach
53688cde60 Replace duplicated "current wallet version" constant by code that looks it up from the .proto itself. 2014-11-14 17:08:51 +01:00
Andreas Schildbach
3aac4b0025 Rewrite most references to prodnet to mainnet in the comments. Does not change any actual code. 2014-11-03 14:23:36 +01:00
Devrandom
22f0600afe Refactor married keychains
* move handling of following keychains into the leading keychain
* move multisig threshold into the leading keychain
* extract MarriedKeyChain from DeterministicKeyChain
2014-10-07 15:39:04 +02:00
Devrandom
03bacf4fa9 Cache deterministic seed 2014-09-22 15:00:18 +02:00
Kosta Korenkov
5910a7f25e Married wallets: multisig threshold could be specified
That allows to create multisigs like 3-of-3. If not specified, majority of
keys will be required (2-of-3, 3-of-5 and so on)
2014-09-09 14:23:32 +02:00
Andreas Schildbach
7d930554a6 Support for recording a memo with transactions. It can be used to record the memo of the payment request that initiated the transaction. Use the new SendRequest.memo register. 2014-09-03 16:13:41 +02:00
Andreas Schildbach
5be769d4ca Support for applications recording exchange rate that was valid when transaction was sent. Use the new SendRequest.exchangeRate register.
Includes a test.
2014-08-28 14:32:26 +02:00
Andreas Schildbach
4834fe6eb6 Remove TransactionConfidence.workDone. It doesn't seem useful and was somehow buggy. 2014-08-16 15:16:11 +02:00
Kosta Korenkov
f6b2fa5a2b Pluggable signers: simple local KeyBag signer
Introduced pluggable signers notion. Instances of
TransactionSigner could be added into the wallet, so that they subsequently
applied to transaction to complete it.
Existing signing code (Transaction.signInputs) was refactored into
LocalTransactionSigner, which is always implicitly added to any wallet.

Related pull request: #157
2014-08-12 17:58:29 +02:00
Mike Hearn
92544e9d47 Add ASSURANCE_CONTRACT_CLAIM/PLEDGE/STUB to the purpose field. 2014-07-21 16:42:20 +02:00
Devrandom
fec6cbc7df Remove support for mnemonic-less keychains 2014-07-10 14:53:42 +02:00
Devrandom
2fae12064c Fix BIP39 implementation 2014-07-10 14:53:42 +02:00
troggy
06755aefde Married HD wallets: introduce shadow keychain notion
Pull request: #99
Based on design notes:
https://groups.google.com/d/msg/bitcoinj/Uxl-z40OLuQ/e2m4mEWR6gMJ
2014-06-23 14:53:09 +02:00
Mike Hearn
a807994b9a Bump wallet version and add missing check (!) to detect wallets from the future. The absence/incompleteness of this feature had not been noticed before, and it means that old apps will fail to read HD wallets due to the new key enum value rather than a more sensible error (but there's still no chance of an old app accepting an HD wallet, so it should still be safe). 2014-05-29 20:11:15 +02:00
Mike Hearn
5638387d3a HD wallets alpha preview 2014-05-29 20:11:13 +02:00