tests and benchmark to be able to test limits of the current restrections in the network. like number of bytes and stuff?
Or is it going to modify the node code to add new feature. I'm trying to understand but I don't seem to have the required knowledge about node software and inner work of the network.
this needed changes to node software is addressed in the 'maintenance-costs' section of the risk-assesment: https://github.com/bitjson/bch-bigint/blob/master/risk-assessment.md#maintenance-costs
Thank you, interesting. So nodes that will accept this will have to implement support for high-precision arithmetic
- it's modifying node code to implement arithmetic opcodes using BigInt library (gmp in case of BCHN) - it's modifying node code to remove the size <= 8 on arithmetic operations (now will be limited by stack item size - 10k - like all other ops) - cumulative cost of bigint ops will be limited by vm-limits budgeting system, so allowing those big int ops will result in 0 additional cost - aside from static test vectors, we test the whole system using property testing methodology (pit opcodes against each other, like <a> <b> OP_ADD OP_SUB must result in <a> for any random a and b
Обсуждают сегодня