graphprotocol / graphprotocol/graph-node

Reading Private Data from Contract

Open
#2,102 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

chains/ethereum enhancement
Dominant language
Rust
Stars
3.2k
Forks
1.1k
Avg merge
4d 1h
Merged PRs (30d)
1

Description

Do you want to request a feature or report a bug?
Feature

What is the current behavior?
its not implemented

What is the expected behavior?
with the web3 js library i can call web3.storageAt(contractaddress, index) to retrieve even private declared constants.
this is at this point not possible with AssemblyScript mappings API

example: https://github.com/emptysetsquad/dollar/blob/master/protocol/contracts/Constants.sol#L75

Contributor guide

Open the contributing guide

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 by comparing the web3.js storageAt behavior described in the issue with the AssemblyScript mappings API. Inspect the linked Constants.sol example to understand the private constant access case. Done means the mappings API can retrieve the requested contract storage value, with behavior verified against the web3.js example.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript, solidity
Domain
backend-api-design, blockchain
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.