DistributedCollective / DistributedCollective/Sovryn-smart-contracts
Some Claim() transactions are failing
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 132
- Forks
- 57
- PR merge metrics
- No merged PRs in 30d
Description
The owner of this address: 0x19992115F80c686F56c1365868060Cbea8AA7a41
has tried six times to redeem his SOV tokens by the method 0x4e71d92d, to the contract 0xE0f5BF8D0C58d9C8A078Db75a9d379E6cdF3149e, but all the atempts has failed: https://explorer.rsk.co/address/0x19992115f80c686f56c1365868060cbea8aa7a41
among the transactions some was tried with high gas limit: https://explorer.rsk.co/tx/0x8f7be9cd869531f03ff572ff4060640d93ceb0f3d1429b439c6cffb85d4196ee
with the same reult.
The address 0x19992115F80c686F56c1365868060Cbea8AA7a41 is among the list of SOV owners from Origin:
https://github.com/DistributedCollective/Sovryn-smart-contracts/blob/3d3265191e4056c80a46fffe69ae6cea481f827c/scripts/deployment/origin_claim_list.csv
(line 470)
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by examining the Claim() path for contract 0xE0f5BF8D0C58d9C8A078Db75a9d379E6cdF3149e and compare it with the failing transactions linked in the issue. Check the address against scripts/deployment/origin_claim_list.csv at line 470, then determine the failure cause and verify that this owner can redeem successfully.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- blockchain, javascript
- Domain
- blockchain
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100