monetas / gochroma Goto Github PK

The two functions that need some tests for the error conditions are:

ColorInsValid
OutPointToColorIn

Godep, or a docker based approach, or something similiar should be chosen to manage the dependencies. Currently, these are

github.com/btcsuite/btcd            167afc5304cc1707303d3a56e42ac6add1b2d129
github.com/btcsuite/btclog          baa3c5ace9907202e5659ee1416ee902facde213
github.com/btcsuite/btcrpcclient    34c87a73404c6bf1cc9648e0042f8817763f507b
github.com/btcsuite/btcutil         ff58d6571d21c0a8478befc038afd07b56bc0549
github.com/btcsuite/fastsha256      17eaa235e05dfb79432c9594dcafe20bb05690a7
github.com/btcsuite/golangcrypto    53f62d9b43e87a6c56975cf862af7edf33a8d0df
github.com/btcsuite/go-socks        a7a73aaa00584d5aee1efdb0891e19b7228d8d69
github.com/btcsuite/seelog          313961b101eb55f65ae0f03ddd4e322731763b6c
github.com/btcsuite/websocket       31079b6807923eb23992c421b114992b95131b55

.

There's no real need for this as the db is kept at the wallet level.

There's a lot of duplicated code in both. Use table-driven to reduce the amount of dupe code.

In particular, IFOC doesn't allow atomic swaps (my car for your car) in a single transaction. This is especially useful for trustless transactions.

IFOC stands for Indivisible First Output Coloring. A more generalized Smart Property Kernel needs to remove the First Output part of it.

This requires an addition to the BlockReaderWriter interface for figuring out if an outpoint has been spent or not.

Write Diffie-Helmann Key Exchange Coloring

blockexplorer.go and btcd.go both use a lot of (int64, error) as return values. Change these to pointers to int64. Note a bunch of tests and lib_test.go will need to be changed as well.

EPOBC uses nSquence of the first txinput to mark that the transaction is EPOBC-related. Do the same for IFOC and use a sequence other than EPOBC's.

New functions include HashString, Hash, AccountNumber, AffectingInputs and ColorValue.