Claiming Morse Suppliers
1
Example output
Enter Decrypt Passphrase:
MsgClaimMorseSupplier {
"shannon_owner_address": "pokt1chn2mglfxqcp52znqk8jq2rww73qffxczz3jph",
"shannon_operator_address": "pokt1chn2mglfxqcp52znqk8jq2rww73qffxczz3jph",
"morse_src_address": "44892C8AB52396BA016ADDD0221783E3BD29A400",
"morse_signature": "rYyN2mnjyMMrYdDhuw+Hrs98b/svn38ixdSWye3Gr66aAJ9CQhdiaYB8Lta8tiwWIteIM8rmWYUh0QkNdpkNDQ==",
"services": [
{
"service_id": "anvil",
"endpoints": [
{
"url": "http://relayminer1:8545",
"rpc_type": 3
}
],
"rev_share": [
{
"address": "pokt1chn2mglfxqcp52znqk8jq2rww73qffxczz3jph",
"rev_share_percentage": 100
}
]
}
]
}
Confirm MsgClaimMorseSupplier: y/[n]: y2
3
Ensure your Shannon Supplier has an onchain public key
MUST READ FOR ALL SUPPLIER
Your RelayMiner & Supplier will not work if you don't follow this section.
Problem: Migrated Suppliers WITHOUT onchain public keys CANNOT sign Relay Responses and will be sanctioned by PATH.
Root Cause: A migrated supplier has an onchain account, but it does not have an onchain public key until it signs an onchain transaction.
Solution: Submit any onchain transaction where --from is the supplier address.
Any transaction will work. For example, a small transfer:
pocketd tx bank send <your_supplier_address> <some_address_you_own> 1upokt --from=<your_supplier_address> ...How to check if you have an onchain account
pocketd q auth account <your_supplier_address> --network=<network>Account without public key:
account:
type: /cosmos.auth.v1beta1.BaseAccount
value:
account_number: "..."
address: pokt1...
sequence: "..."Account with public key:
account:
type: /cosmos.auth.v1beta1.BaseAccount
value:
account_number: "..."
address: pokt1...
public_key:
type: /cosmos.crypto.secp256k1.PubKey
value: Ap/Nr...
sequence: "..."Troubleshooting
See: pocketd tx migration claim-supplier --help for more details.
Was this helpful?
