DistributedCollective / DistributedCollective/Sovryn-smart-contracts

A specially high value 5x Long position opening transaction failed

Open
#185 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
JavaScript
Stars
132
Forks
57
PR merge metrics
No merged PRs in 30d

Description

This margin trade transaction failed.
The user has a balance of 0.099420942250782905 rBTC in his account and tried to supply a collateral of .097 rBTC.

There was an attempt to debug the transaction using our Sovryn node's debugging feature using the following CURL command:
curl -X POST -H "Content-Type:application/json" --data '{"jsonrpc":"2.0","method":"debug_traceTransaction","params":["0x3c15bf7ac9be22798a40ebe629430b1acb94266d941eff469c7f4ccc853c2fe8"],"id":1}' https://mainnet.sovryn.app/rpc

But the outcome overfloated the memory.

Then this code was attempted

$ echo Starting... Please Wait!

$out=$(curl -X POST -H "Content-Type:application/json" --data '{"jsonrpc":"2.0","method":"debug_traceTransaction","params":["0x3c15bf7ac9be22798a40ebe629430b1acb94266d941eff469c7f4ccc853c2fe8"],"id":1}' https://mainnet.sovryn.app/rpc 1> ouput.json )

$echo $out

$read -p " Process Finished! - Press [Enter] key to exit..."

the output.json (whic was extremely heavy) includeed the following result message:

"result":"08c379a0000000000000000000000000000000000000000000000000000000000000002000000000000000000000000000000000000000000000000000000000000000023234000000000000000000000000000000000000000000000000000000000000"
which is not giving any specific revertion message.

why may this transaction failed?
may be that the staking balance of the primary asset of the USDT/BTC AMM is way higher than the actual balance of the pool?

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the linked transaction in the RSK explorer and reproduce the debug_traceTransaction request against the Sovryn node RPC endpoint. Inspect the revert result and compare the reported collateral, account balance, and USDT/BTC AMM staking or pool balances; done means identifying a specific failure cause rather than only the generic revert data.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
blockchain
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.