Proto commits in dogecoin/libdohj

These 64 commits are when the Protocol Buffers files have changed:

2022-02-14

Bump dependency versions to match bitcoinj 0.16

The documentation is generated from this commit.

2022-01-03

Update to bitcoinj 0.16 (#60)

The documentation is generated from this commit.

2021-01-10

Update to bitcoinj 0.15.7 (#44)

2016-06-27

Restructure libdohj around Maven modules

2015-08-08

Add Dogecoin payment protocol support Add Dogecoin payment protocol support, and remove unused proto definition files.

2015-05-30

Remove existing build pom.xml Added genesis block construction for Dogecoin network. Added difficulty calculations for Dogecoin network. Completed difficulty calculation code for Dogecoin. Added code for parsing Dogecoin blocks, and unit tests for same.

2014-12-23

Merge branch 'master' of https://github.com/bitcoinj/bitcoinj into rebase Conflicts: README.md core/pom.xml core/src/main/java/com/dogecoin/dogecoinj/core/DownloadListener.java core/src/main/java/com/dogecoin/dogecoinj/core/MemoryPool.java core/src/main/java/com/dogecoin/dogecoinj/core/NetworkParameters.java core/src/main/java/com/dogecoin/dogecoinj/core/PeerFilterProvider.java core/src/main/java/com/dogecoin/dogecoinj/core/PeerGroup.java core/src/main/java/com/dogecoin/dogecoinj/core/StoredTransactionOutput.java core/src/main/java/com/dogecoin/dogecoinj/core/Wallet.java core/src/main/java/com/dogecoin/dogecoinj/crypto/EncryptedPrivateKey.java core/src/main/java/com/dogecoin/dogecoinj/crypto/KeyCrypterScrypt.java core/src/main/java/com/dogecoin/dogecoinj/jni/NativeTransactionConfidenceListener.java core/src/main/java/com/dogecoin/dogecoinj/kits/WalletAppKit.java core/src/main/java/com/dogecoin/dogecoinj/net/FilterMerger.java core/src/main/java/com/dogecoin/dogecoinj/protocols/channels/IPaymentChannelClient.java core/src/main/java/com/dogecoin/dogecoinj/protocols/channels/PaymentChannelClient.java core/src/main/java/com/dogecoin/dogecoinj/protocols/channels/PaymentChannelClientConnection.java core/src/main/java/com/dogecoin/dogecoinj/protocols/channels/PaymentChannelClientState.java core/src/main/java/com/dogecoin/dogecoinj/store/BlockStore.java core/src/main/java/com/dogecoin/dogecoinj/store/FullPrunedBlockStore.java core/src/main/java/com/dogecoin/dogecoinj/store/H2FullPrunedBlockStore.java core/src/main/java/com/dogecoin/dogecoinj/store/PostgresFullPrunedBlockStore.java core/src/main/java/com/dogecoin/dogecoinj/testing/FakeTxBuilder.java core/src/main/java/com/dogecoin/dogecoinj/testing/TestWithPeerGroup.java core/src/main/java/com/dogecoin/dogecoinj/wallet/KeyChainGroup.java core/src/main/java/org/bitcoinj/core/DownloadListener.java core/src/main/java/org/bitcoinj/core/DownloadProgressTracker.java core/src/main/java/org/bitcoinj/core/MemoryPool.java core/src/main/java/org/bitcoinj/core/StoredTransactionOutput.java core/src/main/java/org/bitcoinj/core/TxConfidenceTable.java core/src/main/java/org/bitcoinj/core/UTXO.java core/src/main/java/org/bitcoinj/params/MainNetParams.java core/src/test/java/com/dogecoin/dogecoinj/core/AbstractFullPrunedBlockChainTest.java core/src/test/java/com/dogecoin/dogecoinj/core/BitcoindComparisonTool.java core/src/test/java/com/dogecoin/dogecoinj/core/FilteredBlockAndPartialMerkleTreeTests.java core/src/test/java/com/dogecoin/dogecoinj/core/FullBlockTestGenerator.java core/src/test/java/com/dogecoin/dogecoinj/core/PostgresFullPrunedBlockChainTest.java core/src/test/java/com/dogecoin/dogecoinj/core/WalletTest.java core/src/test/java/com/dogecoin/dogecoinj/crypto/ChildKeyDerivationTest.java core/src/test/java/com/dogecoin/dogecoinj/store/WalletProtobufSerializerTest.java core/src/test/java/com/dogecoin/dogecoinj/wallet/DefaultRiskAnalysisTest.java core/src/test/java/com/dogecoin/dogecoinj/wallet/DeterministicKeyChainTest.java tools/src/main/java/com/dogecoin/dogecoinj/tools/WalletTool.java wallettemplate/pom.xml wallettemplate/src/main/java/wallettemplate/Main.java wallettemplate/src/main/java/wallettemplate/MainController.java wallettemplate/src/main/java/wallettemplate/SendMoneyController.java

2014-12-19

Add an experimental HTTP based peer discovery engine that uses signed gzipped protocol buffers.

2014-12-02

PaymentChannelClient support encrypted wallets. Store will upgrade forward gracefully.

2014-11-14

Replace duplicated "current wallet version" constant by code that looks it up from the .proto itself.

2014-11-03

Rewrite most references to prodnet to mainnet in the comments. Does not change any actual code.

2014-10-18

Step 2: Move and refactor packages

2014-10-07

Refactor married keychains * move handling of following keychains into the leading keychain * move multisig threshold into the leading keychain * extract MarriedKeyChain from DeterministicKeyChain

2014-09-30

Renamespace to org.bitcoinj away from com.google.bitcoin, as bitcoinj is no longer a Google project and being namespaced under com.google causes issues with Sonatype/Maven Central. To fixinate your code: find . -name '*.java' | xargs sed -i .bak 's/import com.google.bitcoin./import org.bitcoinj./g;s/import static com.google.bitcoin./import static org.bitcoinj./g'

2014-09-22

Cache deterministic seed

2014-09-09

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)

Payment channel API. Negotiation af the channel duration. 1. Client requests a time window, in seconds relative to now. 2. Server suggests an expire time, absolute time in seconds 3. Client accepts or rejects the servers proposal. Note that the IPaymentChannelClient.ClinentConnection interface has a new method. This will break old implementations. Let the client request the duration of a payment channel. Server can set allowed time window.

2014-09-03

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-08-28

Support for applications recording exchange rate that was valid when transaction was sent. Use the new SendRequest.exchangeRate register. Includes a test.

2014-08-16

Remove TransactionConfidence.workDone. It doesn't seem useful and was somehow buggy.

2014-08-12

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-03

Support for bundling an optional info Protobuf ByteString with a PaymentAck message

2014-07-31

Support for bundling an optional info Protobuf ByteString with an UpdatePayment message.

2014-07-21

Add ASSURANCE_CONTRACT_CLAIM/PLEDGE/STUB to the purpose field.

2014-07-10

Remove support for mnemonic-less keychains

Fix BIP39 implementation

2014-06-23

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-05-29

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).

HD wallets alpha preview

Save value of inputs when completing transactions and persist it to the wallet protobuf. Determine the fee of a transaction in case we have all the values.

Update note about regenerating protobuf bindings.

2014-05-08

Add a simple API that lets you tag wallets with arbitrary string->byte[] pairs.

2014-01-28

Adding support for processing PaymentRequests.

2013-11-30

Support watching of scripts/addresses in wallet

2013-11-13

Payment channels: require a minimum payment to initiate. This is a (backwards incompatible) protocol change that prevents clients or servers getting into a situation where they have opened a channel that they then cannot close because insufficient value has been transferred. The server is allowed to specify the minimum payment it requires in order to open any channel at all, and the client then sanity checks that. Currently the rule is very simple - the min payment must be equal to the hard-coded dust limit. In future it will get more complicated as the dust limit starts to float and a more nuanced risk analysis may become required.

2013-11-12

Payment channels: rename "close" to "settle". The previous overloading of the term "close" to mean both settlement of the channel (broadcast of the final payment tx) and terminating/cleaning up the underlying network connection was very confusing and made the code harder to work with. The notion of "closing" a protocol that is often embedded inside others isn't really well defined, so there's perhaps more work to do here, but this change makes the code easier to follow and is basically a big pile of no-ops.

2013-11-11

Wallet: record the timestamp of the last block seen.

2013-11-01

Payment channels: add payment acks. Add a new PAYMENT_ACK message to the protocol. Make incrementPayment return a future that completes when the server has acknowledge the balance increase. Also, prevent users from overlapping multiple increase payment requests. This resolves race conditions that can occur when the billed-for activity is asynchronous to the protocol in which the micropayment protocol is embedded. In this case, it was previously impossible to know when the async activity could be resumed as it would otherwise race with the process of the server checking the payment signature and updating the balance. Most applications of micropayments will use a single protocol that has been extended with an embedding, and thus this is not an issue. However in some rare applications the payment process may run alongside the existing protocol rather than inside it. In this case, payment acks should be used for synchronization.

2013-10-14

Wallet: track relative ordering of transactions within a block. Ensures re-orgs don't replay transactions out of order. Resolves issue 468.

2013-10-04

Payment channels: protocol tweak - when the client sends a CLOSE, the server sends a CLOSE back that contains the final negotiated contract, so it can be inserted into the wallet without needing to wait for a network broadcast (this is useful if the client does not have internet connectivity at that point).

2013-09-30

Payment channels: bug fixes and improved close behaviour. The client now has a new CLOSED state, which is entered once a CLOSE has been sent and the close transaction (final contract) has been broadcast onto the P2P network and entered the wallet. Once received, the hash of the close tx is stored in the wallet - the tx is itself already in the wallets spent pool because it connects to the output of the multisig tx. After seeing three confirmations of the close TX the state is deleted from the client wallet for good. Together these changes resolve a bug/design issue in which if a channel was opened, then closed, then another channel was opened but not closed, then a third attempt to connect to the server was made, the client would try to resume the first closed channel. That would fail because the server already deleted its state object and result in new channels being created even though the second could have been resumed. By tracking the fact that the channel was closed, it can be skipped when considering what channel to resume.

2013-09-05

Payment channels: Better comments and logging.

2013-08-11

Wallet: support for key rotation. Key rotation allows you to specify a timestamp, and any money controlled by any keys created before that time will be automatically respent to keys created after it.

2013-07-11

Store states in protobufs instead of using Java Serialization. Saves having to use reflection.

2013-06-27

Implement server-side and client-side payment channel protocols. This implements micropayment payment channels in several parts: * Adds PaymentChannel[Server|Client]State state machines which handle initialization of the payment channel, keep track of basic in-memory state, and check data received from the other side, based on Mike Hearn's initial implementation. * StoredPaymentChannel[Client|Server]States manage channel timeout+broadcasting of relevant transactions at that time, keeping track of state objects which allow for channel resume, and are saved/loaded as a WalletExtension. * Adds PaymentChannel[Client|Server] which manage a connection by getting new protobufs, generating protobufs for the other side, properly stepping the associated State object and ensuring the StoredStates object is properly used to save state in the wallet. * Adds PaymentChannel[ClientConnection|ServerListener] which create TCP sockets to each other and use PaymentChannel[Client|Server] objects to create/use payment channels. The algorithm implemented is the one described at https://en.bitcoin.it/wiki/Contracts#Example_7:_Rapidly-adjusted_.28micro.29payments_to_a_pre-determined_party with a slight tweak to use looser SIGHASH flags so that the Wallet.completeTx code can work its magic by adding more inputs if it saves on fees. Thanks to Mike Hearn for the initial state machine implementations and all his contracts work and Jeremy Spilman for suggesting the protocol modification that works with non-standard nLockTime Transactions.

Some fixes to wallet serialization: 1) Switch the outpoint index field to be uint32 and fix isCoinBase() to consider the unsigned versions only. Resolves issue 420. 2) Regenerate the protobuf and fix an out of date definition in WalletProtobufSerializer that it exposed.

2013-04-26

Simplifications to the wallet code. Wallet: Remove/deprecate NOT_IN_BEST_CHAIN as a confidence type. TxConfidence: Rename NOT_SEEN_IN_CHAIN -> PENDING which is more precise and consistent. PeerGroup: Fix definition of "mined"

2013-03-18

Merge encrypted wallets functionality by Jim Burton.

2013-03-04

Save the last seen chain height as well as hash in the wallet.

2013-02-15

Label transactions with their source (network, wallet, other, etc). This will be used to allow spending of unconfirmed change.

2012-08-20

Serialize the broadcastBy set for each transaction. Resolves issue 237.

2012-07-21

Correct stale comment in bitcoin.proto

2012-06-08

Renamed TransactionConfidence.OVERRIDDEN_BY_DOUBLE_SPEND to DEAD

2012-06-01

TransactionConfidence changes (coinbase phase 2) + Mike's feedback

2012-04-15

Refactor transaction signing code so users can get the signature hash of an arbitrary input. Also add/fix comments in bitcoin.proto and make the Transaction.pool field optional.

2012-03-13

Use the standard Maven directory layout, rename "lib" to "core". Mavenize submodules.

2012-03-11

Re-organize the source tree so people can depend on bitcoinj without pulling in the examples, tools, or dependencies thereof.

2012-02-02

Be lenient in parsing tx confidence protobuf, store pubkeys, cleanup

Persist TransactionConfidence to protobuf

2012-01-12

Rationalize protobuf Pool enum

2012-01-11

Fixes based on input from Mike, fix invariant checking, fix spentBy

Wallet protobuf cleanup. * Un-nest protobuf * Add rest of tx fields, ASN.1 private key * Pending-inactive combo * Tests

2012-01-10

Read Wallet from protobuf stream

Protobuf serialization for Wallet