Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Message does not correctly encode network #91

Open
ansermino opened this issue Dec 10, 2024 · 0 comments
Open

Message does not correctly encode network #91

ansermino opened this issue Dec 10, 2024 · 0 comments
Labels
Type: Bug Added to issues and PRs if they are addressing a bug

Comments

@ansermino
Copy link
Member

ansermino commented Dec 10, 2024

Describe the bug

When creating a message the address is not encoded according to the network.

To reproduce

  1. Go to faucet
  2. Open Network Inspector in the browser developer tools
  3. Request funds from the mainnet faucet to a valid 0x address
  4. Observe MpoolPush JSON RPC call

Log output

Image
(Note t address, despite requesting mainnet funds)

Resulting message on mainnet: https://beryx.io/fil/mainnet/txs/bafy2bzacecf2azdaqtr7cwhtlb66l6llq2t4w3xmst5hwr5xlyc52byhnn3ki?tab=overview

Expected behaviour

Should encode the address based on the network of the faucet

Screenshots

Environment (please complete the following information):

Current deployment: https://forest-explorer.chainsafe.dev/faucet

Other information and links

This is a non-critical issue as the RPC server does not validate the address.

@ansermino ansermino added the Type: Bug Added to issues and PRs if they are addressing a bug label Dec 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Type: Bug Added to issues and PRs if they are addressing a bug
Projects
Status: New
Development

No branches or pull requests

1 participant