-
Notifications
You must be signed in to change notification settings - Fork 30
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Issue transferable document at token-registry result to a Null #202
Comments
seems like your title escrow address did not exist at rinkeby -> https://rinkeby.etherscan.io/address/0xF17a5Bae892693aBe872EdD388b7854F8E7BcCa0 but it exists at ropsten -> https://ropsten.etherscan.io/address/0xF17a5Bae892693aBe872EdD388b7854F8E7BcCa0 |
oh ok maybe i mix it up. Let me check again. Btw how can I fasten up the transaction ? Seems like very slow waiting for the transaction to be mined after sending to the pool. Already wait up to 30 minutes... This is the command i used to create new title escrow => open-attestation deploy title-escrow --network rinkeby --token-registry 0x2750961cfdD2ADaAC1136fA155091967DdAB70f9 --beneficiary 0x3F749ae09E4b1088DABAC33F528b227C9c4F59d7 --holder 0x3F749ae09E4b1088DABAC33F528b227C9c4F59d7 |
Hi, I already fix and redeploy new title escrow. But when I try to issue the document, it keeps prompt me below error. Can I get any help from you guys ? Thanks open-attestation token-registry issue -a 0x9dE0b6f08D8CeA3Cf7A082aCb84cae1Bea63b1Bf --tokenId 0x49577affe2f328bd31fca063a558c43126d5f429e1bf09679a9ae9816cafd54a --to 0xb18865EE4999D9cacC5641e39514c19c7A4Dd7f5 -n rinkeby whereby, You are falling back to oa-verify default configuration, which is not suitable for production environment. It is highly recommended that you configure and provide your own API key. Refer to https://github.com/Open-Attestation/oa-verify#provider ℹ info Issuing 0x49577affe2f328bd31fca063a558c43126d5f429e1bf09679a9ae9816cafd54a to the initial recipient 0xb18865EE4999D9cacC5641e39514c19c7A4Dd7f5 in the registry 0x9dE0b6f08D8CeA3Cf7A082aCb84cae1Bea63b1Bf ========= NOTICE ========= Request-Rate Exceeded (this message will not be repeated) While your application will continue to function, we highly recommended For more details: https://docs.ethers.io/api-keys/… awaiting Sending transaction to pool |
I run the follownig command after exporting OA_PRIVATE_KEY with my private key.
open-attestation token-registry issue -a 0x3F749ae09E4b1088DABAC33F528b227C9c4F59d7 --tokenId 0x131767b5686a434977fac29a0bf2d20acda19e307d2a54eec363fb5c73657e69 --to 0xF17a5Bae892693aBe872EdD388b7854F8E7BcCa0 -n rinkeby
whereby,
0xF17a5Bae892693aBe872EdD388b7854F8E7BcCa0 is the Title Escrow Address
0x3F749ae09E4b1088DABAC33F528b227C9c4F59d7 is the token registry address
0x131767b5686a434977fac29a0bf2d20acda19e307d2a54eec363fb5c73657e69 is the wrapped document merklee root
The result is as below ===>
You are falling back to oa-verify default configuration, which is not suitable for production environment. It is highly recommended that you configure and provide your own API key. Refer to https://github.com/Open-Attestation/oa-verify#provider
ℹ info Issuing 0x131767b5686a434977fac29a0bf2d20acda19e307d2a54eec363fb5c73657e69 to the initial recipient 0xF17a5Bae892693aBe872EdD388b7854F8E7BcCa0 in the registry 0x3F749ae09E4b1088DABAC33F528b227C9c4F59d7
========= NOTICE =========
Request-Rate Exceeded (this message will not be repeated)
The default API keys for each service are provided as a highly-throttled,
community resource for low-traffic projects and early prototyping.
While your application will continue to function, we highly recommended
signing up for your own API keys to improve performance, increase your
request rate/limit and enable other perks, such as metrics and advanced APIs.
For more details: https://docs.ethers.io/api-keys/
… awaiting Sending transaction to pool
✖ error null
Please let me know if i am missing something ?
The text was updated successfully, but these errors were encountered: