origin-js
origin-js copied to clipboard
We've moved to a monorepo: https://github.com/OriginProtocol/origin
#177 ⚠️ **WARNING** ⚠️ This repository has been deprecated! Please create all new pull requests in [OriginProtocol/origin](https://github.com/OriginProtocol/origin/compare).
Listing images can be set to gifs. This may not be desired.
Eventually we want to automate as much of [the deployment checklist](https://github.com/OriginProtocol/origin-js/issues/104) as possible. A good first step would be: - Check balance of our test accounts - (If balance is...
"OfferData" events can be posted at any time, with any data. However, if getListing sees that an `OfferData` event has happened on a listing, it automatically marks the offer status...
We shouldn't be touching ipfs from anything inside ethereumInterface. The resources are intended to tie IPFS and Ethereum together. We should refactor users to follow this practice.
We currently have schemas for our IPFS data. However, there is also use for public-facing schemas for our `models`. These will allow us to render the model data in a...
As a starting point, it might be good to look at the [tools from Trail of Bits](https://blog.trailofbits.com/2018/03/23/use-our-suite-of-ethereum-security-tools/). There are a lot of good ideas in there. Let me know if...
When executing `npm run test:js`, I see this error scroll by: ``` Error during attestation validation: Error: Invalid signature v value at exports.ecrecover (/home/travis/build/OriginProtocol/origin-js/node_modules/ethereumjs-util/dist/index.js:403:11) at V00_UsersAdapter._callee8$ (/home/travis/build/OriginProtocol/origin-js/src/contractInterface/users/v00_adapter.js:206:25) at tryCatch (/home/travis/build/OriginProtocol/origin-js/node_modules/regenerator-runtime/runtime.js:65:40)...
To incentivize legitimate and helpful behavior for sellers, we are going to experiment with one or more forms of staking Origin tokens for listings. This task is for the contract...
When a require() in our contracts fails, they usually have a reason string that propagates to web3. This reason string is visible in our tests. For some reason, the require()...