Hi Igor, please open a support ticket at https://desk.zoho.eu/portal/jelurida/home (no need to register), provide as much data as you can, account addresses, transaction ids etc.
We will certainly consider a refund if we see that you were indeed scammed.
Step 4) is not intuitive to understand. The idea is that you sum the 6 bits into a number Ni then make sure 3*Ni+1 minus the value in the next row is 0 or that N minus 2 multiplied by the number in the next row is 0.
For example to check the constraint between row 1 and 2:
I like your idea but we still need to use the nonce counter otherwise we cannot generate more than one secret per account per block height. To fix the problem of forks we can require that the block id is at least 720 blocks in the past. It is not really important which block id we use as long as it cannot change in the future so using the nonce to determine the block height is not really important.
Good feedback, the hashed secret mechanism is optional, contracts can decide to ignore phased transactions completely although this is not as simple as it should be at the moment. Ideally a contract should declare if it supports hashed secrets (Yes/No/Only) so users can choose if to use it or not. By default contracts will process a trigger transaction regardless if it phased or not.
The Corda DJVM approach is similar in nature to the Ethereum EVM approach of the previous generation smart contracts. These contracts has to be run by every node (they do try to mask it but it is true) and therefore require metered execution and cannot interface with any external resources. Our lightweight contracts does not have these limitations…
Hi Arek, can’t tell much about the outcome of https://medium.com/binanceexchange/binance-dexathon-845dc0cbfffe
I know that xCubicle has applied but I don’t think they received any feedback from Binance.
When you prune transactions it means that a new node which joins the network cannot calculate the up to date account balances by re-validating all the transactions in the ledger since some transactions are not available anymore.
This means that the node has to first obtain a snapshot of the balances from another node and…