nxt system should have a validation function to verify the account is available.
e.g:
acct: 209832084023840384023
MD5 & SHA Checksum: DfwSgeH
so the new account: DfwSgeH-209832084023840384023
Check the MD5 or SHA to verify the account available..
thanks for this example coolfish,
could you explain further please how this checksum approach can verify account available?
it just a simple example.
acct: 209832084023840384023
MD5 & SHA Checksum: DfwSgeH // from MD5("accountid")
so the new account: DfwSgeH-209832084023840384023 // from MD5("accountid")+ "- accountid"
if( MD5("209832084023840384023")=="DfwSgeH" ) it is available..
else unavailable.
yes, so far so good but how will this prevent from sending funds to a unknown account (hiberNXT)?
really, i don't get it (well, my had is full with gui & code atm) but the only way to reduce
the risk is to make a realtime check in front of each transfer but even this is not solid
because the account you intend to send funds could be a just unlocked one without any transaction
history and therefore unknown to the bc. at least this approach could give the user a feedback
to decide if the transfer should make or not.
how does a checksum fit's into this scenario or do i oversee something here?