Dev Report - numbersprotocol/community-support GitHub Wiki

Asset registration failed Report (22 Feb 2023)

[ Ticket Description ]

Asset can't register successfully on Capture App

[ Root Cause ]

We realized the IPFS gateway was not healthy, which caused the failures of the API requests to pin metadata to IPFS. Since commit API relies on this API to pin AssetTree, and NFTRecords to IPFS, commit API also fails and leads to the failure of all registrations.

Current status:

  • IPFS Gateway - restarted, healthy
  • IPFS Metadata API - normal
  • Commit API - normal
  • Registration service - normal

[ Solution ]

ipfs gateway (s3-ipfs) instance reachability failed => stop and start the instance. another problem: pipedream commit api custom json string error => update implementation to support json object and json string create [FR] Build a status service to display the current status future improvements

[ Ticket Closed Time ]

close at 2022/02/22 14:17 taipei time Total time spent : 2 hours

Network App Order Attack Report (25 Jun 2022)

[ Ticket Description ]

Many NFT can’t be finished in AVAX NFT campaign.

[ Root Cause ]

There were a lot of useless tasks generated by attackers and our server spent much time to handle those invalid orders. Total attack tasks: 19512 Max tasks waiting at the same time: 5317

[ Solution ]

Reduce task wait time, add more checks during our order transaction, and block attackers. Current tasks: 0

[ Ticket Closed Time ]

6:10 am UTC on 29th June 2022

Capture Wallet Migration (22 Mar 2022)

Total Wallets (wallet-pairs) involved: 1993 Total NUM transferred 61823.441792173082602619

Total Gas spent: 41244000 Total Cost: 3.22091514448759117 BNB

There are 7 users who withdraw BNB sent by the service wallet so that the migration cannot be completed. Since the assets cannot be migrated to asset wallets successfully, the service is suspended for the following wallets:

  • 0xAC52CcCc233bD9b0C2fD12A592Cd2447A7A7Aa82
  • 0xb869fA525568DDC8f82849d9f02F444BD4eAaF49
  • 0x72cbd65E08725d0d03fE2cFE8e99343320499915
  • 0x4c841BB9cA4bC0EEFAf3f01EE10A0F62a80cE413
  • 0xA0ED83B2982c716A6c998DB9571Af67d1D377a15
  • 0x620a1Fa7651932CE2868937a8E8548a9CC3b9956
  • 0x07B3c92f743454acDe0dDF4627BcAba980fEbe42

More details about Integrity Wallet v.s. Asset Wallet can be found here.

Unlock report (21 Mar 2022)

Dear NUM community and Numbers Protocol supporters,

The 3-month unlock of private-sale investors has ended and the distribution is done on 18th March 2022.

Here is a short summary of the unlock:

  • Total number of investors: 40
  • Claim contract: 0x904b6d98efaa8eed1ea282271f891e9f76618fff
  • Total tokens to be distributed: 7,207,729
  • Total tokens actual distributed to the contract: 5,956,479 (82.64%)
  • Tokens on hold because of potential violation of SAFT: 1,251,250 (17.36%)

If you encounter any problem while claiming tokens, it may be

  • Technical issues, please contact [email protected]
  • Due to the potential violation of SAFT, your contact did not pass the verification check. Please contact [email protected]. Our legal team will do our best to help you find a solution.

Thank you very much for your always support. We won’t be able to go this far without you. If you have any questions regarding the distribution, please contact [email protected]. We will continuously grow the project and make Numbers Protocol the foundation of the future Web 3.0 world.

Gift Capture error (24 Dec 2021)

[ Ticket Description ]

Participants of "Gift Capture" campaign may encounter "Invalid operation, please check your input again." error while sending the Capture using gift feature.

[ Root Cause ]

The way gift feature work is, it sends an API call to backend and requests backend to send a the Capture to receiver. If receiver accepts the request within 72 hours, the NFT ownership will be transferred. Otherwise, there won't be any ownership transfer happen. With this design, backend plays a role to deliver Captures in a "polite" way, i.e. receivers can decide whether or not they want to receive this NFT. However, because there were too many requests flooded into backend in two hours on 24th December, the gateways' load average was even more than 6K.

[ Solution ]

Scaled the API gateways immediately, and the Capture service should be normal again.

[ Ticket Closed Time ]

8:54 am UTC on 24th December 2021