📡 Problem with the Faucet

[KarimJedda]

Faucet Type

Web

Problem

From a Telegram discussion

Hey all - The faucet is not working for me when I put H160 (AccountKey20) type address https://faucet.polkadot.io/westend?parachain=1000

It does an XCM transfer to an AccountId32 that is my address and FFF to fill in the 32 bytes.

Is this behavior expected?

https://westend.subscan.io/xcm_message/westend-42b82aed9d7aa0c7bf6ae146d39039d16304cd0d

cc @albertov19

Address

No response

Network ID

Relay Chain

Relevant log output

No response

[albertov19]

To add more context. It seems that the faucet is properly delivering the funds to the right H160 account. It seems that when you pass an Eth-style address it just appends f until the desired length (32 bytes).

The problem of me actually not seeing the funds in Metamask is because there is an issue with eth_getBalance. Check this:

curl --location 'https://westend-asset-hub-eth-rpc.polkadot.io' \
--header 'Content-Type: application/json' \
--data '{
    "jsonrpc":"2.0",
    "id":1,
    "method":"eth_getBalance",
    "params": ["0x476e0ecfc39c5070846159dceea5555fcbb26e08","latest"]
  }'

Response:

Error decoding into dynamic value: Error at : Error decoding bytes given the type ID and registry provided: Not enough data to fill buffer

I reproduced this with just a manual JSON RPC call but also in the console log of Metamask.

[mutantcornholio]

To add more context. It seems that the faucet is properly delivering the funds to the right H160 account. It seems that when you pass an Eth-style address it just appends f until the desired length (32 bytes).

Yeah, kinda.

The problem of me actually not seeing the funds in Metamask is because there is an issue with eth_getBalance.

Worked for me earlier today, but doesn't work now.

[athei]

It does an XCM transfer to an AccountId32 that is my address and FFF to fill in the 32 bytes.

This is expected behaviour. So I assume the person is trying to send to an account owned by a Polkadot account? In this case why not enter the full address instead of the H160?

[albertov19]

It does an XCM transfer to an AccountId32 that is my address and FFF to fill in the 32 bytes.

This is expected behaviour. So I assume the person is trying to send to an account owned by a Polkadot account? In this case why not enter the full address instead of the H160?

As an Ethereum developer, if you go to a Faucet, you would want to paste your ETH address as it is the one you usually interact with. This worked on my end with no problem (as you said, it was expected behavior).

The issue is not actually on the faucet but on the ETH_JSON_RPC side, as I reported in my comment.

I can see the actual balance in my Eth address (with the appended F to make it 32 bytes Substrate compliant), but only if I check it via the Substrate API and not the Ethereum JSON RPC.

[athei]

Okay then I misunderstood. I thought it was sent to an unexpected account. The error message looks like it is coming from suxt trying to decode.

[pgherveou]

I'll take a look now

[pgherveou]

Looks like this is related to the release of the runtime upgrade 1017003 that happened yesterday, we will re-deploy the eth-rpc to fix that

[albertov19]

Seems that this was fixed with the latest fix. Thanks! @pgherveou