2015-05-01 08:28:01 +02:00
|
|
|
// Copyright (c) 2014 The btcsuite developers
|
Reimagine btcjson package with version 2.
This commit implements a reimagining of the way the btcjson package
functions based upon how the project has evolved and lessons learned while
using it since it was first written. It therefore contains significant
changes to the API. For now, it has been implemented in a v2 subdirectory
to prevent breaking existing callers, but the ultimate goal is to update
all callers to use the new version and then to replace the old API with
the new one.
This also removes the need for the btcws completely since those commands
have been rolled in.
The following is an overview of the changes and some reasoning behind why
they were made:
- The infrastructure has been completely changed to be reflection based instead
of requiring thousands and thousands of lines of manual, and therefore error
prone, marshal/unmarshal code
- This makes it much easier to add new commands without making marshalling
mistakes since it is simply a struct definition and a call to register that
new struct (plus a trivial New<foo>Cmd function and tests, of course)
- It also makes it much easier to gain a lot of information from simply
looking at the struct definition which was previously not possible
such as the order of the parameters, which parameters are required
versus optional, and what the default values for optional parameters
are
- Each command now has usage flags associated with them that can be
queried which are intended to allow classification of the commands such
as for chain server and wallet server and websocket-only
- The help infrastructure has been completely redone to provide automatic
generation with caller provided description map and result types. This
is in contrast to the previous method of providing the help directly
which meant it would end up in the binary of anything that imported the
package
- Many of the structs have been renamed to use the terminology from the
JSON-RPC
specification:
- RawCmd/Message is now only a single struct named Request to reflect the fact
it is a JSON-RPC request
- Error is now called RPCError to reflect the fact it is specifically an RPC
error as opposed to many of the other errors that are possible
- All RPC error codes except the standard JSON-RPC 2.0 errors have been
converted from full structs to only codes since an audit of the codebase
has shown that the messages are overridden the vast majority of the time
with specifics (as they should be) and removing them also avoids the
temptation to return non-specific, and therefore not as helpful, error
messages
- There is now an Error which provides a type assertable error with
error codes so callers can better ascertain failure reasons
programatically
- The ID is no longer a part of the command and is instead specified at the time
the command is marshalled into a JSON-RPC request. This aligns better with
the way JSON-RPC functions since it is the caller who manages the ID that is
sent with any given _request_, not the package
- All <Foo>Cmd structs now treat non-pointers as required fields and pointers as
optional fields
- All New<Foo>Cmd functions now accept the exact number of parameters, with
pointers to the appropriate type for optional parameters
- This is preferrable to the old vararg syntax since it means the code will
fail to compile if the optional arguments are changed now which helps
prevent errors creep in over time from missed modifications to optional args
- All of the connection related code has been completely eliminated since this
package is not intended to used a client, rather it is intended to provide
the infrastructure needed to marshal/unmarshal Bitcoin-specific JSON-RPC
requests and replies from static types
- The btcrpcclient package provides a robust client with connection management
and higher-level types that in turn uses the primitives provided by this
package
- Even if the caller does not wish to use btcrpcclient for some reason, they
should still be responsible for connection management since they might want
to use any number of connection features which the package would not
necessarily support
- Synced a few of the commands that have added new optional fields that
have since been added to Bitcoin Core
- Includes all of the commands and notifications that were previously in
btcws
- Now provides 100% test coverage with parallel tests
- The code is completely golint and go vet clean
This has the side effect of addressing nearly everything in, and therefore
closes #26.
Also fixes #18 and closes #19.
2014-12-31 08:05:03 +01:00
|
|
|
// Use of this source code is governed by an ISC
|
|
|
|
|
// license that can be found in the LICENSE file.
|
|
|
|
|
|
|
|
|
|
package btcjson
|
|
|
|
|
|
|
|
|
|
// GetTransactionDetailsResult models the details data from the gettransaction command.
|
2015-05-06 17:43:02 +02:00
|
|
|
//
|
|
|
|
|
// This models the "short" version of the ListTransactionsResult type, which
|
|
|
|
|
// excludes fields common to the transaction. These common fields are instead
|
|
|
|
|
// part of the GetTransactionResult.
|
Reimagine btcjson package with version 2.
This commit implements a reimagining of the way the btcjson package
functions based upon how the project has evolved and lessons learned while
using it since it was first written. It therefore contains significant
changes to the API. For now, it has been implemented in a v2 subdirectory
to prevent breaking existing callers, but the ultimate goal is to update
all callers to use the new version and then to replace the old API with
the new one.
This also removes the need for the btcws completely since those commands
have been rolled in.
The following is an overview of the changes and some reasoning behind why
they were made:
- The infrastructure has been completely changed to be reflection based instead
of requiring thousands and thousands of lines of manual, and therefore error
prone, marshal/unmarshal code
- This makes it much easier to add new commands without making marshalling
mistakes since it is simply a struct definition and a call to register that
new struct (plus a trivial New<foo>Cmd function and tests, of course)
- It also makes it much easier to gain a lot of information from simply
looking at the struct definition which was previously not possible
such as the order of the parameters, which parameters are required
versus optional, and what the default values for optional parameters
are
- Each command now has usage flags associated with them that can be
queried which are intended to allow classification of the commands such
as for chain server and wallet server and websocket-only
- The help infrastructure has been completely redone to provide automatic
generation with caller provided description map and result types. This
is in contrast to the previous method of providing the help directly
which meant it would end up in the binary of anything that imported the
package
- Many of the structs have been renamed to use the terminology from the
JSON-RPC
specification:
- RawCmd/Message is now only a single struct named Request to reflect the fact
it is a JSON-RPC request
- Error is now called RPCError to reflect the fact it is specifically an RPC
error as opposed to many of the other errors that are possible
- All RPC error codes except the standard JSON-RPC 2.0 errors have been
converted from full structs to only codes since an audit of the codebase
has shown that the messages are overridden the vast majority of the time
with specifics (as they should be) and removing them also avoids the
temptation to return non-specific, and therefore not as helpful, error
messages
- There is now an Error which provides a type assertable error with
error codes so callers can better ascertain failure reasons
programatically
- The ID is no longer a part of the command and is instead specified at the time
the command is marshalled into a JSON-RPC request. This aligns better with
the way JSON-RPC functions since it is the caller who manages the ID that is
sent with any given _request_, not the package
- All <Foo>Cmd structs now treat non-pointers as required fields and pointers as
optional fields
- All New<Foo>Cmd functions now accept the exact number of parameters, with
pointers to the appropriate type for optional parameters
- This is preferrable to the old vararg syntax since it means the code will
fail to compile if the optional arguments are changed now which helps
prevent errors creep in over time from missed modifications to optional args
- All of the connection related code has been completely eliminated since this
package is not intended to used a client, rather it is intended to provide
the infrastructure needed to marshal/unmarshal Bitcoin-specific JSON-RPC
requests and replies from static types
- The btcrpcclient package provides a robust client with connection management
and higher-level types that in turn uses the primitives provided by this
package
- Even if the caller does not wish to use btcrpcclient for some reason, they
should still be responsible for connection management since they might want
to use any number of connection features which the package would not
necessarily support
- Synced a few of the commands that have added new optional fields that
have since been added to Bitcoin Core
- Includes all of the commands and notifications that were previously in
btcws
- Now provides 100% test coverage with parallel tests
- The code is completely golint and go vet clean
This has the side effect of addressing nearly everything in, and therefore
closes #26.
Also fixes #18 and closes #19.
2014-12-31 08:05:03 +01:00
|
|
|
type GetTransactionDetailsResult struct {
|
2015-05-06 17:43:02 +02:00
|
|
|
Account string `json:"account"`
|
|
|
|
|
Address string `json:"address,omitempty"`
|
|
|
|
|
Amount float64 `json:"amount"`
|
|
|
|
|
Category string `json:"category"`
|
|
|
|
|
InvolvesWatchOnly bool `json:"involveswatchonly,omitempty"`
|
|
|
|
|
Fee *float64 `json:"fee,omitempty"`
|
|
|
|
|
Vout uint32 `json:"vout"`
|
Reimagine btcjson package with version 2.
This commit implements a reimagining of the way the btcjson package
functions based upon how the project has evolved and lessons learned while
using it since it was first written. It therefore contains significant
changes to the API. For now, it has been implemented in a v2 subdirectory
to prevent breaking existing callers, but the ultimate goal is to update
all callers to use the new version and then to replace the old API with
the new one.
This also removes the need for the btcws completely since those commands
have been rolled in.
The following is an overview of the changes and some reasoning behind why
they were made:
- The infrastructure has been completely changed to be reflection based instead
of requiring thousands and thousands of lines of manual, and therefore error
prone, marshal/unmarshal code
- This makes it much easier to add new commands without making marshalling
mistakes since it is simply a struct definition and a call to register that
new struct (plus a trivial New<foo>Cmd function and tests, of course)
- It also makes it much easier to gain a lot of information from simply
looking at the struct definition which was previously not possible
such as the order of the parameters, which parameters are required
versus optional, and what the default values for optional parameters
are
- Each command now has usage flags associated with them that can be
queried which are intended to allow classification of the commands such
as for chain server and wallet server and websocket-only
- The help infrastructure has been completely redone to provide automatic
generation with caller provided description map and result types. This
is in contrast to the previous method of providing the help directly
which meant it would end up in the binary of anything that imported the
package
- Many of the structs have been renamed to use the terminology from the
JSON-RPC
specification:
- RawCmd/Message is now only a single struct named Request to reflect the fact
it is a JSON-RPC request
- Error is now called RPCError to reflect the fact it is specifically an RPC
error as opposed to many of the other errors that are possible
- All RPC error codes except the standard JSON-RPC 2.0 errors have been
converted from full structs to only codes since an audit of the codebase
has shown that the messages are overridden the vast majority of the time
with specifics (as they should be) and removing them also avoids the
temptation to return non-specific, and therefore not as helpful, error
messages
- There is now an Error which provides a type assertable error with
error codes so callers can better ascertain failure reasons
programatically
- The ID is no longer a part of the command and is instead specified at the time
the command is marshalled into a JSON-RPC request. This aligns better with
the way JSON-RPC functions since it is the caller who manages the ID that is
sent with any given _request_, not the package
- All <Foo>Cmd structs now treat non-pointers as required fields and pointers as
optional fields
- All New<Foo>Cmd functions now accept the exact number of parameters, with
pointers to the appropriate type for optional parameters
- This is preferrable to the old vararg syntax since it means the code will
fail to compile if the optional arguments are changed now which helps
prevent errors creep in over time from missed modifications to optional args
- All of the connection related code has been completely eliminated since this
package is not intended to used a client, rather it is intended to provide
the infrastructure needed to marshal/unmarshal Bitcoin-specific JSON-RPC
requests and replies from static types
- The btcrpcclient package provides a robust client with connection management
and higher-level types that in turn uses the primitives provided by this
package
- Even if the caller does not wish to use btcrpcclient for some reason, they
should still be responsible for connection management since they might want
to use any number of connection features which the package would not
necessarily support
- Synced a few of the commands that have added new optional fields that
have since been added to Bitcoin Core
- Includes all of the commands and notifications that were previously in
btcws
- Now provides 100% test coverage with parallel tests
- The code is completely golint and go vet clean
This has the side effect of addressing nearly everything in, and therefore
closes #26.
Also fixes #18 and closes #19.
2014-12-31 08:05:03 +01:00
|
|
|
}
|
|
|
|
|
|
|
|
|
|
// GetTransactionResult models the data from the gettransaction command.
|
|
|
|
|
type GetTransactionResult struct {
|
|
|
|
|
Amount float64 `json:"amount"`
|
|
|
|
|
Fee float64 `json:"fee,omitempty"`
|
|
|
|
|
Confirmations int64 `json:"confirmations"`
|
|
|
|
|
BlockHash string `json:"blockhash"`
|
|
|
|
|
BlockIndex int64 `json:"blockindex"`
|
|
|
|
|
BlockTime int64 `json:"blocktime"`
|
|
|
|
|
TxID string `json:"txid"`
|
|
|
|
|
WalletConflicts []string `json:"walletconflicts"`
|
|
|
|
|
Time int64 `json:"time"`
|
|
|
|
|
TimeReceived int64 `json:"timereceived"`
|
|
|
|
|
Details []GetTransactionDetailsResult `json:"details"`
|
|
|
|
|
Hex string `json:"hex"`
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
// InfoWalletResult models the data returned by the wallet server getinfo
|
|
|
|
|
// command.
|
|
|
|
|
type InfoWalletResult struct {
|
|
|
|
|
Version int32 `json:"version"`
|
|
|
|
|
ProtocolVersion int32 `json:"protocolversion"`
|
|
|
|
|
WalletVersion int32 `json:"walletversion"`
|
|
|
|
|
Balance float64 `json:"balance"`
|
|
|
|
|
Blocks int32 `json:"blocks"`
|
|
|
|
|
TimeOffset int64 `json:"timeoffset"`
|
|
|
|
|
Connections int32 `json:"connections"`
|
|
|
|
|
Proxy string `json:"proxy"`
|
|
|
|
|
Difficulty float64 `json:"difficulty"`
|
|
|
|
|
TestNet bool `json:"testnet"`
|
|
|
|
|
KeypoolOldest int64 `json:"keypoololdest"`
|
|
|
|
|
KeypoolSize int32 `json:"keypoolsize"`
|
|
|
|
|
UnlockedUntil int64 `json:"unlocked_until"`
|
|
|
|
|
PaytxFee float64 `json:"paytxfee"`
|
|
|
|
|
RelayFee float64 `json:"relayfee"`
|
|
|
|
|
Errors string `json:"errors"`
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
// ListTransactionsResult models the data from the listtransactions command.
|
|
|
|
|
type ListTransactionsResult struct {
|
2015-05-06 17:43:02 +02:00
|
|
|
Account string `json:"account"`
|
|
|
|
|
Address string `json:"address,omitempty"`
|
|
|
|
|
Amount float64 `json:"amount"`
|
|
|
|
|
BlockHash string `json:"blockhash,omitempty"`
|
|
|
|
|
BlockIndex *int64 `json:"blockindex,omitempty"`
|
|
|
|
|
BlockTime int64 `json:"blocktime,omitempty"`
|
|
|
|
|
Category string `json:"category"`
|
|
|
|
|
Confirmations int64 `json:"confirmations"`
|
|
|
|
|
Fee *float64 `json:"fee,omitempty"`
|
|
|
|
|
Generated bool `json:"generated,omitempty"`
|
|
|
|
|
InvolvesWatchOnly bool `json:"involveswatchonly,omitempty"`
|
|
|
|
|
Time int64 `json:"time"`
|
|
|
|
|
TimeReceived int64 `json:"timereceived"`
|
|
|
|
|
TxID string `json:"txid"`
|
|
|
|
|
Vout uint32 `json:"vout"`
|
|
|
|
|
WalletConflicts []string `json:"walletconflicts"`
|
|
|
|
|
Comment string `json:"comment,omitempty"`
|
|
|
|
|
OtherAccount string `json:"otheraccount,omitempty"`
|
Reimagine btcjson package with version 2.
This commit implements a reimagining of the way the btcjson package
functions based upon how the project has evolved and lessons learned while
using it since it was first written. It therefore contains significant
changes to the API. For now, it has been implemented in a v2 subdirectory
to prevent breaking existing callers, but the ultimate goal is to update
all callers to use the new version and then to replace the old API with
the new one.
This also removes the need for the btcws completely since those commands
have been rolled in.
The following is an overview of the changes and some reasoning behind why
they were made:
- The infrastructure has been completely changed to be reflection based instead
of requiring thousands and thousands of lines of manual, and therefore error
prone, marshal/unmarshal code
- This makes it much easier to add new commands without making marshalling
mistakes since it is simply a struct definition and a call to register that
new struct (plus a trivial New<foo>Cmd function and tests, of course)
- It also makes it much easier to gain a lot of information from simply
looking at the struct definition which was previously not possible
such as the order of the parameters, which parameters are required
versus optional, and what the default values for optional parameters
are
- Each command now has usage flags associated with them that can be
queried which are intended to allow classification of the commands such
as for chain server and wallet server and websocket-only
- The help infrastructure has been completely redone to provide automatic
generation with caller provided description map and result types. This
is in contrast to the previous method of providing the help directly
which meant it would end up in the binary of anything that imported the
package
- Many of the structs have been renamed to use the terminology from the
JSON-RPC
specification:
- RawCmd/Message is now only a single struct named Request to reflect the fact
it is a JSON-RPC request
- Error is now called RPCError to reflect the fact it is specifically an RPC
error as opposed to many of the other errors that are possible
- All RPC error codes except the standard JSON-RPC 2.0 errors have been
converted from full structs to only codes since an audit of the codebase
has shown that the messages are overridden the vast majority of the time
with specifics (as they should be) and removing them also avoids the
temptation to return non-specific, and therefore not as helpful, error
messages
- There is now an Error which provides a type assertable error with
error codes so callers can better ascertain failure reasons
programatically
- The ID is no longer a part of the command and is instead specified at the time
the command is marshalled into a JSON-RPC request. This aligns better with
the way JSON-RPC functions since it is the caller who manages the ID that is
sent with any given _request_, not the package
- All <Foo>Cmd structs now treat non-pointers as required fields and pointers as
optional fields
- All New<Foo>Cmd functions now accept the exact number of parameters, with
pointers to the appropriate type for optional parameters
- This is preferrable to the old vararg syntax since it means the code will
fail to compile if the optional arguments are changed now which helps
prevent errors creep in over time from missed modifications to optional args
- All of the connection related code has been completely eliminated since this
package is not intended to used a client, rather it is intended to provide
the infrastructure needed to marshal/unmarshal Bitcoin-specific JSON-RPC
requests and replies from static types
- The btcrpcclient package provides a robust client with connection management
and higher-level types that in turn uses the primitives provided by this
package
- Even if the caller does not wish to use btcrpcclient for some reason, they
should still be responsible for connection management since they might want
to use any number of connection features which the package would not
necessarily support
- Synced a few of the commands that have added new optional fields that
have since been added to Bitcoin Core
- Includes all of the commands and notifications that were previously in
btcws
- Now provides 100% test coverage with parallel tests
- The code is completely golint and go vet clean
This has the side effect of addressing nearly everything in, and therefore
closes #26.
Also fixes #18 and closes #19.
2014-12-31 08:05:03 +01:00
|
|
|
}
|
|
|
|
|
|
|
|
|
|
// ListReceivedByAccountResult models the data from the listreceivedbyaccount
|
|
|
|
|
// command.
|
|
|
|
|
type ListReceivedByAccountResult struct {
|
|
|
|
|
Account string `json:"account"`
|
|
|
|
|
Amount float64 `json:"amount"`
|
|
|
|
|
Confirmations uint64 `json:"confirmations"`
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
// ListReceivedByAddressResult models the data from the listreceivedbyaddress
|
|
|
|
|
// command.
|
|
|
|
|
type ListReceivedByAddressResult struct {
|
|
|
|
|
Account string `json:"account"`
|
|
|
|
|
Address string `json:"address"`
|
|
|
|
|
Amount float64 `json:"amount"`
|
|
|
|
|
Confirmations uint64 `json:"confirmations"`
|
|
|
|
|
TxIDs []string `json:"txids,omitempty"`
|
|
|
|
|
InvolvesWatchonly bool `json:"involvesWatchonly,omitempty"`
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
// ListSinceBlockResult models the data from the listsinceblock command.
|
|
|
|
|
type ListSinceBlockResult struct {
|
|
|
|
|
Transactions []ListTransactionsResult `json:"transactions"`
|
|
|
|
|
LastBlock string `json:"lastblock"`
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
// ListUnspentResult models a successful response from the listunspent request.
|
|
|
|
|
type ListUnspentResult struct {
|
|
|
|
|
TxID string `json:"txid"`
|
|
|
|
|
Vout uint32 `json:"vout"`
|
|
|
|
|
Address string `json:"address"`
|
|
|
|
|
Account string `json:"account"`
|
|
|
|
|
ScriptPubKey string `json:"scriptPubKey"`
|
|
|
|
|
RedeemScript string `json:"redeemScript,omitempty"`
|
|
|
|
|
Amount float64 `json:"amount"`
|
|
|
|
|
Confirmations int64 `json:"confirmations"`
|
|
|
|
|
}
|
|
|
|
|
|
2015-05-06 15:50:23 +02:00
|
|
|
// SignRawTransactionError models the data that contains script verification
|
|
|
|
|
// errors from the signrawtransaction request.
|
|
|
|
|
type SignRawTransactionError struct {
|
|
|
|
|
TxID string `json:"txid"`
|
|
|
|
|
Vout uint32 `json:"vout"`
|
2015-05-07 19:30:21 +02:00
|
|
|
ScriptSig string `json:"scriptSig"`
|
2015-05-06 15:50:23 +02:00
|
|
|
Sequence uint32 `json:"sequence"`
|
|
|
|
|
Error string `json:"error"`
|
|
|
|
|
}
|
|
|
|
|
|
Reimagine btcjson package with version 2.
This commit implements a reimagining of the way the btcjson package
functions based upon how the project has evolved and lessons learned while
using it since it was first written. It therefore contains significant
changes to the API. For now, it has been implemented in a v2 subdirectory
to prevent breaking existing callers, but the ultimate goal is to update
all callers to use the new version and then to replace the old API with
the new one.
This also removes the need for the btcws completely since those commands
have been rolled in.
The following is an overview of the changes and some reasoning behind why
they were made:
- The infrastructure has been completely changed to be reflection based instead
of requiring thousands and thousands of lines of manual, and therefore error
prone, marshal/unmarshal code
- This makes it much easier to add new commands without making marshalling
mistakes since it is simply a struct definition and a call to register that
new struct (plus a trivial New<foo>Cmd function and tests, of course)
- It also makes it much easier to gain a lot of information from simply
looking at the struct definition which was previously not possible
such as the order of the parameters, which parameters are required
versus optional, and what the default values for optional parameters
are
- Each command now has usage flags associated with them that can be
queried which are intended to allow classification of the commands such
as for chain server and wallet server and websocket-only
- The help infrastructure has been completely redone to provide automatic
generation with caller provided description map and result types. This
is in contrast to the previous method of providing the help directly
which meant it would end up in the binary of anything that imported the
package
- Many of the structs have been renamed to use the terminology from the
JSON-RPC
specification:
- RawCmd/Message is now only a single struct named Request to reflect the fact
it is a JSON-RPC request
- Error is now called RPCError to reflect the fact it is specifically an RPC
error as opposed to many of the other errors that are possible
- All RPC error codes except the standard JSON-RPC 2.0 errors have been
converted from full structs to only codes since an audit of the codebase
has shown that the messages are overridden the vast majority of the time
with specifics (as they should be) and removing them also avoids the
temptation to return non-specific, and therefore not as helpful, error
messages
- There is now an Error which provides a type assertable error with
error codes so callers can better ascertain failure reasons
programatically
- The ID is no longer a part of the command and is instead specified at the time
the command is marshalled into a JSON-RPC request. This aligns better with
the way JSON-RPC functions since it is the caller who manages the ID that is
sent with any given _request_, not the package
- All <Foo>Cmd structs now treat non-pointers as required fields and pointers as
optional fields
- All New<Foo>Cmd functions now accept the exact number of parameters, with
pointers to the appropriate type for optional parameters
- This is preferrable to the old vararg syntax since it means the code will
fail to compile if the optional arguments are changed now which helps
prevent errors creep in over time from missed modifications to optional args
- All of the connection related code has been completely eliminated since this
package is not intended to used a client, rather it is intended to provide
the infrastructure needed to marshal/unmarshal Bitcoin-specific JSON-RPC
requests and replies from static types
- The btcrpcclient package provides a robust client with connection management
and higher-level types that in turn uses the primitives provided by this
package
- Even if the caller does not wish to use btcrpcclient for some reason, they
should still be responsible for connection management since they might want
to use any number of connection features which the package would not
necessarily support
- Synced a few of the commands that have added new optional fields that
have since been added to Bitcoin Core
- Includes all of the commands and notifications that were previously in
btcws
- Now provides 100% test coverage with parallel tests
- The code is completely golint and go vet clean
This has the side effect of addressing nearly everything in, and therefore
closes #26.
Also fixes #18 and closes #19.
2014-12-31 08:05:03 +01:00
|
|
|
// SignRawTransactionResult models the data from the signrawtransaction
|
|
|
|
|
// command.
|
|
|
|
|
type SignRawTransactionResult struct {
|
2015-05-07 18:42:16 +02:00
|
|
|
Hex string `json:"hex"`
|
|
|
|
|
Complete bool `json:"complete"`
|
2015-05-07 18:34:50 +02:00
|
|
|
Errors []SignRawTransactionError `json:"errors,omitempty"`
|
Reimagine btcjson package with version 2.
This commit implements a reimagining of the way the btcjson package
functions based upon how the project has evolved and lessons learned while
using it since it was first written. It therefore contains significant
changes to the API. For now, it has been implemented in a v2 subdirectory
to prevent breaking existing callers, but the ultimate goal is to update
all callers to use the new version and then to replace the old API with
the new one.
This also removes the need for the btcws completely since those commands
have been rolled in.
The following is an overview of the changes and some reasoning behind why
they were made:
- The infrastructure has been completely changed to be reflection based instead
of requiring thousands and thousands of lines of manual, and therefore error
prone, marshal/unmarshal code
- This makes it much easier to add new commands without making marshalling
mistakes since it is simply a struct definition and a call to register that
new struct (plus a trivial New<foo>Cmd function and tests, of course)
- It also makes it much easier to gain a lot of information from simply
looking at the struct definition which was previously not possible
such as the order of the parameters, which parameters are required
versus optional, and what the default values for optional parameters
are
- Each command now has usage flags associated with them that can be
queried which are intended to allow classification of the commands such
as for chain server and wallet server and websocket-only
- The help infrastructure has been completely redone to provide automatic
generation with caller provided description map and result types. This
is in contrast to the previous method of providing the help directly
which meant it would end up in the binary of anything that imported the
package
- Many of the structs have been renamed to use the terminology from the
JSON-RPC
specification:
- RawCmd/Message is now only a single struct named Request to reflect the fact
it is a JSON-RPC request
- Error is now called RPCError to reflect the fact it is specifically an RPC
error as opposed to many of the other errors that are possible
- All RPC error codes except the standard JSON-RPC 2.0 errors have been
converted from full structs to only codes since an audit of the codebase
has shown that the messages are overridden the vast majority of the time
with specifics (as they should be) and removing them also avoids the
temptation to return non-specific, and therefore not as helpful, error
messages
- There is now an Error which provides a type assertable error with
error codes so callers can better ascertain failure reasons
programatically
- The ID is no longer a part of the command and is instead specified at the time
the command is marshalled into a JSON-RPC request. This aligns better with
the way JSON-RPC functions since it is the caller who manages the ID that is
sent with any given _request_, not the package
- All <Foo>Cmd structs now treat non-pointers as required fields and pointers as
optional fields
- All New<Foo>Cmd functions now accept the exact number of parameters, with
pointers to the appropriate type for optional parameters
- This is preferrable to the old vararg syntax since it means the code will
fail to compile if the optional arguments are changed now which helps
prevent errors creep in over time from missed modifications to optional args
- All of the connection related code has been completely eliminated since this
package is not intended to used a client, rather it is intended to provide
the infrastructure needed to marshal/unmarshal Bitcoin-specific JSON-RPC
requests and replies from static types
- The btcrpcclient package provides a robust client with connection management
and higher-level types that in turn uses the primitives provided by this
package
- Even if the caller does not wish to use btcrpcclient for some reason, they
should still be responsible for connection management since they might want
to use any number of connection features which the package would not
necessarily support
- Synced a few of the commands that have added new optional fields that
have since been added to Bitcoin Core
- Includes all of the commands and notifications that were previously in
btcws
- Now provides 100% test coverage with parallel tests
- The code is completely golint and go vet clean
This has the side effect of addressing nearly everything in, and therefore
closes #26.
Also fixes #18 and closes #19.
2014-12-31 08:05:03 +01:00
|
|
|
}
|
|
|
|
|
|
|
|
|
|
// ValidateAddressWalletResult models the data returned by the wallet server
|
|
|
|
|
// validateaddress command.
|
|
|
|
|
type ValidateAddressWalletResult struct {
|
|
|
|
|
IsValid bool `json:"isvalid"`
|
|
|
|
|
Address string `json:"address,omitempty"`
|
|
|
|
|
IsMine bool `json:"ismine,omitempty"`
|
|
|
|
|
IsWatchOnly bool `json:"iswatchonly,omitempty"`
|
|
|
|
|
IsScript bool `json:"isscript,omitempty"`
|
|
|
|
|
PubKey string `json:"pubkey,omitempty"`
|
|
|
|
|
IsCompressed bool `json:"iscompressed,omitempty"`
|
|
|
|
|
Account string `json:"account,omitempty"`
|
|
|
|
|
Addresses []string `json:"addresses,omitempty"`
|
|
|
|
|
Hex string `json:"hex,omitempty"`
|
|
|
|
|
Script string `json:"script,omitempty"`
|
|
|
|
|
SigsRequired int32 `json:"sigsrequired,omitempty"`
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
// GetBestBlockResult models the data from the getbestblock command.
|
|
|
|
|
type GetBestBlockResult struct {
|
|
|
|
|
Hash string `json:"hash"`
|
|
|
|
|
Height int32 `json:"height"`
|
|
|
|
|
}
|
