• 400 - Bad Request (Client Error)
• 401 - Unauthorized, authentication required
• 404 - Not Found

JSON API reports user input errors back to the client, e.g:

{"errors":["JSON parser error: Unexpected character 'f' at input index 27 (line 1, position 28)"],"status":400}

{"errors":["Can't read null as string element for actAs"],"status":401}

However there were multiple requests

Large integers, like 9999999999999999999999999 are valid in JSON files and are valid as data parts in the 0xcert conventions. However these numbers are currently not representable in JavaScript in full fidelity. This violates some guarantees made by (or assumptions you might make while using) the 0xcert Framework. Workarounds are available.

Discussion

These examples are running Safari Ver

I was researching on the various tools for Ethereum smart contract security and came across Securify. I read through in this document that Securify detects 18 critical vulnerabilities in Ethereum smart contracts. Can someone kindly consider my humble request fo

See the example of should-refill in http://1corp.io/snow/docs

-Function with the prefix should_ and the same parameters.
-Return True if need to call.

Ideally the standard should allow to do:
When function1 with args1 of contract1 returns true, call function2 with args2 of contract.

A deamon could watch the blockchain, calling function1 with args1 of contract1 at repeated interval. When

in https://docs.orbs.network/contract-sdk/orbs-contracts/events :

Orbs contract events give you the ability to log information into the blockchain that is stored as part of the receipt block.

the term "the receipt block" is an error?
also, should add motivation to adding events to receipts. what is it good for in real life use cases?

the reference contract contains an init function: