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
Implementing proto model for node registration transaction's attachment: one attachment for registration,update,remove,claim should be sufficient and grpc service methods ( /update/remove/claim) for api endpoints
Breakdown
Refactor nodeRegistration.proto model adding attachment message (trying with one attachement for all noderegistration apis first)
nodePublicKey: node pub key
lockedBalance: amount to be locked
nodeAddress: node address (IP address or domain name)
accountType: node owner account type
accountAddress: node owner account address
poown: proof of ownership message (get message structure from proof of ownership proto message, that should be something like the following):
accountType: account type
accountAddress: account address
blockHash: block hash of a recent block (when generated this is the node's last known block)
blockHeight: block height
signature: signature on all the above (by the node's private key)
… body proto message (#88)
* #82 - recompiled schema after adding node registration message and fixing bug in accountBalance request message
* recompiled schema after adding queued to noderegistration message
* fixed wrong data type for queued field
* #82 - recompiled schema after adding node registration message and fixing bug in accountBalance request message
* fixed wrong data type for queued field
* added util function to validate an account address
added new tx type for node registration (2,0)
WIP: implementation of (new) nodeRegistration transaction workflow
refactored some noderegistration query
fixed accountBalanceQuery: missing interface signature for ExtractModel and missing method for BuildModel
* refactored InsertNodeRegistration query
* implemented generic tx validation (util)
moved transactionUtil functions to common
separated generic tx from txType-specific validation logic
WIP: noderegistration txType
* commented out signature validation because of circular dependency
* fixed bug in addmempooltransaction
Description
Implementing proto model for node registration transaction's attachment: one attachment for registration,update,remove,claim should be sufficient and grpc service methods ( /update/remove/claim) for api endpoints
Breakdown
Additional Diagram / File
Reference
#68
The text was updated successfully, but these errors were encountered: