oasisprotocol / oasisprotocol/explorer
Parse net.oasis.scheduler.permissions
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 13
- Forks
- 13
- Avg merge
- 58m
- Merged PRs (30d)
- 2
Description
subcall https://explorer.oasis.io/testnet/sapphire/tx/0x6afcd94bd8ab9e18f12c3a0c445d198432fbe0f6b97e10b5a03065031e3ab022
native https://explorer.dev.oasis.io/testnet/sapphire/tx/512bb2c8a8edc9d812ac51ab0ffcd78dcf4faec81ad3474ab62917663b83c70d
oWhsb2cudmlld4FVABUafBL3j0oDGd4HRygbj5UK92DG is
{ log.view: [oasis1qq235lqj77855qcemcr5w2qm372s4amqcc4v3ztc (== 0xC3ecf872F643C6238Aa20673798eed6F7dA199e9)] }
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 reproducing the two linked Sapphire transactions and inspect the encoded net.oasis.scheduler.permissions value, including its CBOR-decoded log.view sample. Trace the explorer's existing handling of this permission field and determine which parsed result is missing; done means the field is parsed consistently for the supplied transactions and covered by an appropriate test.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- blockchain
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100