Reading the chain…

ChainRobinhood Chain #4663

Block68,192,285

Endpoint and time

Endpointrpc.mainnet.chain.robinhood.com

Read at2026-09-20 19:33:05 UTC

Prill report

0x4189f0c66ebbb0bfef1c31f763131361ef32f77c

PRPermian Resources • Robinhood TokenISIN US71424F1057×1.004477… — 0.44% from 1As published by the chain operator. Nothing here was checked against the security it names; the ISIN is there so you can check it somewhere we cannot reach.

8 checks ran. 3 findings are consequential. 1 could not be determined — a gap, not a clean result.

Consequential: 3
Worth knowing: 1
Notable: 1
Context: 5

Reading the address you typed tells you about the stub. The behaviour is further along.

Ordered by consequence. Open any finding for the call behind it, or for what it cannot see.

01ConsequentialConfirmed

A balance here is worth 1.004477942292229526 times what it says.

This contract implements the scaled-balance extension, and its multiplier is currently 1.004477942292229526 rather than 1. The real position is the raw balance times 1.004477942292229526. Anything that reads the raw balance - a wallet, a price display, a pool, your own code - is wrong by that factor unless it applies the multiplier too. Nothing about this is hidden or improper; it is how this token type handles splits and dividends. It is also exactly the kind of thing that is invisible until it costs someone money.

Evidence — 1 call

uiMultiplier()

Request

{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "eth_call",
  "params": [
    {
      "to": "0x4189f0c66ebbb0bfef1c31f763131361ef32f77c",
      "data": "0xa60bf13d"
    },
    "0x410881d"
  ]
}

Result

0x0000000000000000000000000000000000000000000000000df09f5dd70b2d96

Chain 4663 · replay this against any node for the same answer

What this check cannot see

This reads the multiplier the contract reports right now, at this block. It cannot tell you why the multiplier is what it is, and a scheduled change that has not been written on chain yet would not appear here.

02ConsequentialConfirmed

193 other contracts we know about share this same upgrade switch.

Do not take our word for it.

18 recorded calls against block 68,192,285. Re-run every one of them in your browser against a node we do not control. If we are wrong, you see which call disagrees.

Verify this yourself

What these checks ask

contract.exists: Is there a contract at this address, and how large is its code?
proxy.detect: Does this contract hold its own logic, or forward to logic held elsewhere?
token.identity: What does this contract call itself, and how much of it exists?
erc8056.multiplier: Does the meaning of a balance here change without the balance changing?
code.provenance: What exactly is this code, and was it the same a short while ago?
proxy.blast: If the logic can be replaced, what else is replaced at the same time?
admin.authority: Who is able to change this contract, and is that a person or a contract?
powers.selectors: What powers are compiled into the code at this address?

Read something else

Open this address on Blockscout ↗

03ConsequentialConfirmed

The logic behind this contract can be replaced by whoever controls its beacon.

This is a beacon proxy. It holds no logic of its own: every call is forwarded to whatever address the beacon at 0xe10b6f6b275de231345c20d14ab812db62151b00 currently names. Because the beacon can be pointed at different logic, the behaviour of this contract - what transfer does, who can move your balance, whether it can be paused - is not fixed by anything at this address. This is not by itself a sign of anything wrong; it is a normal and often deliberate operational choice. It does mean that reading this contract's code tells you what it does today, not what it will do.

Read the beacon0xe10b6f…151b00

Evidence — 2 calls

code at the address

Request

{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "eth_getCode",
  "params": [
    "0x4189f0c66ebbb0bfef1c31f763131361ef32f77c",
    "0x410881d"
  ]
}

Result

0x6080604052600a600c565b005b60186014601a565b609d565b565b5f7f000000000000000000000000e10b6f6b275de231345c20d14ab812db62151b006001600160a01b0316635c60da1b6040518163ffffffff1660e01b8152600401602060405180830381865afa1580156076573d5f5f3e3d5ffd5b505050506040513d601f19601f820116820180604052508101906098919060ba565b905090565b365f5f375f5f365f845af43d5f5f3e80801560b6573d5ff35b3d5ffd5b5f6020828403121560c9575f5ffd5b81516001600160a01b038116811460de575f5ffd5b939250505056fea2646970667358221220e296a217a10765339b402e91ead95bcbcf74e678d7c756705f097d88cc2554b064736f6c63430008210033

Chain 4663 · replay this against any node for the same answer

ERC-1967 beacon slot

Request

{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "eth_getStorageAt",
  "params": [
    "0x4189f0c66ebbb0bfef1c31f763131361ef32f77c",
    "0xa3f0ad74e5423aebfd80d3ef4346578335a9a72aeaee59ff6cb3582b35133d50",
    "0x410881d"
  ]
}

Result

0x000000000000000000000000e10b6f6b275de231345c20d14ab812db62151b00

Chain 4663 · replay this against any node for the same answer

What this check cannot see

This checks the three standardised storage slots and the two standardised bytecode patterns. A contract that forwards calls by some other mechanism would not be detected here, and a proxy that is not currently pointing anywhere would read as empty.

05NotableConfirmed

The powers in this contract cannot be read from this address.

The code here is a forwarding stub, so scanning it tells you about the stub and nothing about what calling this contract would actually do. Whether it can mint, pause, freeze an account or charge a fee is decided by the implementation it points at, which right now is 0xb35490d6f9163de4f80d88dc75c3516eb64c5ae2. Reading that address answers this question properly, and there is a link to do it below. This is not a gap in the report - it is the honest shape of the question for a proxy.

Read the logic0xb35490…4c5ae2

Evidence — 1 call

code at the address

Request

{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "eth_getCode",
  "params": [
    "0x4189f0c66ebbb0bfef1c31f763131361ef32f77c",
    "0x410881d"
  ]
}

Result

Chain 4663 · replay this against any node for the same answer

What this check cannot see

This contract forwards its calls elsewhere, so its own bytecode contains almost no functions. Everything below is about the stub, not about the behaviour you would get by calling it. To see the real function surface, read the implementation address. This reads the function selectors compiled into the code at this address. It cannot see what those functions do, who is allowed to call them, or whether they are reachable at all. Functions absent from this list are absent from this bytecode - which is not the same as absent from the contract, if calls are forwarded elsewhere.

07ContextConfirmed

This code is unchanged since block 68,187,285.

We read the code at this address 5,000 blocks ago and it is byte-identical to the code there now. For a proxy this is a statement about the stub only - the logic it forwards to can have changed without a single byte of this code moving.

Evidence — 2 calls

code at block 68187285

Request

{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "eth_getCode",
  "params": [
    "0x4189f0c66ebbb0bfef1c31f763131361ef32f77c",
    "0x4107495"
  ]
}

Result

Chain 4663 · replay this against any node for the same answer

code at the address

Request

{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "eth_getCode",
  "params": [
    "0x4189f0c66ebbb0bfef1c31f763131361ef32f77c",
    "0x410881d"
  ]
}

Result

Chain 4663 · replay this against any node for the same answer

What this check cannot see

Comparing code across blocks requires an endpoint that retains historical state. Most public endpoints keep only a recent window and will refuse anything older, in which case this question cannot be answered here at all - which is reported rather than hidden. A code hash identifies the deployed bytecode exactly; it says nothing about the source it was compiled from.

10ContextConfirmed

This contract calls itself Permian Resources • Robinhood Token (PR).

It reports a total supply of 573.337, with 18 decimal places. Bear in mind what a name is: text the contract returns when asked. It is not registered anywhere and nothing prevents another contract from returning exactly the same text. If you arrived here expecting a particular project, the address is the only thing that settles it.

Evidence — 4 calls

name()

Request

{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "eth_call",
  "params": [
    {
      "to": "0x4189f0c66ebbb0bfef1c31f763131361ef32f77c",
      "data": "0x06fdde03"
    },
    "0x410881d"
  ]
}

Result

0x000000000000000000000000000000000000000000000000000000000000002000000000000000000000000000000000000000000000000000000000000000255065726d69616e205265736f757263657320e280a220526f62696e686f6f6420546f6b656e000000000000000000000000000000000000000000000000000000

Chain 4663 · replay this against any node for the same answer

symbol()

Request

{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "eth_call",
  "params": [
    {
      "to": "0x4189f0c66ebbb0bfef1c31f763131361ef32f77c",
      "data": "0x95d89b41"
    },
    "0x410881d"
  ]
}

Result

0x000000000000000000000000000000000000000000000000000000000000002000000000000000000000000000000000000000000000000000000000000000025052000000000000000000000000000000000000000000000000000000000000

Chain 4663 · replay this against any node for the same answer

decimals()

Request

{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "eth_call",
  "params": [
    {
      "to": "0x4189f0c66ebbb0bfef1c31f763131361ef32f77c",
      "data": "0x313ce567"
    },
    "0x410881d"
  ]
}

Result

0x0000000000000000000000000000000000000000000000000000000000000012

Chain 4663 · replay this against any node for the same answer

totalSupply()

Request

{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "eth_call",
  "params": [
    {
      "to": "0x4189f0c66ebbb0bfef1c31f763131361ef32f77c",
      "data": "0x18160ddd"
    },
    "0x410881d"
  ]
}

Result

0x00000000000000000000000000000000000000000000001f14a633d494228000

Chain 4663 · replay this against any node for the same answer

What this check cannot see

A name and a symbol are text the contract chose for itself. They are not unique, not registered, and not checked by anyone - two contracts can carry the same symbol, and one can carry the symbol of another on purpose. Only the address identifies a contract.

0x4189f0c66ebbb0bfef1c31f763131361ef32f77c

A balance here is worth 1.004477942292229526 times what it says.

193 other contracts we know about share this same upgrade switch.

Do not take our word for it.

What these checks ask

Read something else

The logic behind this contract can be replaced by whoever controls its beacon.

We could not determine who controls this contract.

The powers in this contract cannot be read from this address.

The exact code at this address has a fingerprint you can compare.

This code is unchanged since block 68,187,285.

There is a contract here, and its code is 283 bytes.

The behaviour of this contract currently comes from 0xb35490d6f9163de4f80d88dc75c3516eb64c5ae2.

This contract calls itself Permian Resources • Robinhood Token (PR).