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
2021-04-22T16:09:23Z My1
so the State v2 Blocks are seemingly decided to come into Nano, and they have a VERY nifty new field, the signer, which not only would make epoch signing easier (despite it being a very weird concept on the chain only you are supposed to be able to modify), it also allows for some other things, one of which I am proposing now.one of the very annoying things of Nano is the issue with ready to recieve blocks, which are kinda floating send blocks, as I like to imagine them. This while not only adding confusion to users because 'pending' transactions are still final they are not part of the balance yet and are often wrongly seen as unconfirmed sends, a wholly different matter, also has the far bigger issue of these floating nano, not being part of consensus.This means that for example 2 Million NANO from Binance's second cold wallet are not taking part in the voting process (as well as any other Nano that wasnt properly recieved), on top of that, floating sends cannot just be thrown into pruning or whatever but need to be kept ready to ensure that the account can properly recieve it, which is kinda annoying.So my Idea would be that with or some time after state-v2 that on a block that only acts as a recieve, the representative of that account has the ability to sign those blocks (if it wants to) so the Nano can stay in the consensus process to keep voting healthy and more Nano online
The text was updated successfully, but these errors were encountered:
2021-04-22T16:09:23Z My1
so the State v2 Blocks are seemingly decided to come into Nano, and they have a VERY nifty new field, the signer, which not only would make epoch signing easier (despite it being a very weird concept on the chain only you are supposed to be able to modify), it also allows for some other things, one of which I am proposing now.one of the very annoying things of Nano is the issue with ready to recieve blocks, which are kinda floating send blocks, as I like to imagine them. This while not only adding confusion to users because 'pending' transactions are still final they are not part of the balance yet and are often wrongly seen as unconfirmed sends, a wholly different matter, also has the far bigger issue of these floating nano, not being part of consensus.This means that for example 2 Million NANO from Binance's second cold wallet are not taking part in the voting process (as well as any other Nano that wasnt properly recieved), on top of that, floating sends cannot just be thrown into pruning or whatever but need to be kept ready to ensure that the account can properly recieve it, which is kinda annoying.So my Idea would be that with or some time after state-v2 that on a block that only acts as a recieve, the representative of that account has the ability to sign those blocks (if it wants to) so the Nano can stay in the consensus process to keep voting healthy and more Nano online
The text was updated successfully, but these errors were encountered: