> For the complete documentation index, see [llms.txt](https://aboutcryptotalks.gitbook.io/aboutcrypto/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://aboutcryptotalks.gitbook.io/aboutcrypto/portal-bridge-in-5-steps-for-treasury-transfers.md).

# Portal Bridge in 5 Steps for Treasury Transfers

Portal Bridge is a cross-chain token bridge that moves supported assets through Wormhole between Solana, Ethereum and other blockchains. The deciding check is whether the destination asset is the exact token your treasury or payees can receive. To send it, use [Portal Bridge](https://portalbridge.app) to initiate the transfer for the chosen token and recipient.

### What Is Portal Bridge?

Portal Bridge is an app for transferring supported tokens from one blockchain to another using Wormhole infrastructure. For a business, that can mean moving treasury funds to a different chain or funding a wallet used for payouts. The result is a token in the recipient’s wallet on the destination chain, which may be a wrapped representation of the original asset.

That distinction matters more than a matching token symbol. A payout system expecting native USDC on Ethereum may not accept a Wormhole-wrapped version of USDC, even if both display “USDC.” Identify the receiving token by its chain and contract address, and confirm that your custodian, exchange or payout contract accepts it before moving funds.

### How Does Portal Bridge Transfer Tokens Between Blockchains?

The transfer begins with a transaction on the source chain and ends with a separate delivery on the destination chain. With Wormhole Wrapped Token Transfers, the source-chain contract locks an original token or burns an existing wrapped token. Wormhole’s Guardians observe the transaction and sign a verifiable message called a VAA, which proves what was sent and where it should go.

The destination-chain contract verifies that message before minting a wrapped token or releasing an original token. Tokens therefore do not travel directly between blockchains; the contracts change the asset’s representation against a verified record of the source transaction. A transfer is complete for accounting purposes only when the destination transaction has delivered the expected asset to the intended wallet.

For example, sending an asset native to Solana through a wrapped-token route to Ethereum can produce its Wormhole-wrapped counterpart there. Sending that counterpart back burns it on Ethereum and releases the locked original on Solana. This is why the route and destination token deserve a check before the team signs anything.

### How Do I Bridge Tokens From Solana to Ethereum With Portal Bridge?

Use these five steps to move an approved amount from a Solana treasury wallet to an Ethereum recipient. The same checks apply to other supported chain pairs, although the available assets, destination token and completion method can differ.

1. **Specify the receiving asset.** Record the source token, intended Ethereum token, amount and recipient address in the transfer instruction. For a 10,000 USDC treasury move, write down whether the recipient needs native USDC or accepts a wrapped representation; “10,000 USDC on Ethereum” alone leaves that decision open. Check the destination token’s contract address against the recipient’s requirements before approving the route.
2. **Prepare the wallets.** Ensure the Solana sending wallet holds the transfer amount plus enough of its native token for the source transaction. If completion requires a transaction signed on Ethereum, arrange an Ethereum wallet with enough native gas before starting. Confirm the destination address belongs to the intended treasury or payee, since a valid transaction to the wrong address cannot be corrected by changing the transfer record later.
3. **Initiate the approved transfer.** At portalbridge.app, the operator initiates the selected token transfer from Solana to the Ethereum recipient. Before signing the source transaction, compare the chain, token, amount and full recipient address with the approved instruction. Save the source transaction hash as soon as it is submitted; it is the starting point for tracking the Wormhole message and resolving an incomplete transfer.
4. **Complete delivery on Ethereum.** Wait for the source transaction to reach the required finality and for Wormhole’s signed message to become available. Depending on the transfer route, a relayer may submit the destination transaction, or the operator may need to redeem the message using an Ethereum wallet and pay destination gas. If delivery appears delayed, inspect the source transaction and redemption status before attempting another transfer; resending could create a duplicate payout.
5. **Reconcile the received token.** Check the Ethereum transaction, the receiving address, the token contract and the net amount credited. Match both transaction hashes to the original instruction, then record any gas or relay costs separately from the token amount received. For recurring payouts, use a small first transfer to validate a new chain, asset and recipient combination before releasing the full batch.

### What Sets Portal Bridge Transfer Fees and Timing?

The cost depends on source-chain gas, destination-chain gas when a separate redemption is needed, and any fee for relaying the transfer. Those amounts vary with network activity and route, so use the cost shown for the specific transfer rather than a fixed fee assumption. For illustration, $4 of combined costs is 4% of a $100 payout but 0.04% of a $10,000 treasury move; batching may matter more than speed for small, frequent payments.

Time depends on source-chain finality, Guardian attestation and the destination transaction. Plan for minutes to tens of minutes, with longer delays possible during congestion or when manual redemption remains outstanding. Set an internal payout deadline that includes that uncertainty, and treat a confirmed source transaction as an in-progress transfer until the destination credit is verified.

### How Should a Team Handle Regular Transfers?

Regular transfers need a repeatable record of the asset and route, not merely a saved recipient address. Keep an approved pair of source and destination token contract addresses for each payout type, along with the chain, recipient, expected amount and the two transaction hashes. Review that record whenever the receiving service changes its accepted token or the route produces a different destination asset.

For each transfer, I would verify the destination token first, then compare the quoted cost with the payment size. Send only when the recipient can use that exact asset and the total cost fits the transfer’s purpose.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://aboutcryptotalks.gitbook.io/aboutcrypto/portal-bridge-in-5-steps-for-treasury-transfers.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.