We have not deployed this contract to Neo mainnet yet, so you can’t stake your tokens yet! But this will of course be live for exchange launch.
Please note that staking dividends and distributions are handled by the matching engine rather than this contract. Either way, I’m happy to answer any questions the community has.
This is not the thread to demand answers and complain, take a moment to celebrate this amazing accomplishment by the team! Bravo Thomas and team, looking forward to seeing the staking contract go live!
Congratulations nash team, great achievement that should be celebrated by this community. This is another step closer for nash and the community to being able to use a platform and be rewarded for using the product.
1 mod 2 = 1
1 mod 500 = 1
while
100000000 mod 1 = 0
100000000 mod 2 = 0
100000000 mod 5 = 0
100000000 mod 10 = 0
and so on?
It says if result is not equal to zero raise the exception else return amount right?
means…
if the left over from deviding the amount by the STAKE_MODULUS is not equal to 0 it raises an error.
the amount is always multiplied by 100,000,000 in NEP5 so that the contract doesnt have to deal with decimals. ie. 1 NEX’s amount is equal to 100,000,000 in the “eyes” of the contract.
Neo Global Development ( NGD ) does currently run the most consensus nodes, though this is slowly changing. COZ also runs one along with Dutch Telecom provider KPN. There are I think 2 more entities preparing their nodes on testnet, and once they are stable they’ll be coming on line. When that is complete, NGD nodes would need collaboration from non NGD nodes in order to cheat the network.
In regards to network issues with NEO, we’re well aware of them and have been pushing for changes for some time to improve stability. Either way, we’ve designed our protocol in a way that even if NEO is not running properly, the exchange will function almost the same as normal, with the exception being that deposits and withdrawals would be delayed.
With regards to NEO being a component of our name, this is no longer an issue with the new name