You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Sequence to implement BIP175, pay to contract protocol as well as other utilities that will allow recipients and conferees to interact with the protocol under different circumstances.
Create CoinTypeKey function to grab coin type key (or basepayment hash) within the wallets clients local database. This is to be used within getPayToContractAddress.
Required additions to dcrd/dcrjson to allow RPCs from client to dcrd server.
CreatehashContracts, createContractArray, lexiSort functions for future use in functions within legacyrpc/methods.go.
Create getContractsHash and getPayToContractAddress methods within legacyrpc/methods.go
Refactor hashContracts to use blake256
Refactor lexiSort to use golang standard library - sort
Refactor getContractHash and getPayToContractAddress to utilize less of the heap
Implement required help messages in dcrwallet/internal for newly created RPC calls. Go Generate will also need to be ran in on legacyrpc/methods.go
Implement getContractHash & getPayToContractAddress as grpc
Create functions verifyContractHash and verifyContractHashAddress that allows the conferrer to verify the contract and P2PKH contract hash of the recipient.
Add createContract method within legacyrpc/methods.go. This will add ability to create "simple" contracts from the dcrwallet cli itself. And implement required help messages within dcrwallet/internal.
Refactor createContracyArray, hashContracts, getContractHash, getPayToContractAddress to include the createContract optionality.
Include P2PKH contract hashes in the wallets database. Work will have to be done in wallet.go
i.e get: getaddressbycontract : registers addresses in the database not by account by by contracts. getaddressbyconferee : registers addressees with their respected conferees.
Other:
This leads me to the thought of registering addresses to conferrees.
i.e registeraddreswithconferree takes in a address and a conferree and links them together.
The text was updated successfully, but these errors were encountered:
Sequence to implement BIP175, pay to contract protocol as well as other utilities that will allow recipients and conferees to interact with the protocol under different circumstances.
See https://github.com/bitcoin/bips/blob/master/bip-0175.mediawiki & https://arxiv.org/pdf/1212.3257v1.pdf for more details.
Create
CoinTypeKey
function to grab coin type key (or basepayment hash) within the wallets clients local database. This is to be used withingetPayToContractAddress
.Required additions to
dcrd/dcrjson
to allow RPCs from client to dcrd server.Create
hashContracts
,createContractArray
,lexiSort
functions for future use in functions withinlegacyrpc/methods.go
.Create
getContractsHash
andgetPayToContractAddress
methods within legacyrpc/methods.goRefactor
hashContracts
to use blake256Refactor
lexiSort
to use golang standard library - sortRefactor
getContractHash
andgetPayToContractAddress
to utilize less of the heapImplement required help messages in
dcrwallet/internal
for newly created RPC calls. Go Generate will also need to be ran in onlegacyrpc/methods.go
Implement
getContractHash
&getPayToContractAddress
as grpcCreate functions
verifyContractHash
andverifyContractHashAddress
that allows the conferrer to verify the contract and P2PKH contract hash of the recipient.Add
createContract
method withinlegacyrpc/methods.go
. This will add ability to create "simple" contracts from the dcrwallet cli itself. And implement required help messages withindcrwallet/internal
.Refactor
createContracyArray
,hashContracts
,getContractHash
,getPayToContractAddress
to include thecreateContract
optionality.Include P2PKH contract hashes in the wallets database. Work will have to be done in
wallet.go
i.e get:
getaddressbycontract
: registers addresses in the database not by account by by contracts.getaddressbyconferee
: registers addressees with their respected conferees.Other:
This leads me to the thought of registering addresses to conferrees.
i.e
registeraddreswithconferree
takes in a address and a conferree and links them together.The text was updated successfully, but these errors were encountered: