Closed truedat101 closed 3 years ago
The good news is we have a nice reference of both a spec, a white paper, and a set of code that is well documented.
Add a unit test for the Address struct.
@pedroalvesbatista if you haven't started on this I can work on this.
Related to #9 . I think when #9 is done, we just need to take that data, and implement an Address struct or class.
Not really sure if we need an Address class, but might be useful for handling basic operations on address.
Punt out to proto3
Yeah, for addresses for now, yet, structs and basic ops should be enough. When working with peers and network maybe we need some class.
I added skeleton for functions to handle some basics of address approach. I will start to work more deeply on address while work on the hexdecimal hash generation.
Wait so if we can generate an address, isn't this 100% done?
I feel comfortable that we have a standard format. This is enforced by KeyPairFactory. Our spec/standard is: https://docs.nem.io/en/address-components
Marking this as done.
Actually, leave this open. The entire thing needs a test case. See accountcore.d.
Wow, accountcore.d is a mess. No structure and no actual work done.
ugg, seems like PB broke the dub.json.
A basic test case is done.
Transactions and wallets have addresses. We need a standard way to handle addressing.
Please reference details of NEM addressing: https://docs.nem.io/en/address-components
Let's borrow the best parts of this for the time being as an approach. Please define an address struct that handles this format:
The address of an account is a base-32 encoded triplet consisting of:
NEM's address api is defined here: https://www.nem.ninja/org.nem.core/org/nem/core/model/Address.html