The available evidence supports a summary of a historical audit of Portal to Bitcoin—not a current risk rating for any live deployment. “Portal” can also refer to an unrelated Ethereum data-access protocol, so the project and contracts must be identified before drawing conclusions.
Which Portal does this analysis cover?
This article covers Portal to Bitcoin, whose crypto-asset whitepaper describes the Portal Network as a Cosmos-based zone for atomic cross-chain asset swaps. The whitepaper says users bridge assets into a margin account and use an order book to swap with counterparties while minimizing required collateral. It describes a centralized Validator—initially the Portal team—and the Portal Foundation as key actors in the swap workflow, asset registration, and release of bridge funds. These are the whitepaper’s descriptions of the design and roles, not independent confirmation of current operations or control.
As an Amazon Associate I earn from qualifying purchases.
Ethereum’s Portal Network is different: it is an in-progress peer-to-peer protocol suite for lightweight access to Ethereum data and JSON-RPC functionality. Its specifications discuss retrieving account and state data, including contract code and storage, with validation against a recent header. That project may help users access Ethereum state; it is not evidence about Portal to Bitcoin’s bridge contracts. See the Ethereum Portal Network specifications.
Free tools Windows power users keep installed
One-click scans. No signup required.
What did the Portal to Bitcoin audit report?
Portal to Bitcoin’s whitepaper says Grey Swan audited core Portal Network smart contracts on Portal and Ethereum from June 23 through July 21, 2025, against code at commit 816e32a. It reports 15 issues and 12 considerations. The whitepaper says Grey Swan recommended resolving critical and high issues before deployment, and resolving medium and low issues as well.
#1 Best Overall
| Severity | Reported issue or scope | Status stated in the whitepaper |
|---|---|---|
| Critical: 1 issue | CustomERC6909 functions setOperator and approve reportedly let any user grant themselves unlimited permission to transfer assets from another user’s account. |
The whitepaper says the Portal team fixed it in a subsequent commit. It does not establish that the fix is in every live deployment. |
| High: 1 issue | The HTLC-based Invoice Manager reportedly had no refund timelock for the first depositor, so assets could remain locked indefinitely if the second party did not complete the swap. | Marked “Partially Resolved”: a timelock was added, while dynamic adjustment based on network conditions was still in progress. |
| Medium: 3 issues | The reported issues involved registering assets on a disabled chain; accepting Ether without crediting the sender in a receive function in two contracts; and integer overflow in a Portal Gateway power accumulator that could enable validator-set manipulation. |
The whitepaper says all three were fixed. |
| Low: 10 issues | The whitepaper describes these primarily as code-quality, best-practice, and edge-case concerns. | Further particulars are not stated in the summarized audit account. |
| Considerations: 12 | The whitepaper reports twelve considerations in addition to the fifteen issues. | They are described primarily as code-quality, best-practice, and edge-case concerns; further particulars are not stated in the summarized audit account. |
All audit details and remediation descriptions in the table are attributed to the Portal to Bitcoin whitepaper’s account of the Grey Swan audit. The whitepaper does not independently establish which fixes reached production, what code is currently deployed, or whether any historical issue remains exploitable.
Where should a deployment-specific review focus?
An audit finding identifies a risk in a particular code scope; it does not establish the condition of a different commit or deployment. For any confirmed Portal deployment, first map the assets, contracts, chains, and parties that can authorize or execute transfers. Then test the paths that connect those trust boundaries.
- Authorization and asset movement: Trace operator grants, approvals, minting, burning, escrow, release, and emergency paths. Confirm that each permission is limited to the intended actor, account, and asset. The reported
CustomERC6909issue makes delegated authority a concrete area to scrutinize. - Swap completion, refunds, and timeouts: Follow both parties’ deposits and completion paths, identify who can claim a refund and when, and test delayed or failed completion. Compare timeout assumptions across participating chains, including congestion and delayed finality. The Invoice Manager finding makes incomplete swaps and refund timing a priority.
- Chain and asset registration: Check that a chain is enabled before assets or routes can be registered. Review whether later registration changes could create unsupported or unbacked asset claims.
- Value accounting and native-asset receipt: Verify that every accepted transfer updates the expected account state. Include
receiveand fallback paths, as well as failed external calls, in the accounting trace. - Validator power and set transitions: Inspect arithmetic bounds, membership changes, quorum and signature rules, and whether a low-power group can influence the validator set. The whitepaper specifically reports an unchecked power-accumulator overflow in this area.
- Bridge trust and control: Establish who verifies cross-chain transfers, who can halt or censor activity, and who can release funds. Bridge designs carry different smart-contract, wrapped-asset, counterparty, and operational risks. Ethereum.org cautions: “While many bridges have successfully passed audits, all it takes is one flaw in a smart contract for assets to be exposed to hacks.” That is a general warning about bridges, not a finding about Portal to Bitcoin. See Ethereum.org’s bridge documentation.
- Cross-chain token permissions: If a deployment uses cross-chain mint or burn interfaces, identify every authorized caller and evaluate suitable limits. ERC-7802 says token issuers control which contracts can call cross-chain mint and burn functions and warns that a buggy or malicious authorized caller may harm holders. It is a proposal, not evidence that Portal implements it.
How can you tell whether the audit applies to deployed contracts?
Before treating an audit result or a claimed remediation as relevant to a live system, match the audited source to the exact deployment. The available whitepaper does not provide a verified current contract inventory or establish a present remediation state.
- Identify the deployment: Record the network and chain ID, contract addresses, and the assets or routes in scope. Do not assume that a project name alone identifies a particular contract set.
- Resolve proxies and control: For proxy-based contracts, identify the implementation and admin addresses. Record current role holders, upgrade permissions, and the history of implementation changes.
- Match code to the audit: Compare verified source or reproducible build output with the audited commit,
816e32a. Check for code changes after the audit dates of June 23–July 21, 2025, rather than assuming the audited commit is what runs now. - Verify each remediation: Locate the changes corresponding to the critical issue reported fixed in a subsequent commit, the partially resolved timelock issue, and the three medium findings reported fixed. Confirm that the relevant changes are included in the deployed implementation and that any remaining work is understood.
- Reassess material changes: If the live code, roles, configuration, supported chains, or swap workflow differ from the audited scope, evaluate those differences separately. An audit is scoped to the code and assumptions reviewed at that time.
What the audit does—and does not—establish
The whitepaper supplies a dated account of a Grey Swan review and specific reported findings, along with selected remediation statements. It does not establish current total value locked, a probability of exploitation, an estimated loss, a live-contract inventory, or the status of every fix. Those conclusions require deployment-specific evidence.
Do not transfer conclusions from this audit to Ethereum’s separate Portal Network, or use the name “Portal” alone to infer a system’s contracts or exposure. For any bridge, the relevant design questions include who verifies transfers, which chains and message capabilities are supported, how timeouts and finality work, what fees or security capital are involved, who can upgrade or halt the system, and what happens when a swap is delayed or incomplete. Ethereum.org discusses lock-and-mint, burn-and-mint, and atomic-swap designs alongside differences in security assumptions, connectivity, convenience, message capability, and cost in its bridge documentation.
Quick Recap
Best Value
- Made in USA - Proudly produced in Ohio by a Veteran-owned business
- Comprehensive Coverage: This BookFactory log book includes essential fields such as post/shift, time of change, date, weather conditions, and a designated space for detailed notes. This ensures that all relevant information is captured and easily accessible.
- Sturdy Cover: The trans-lux cover protects the log book from wear and tear, ensuring its longevity and maintaining the integrity of your recorded data.
- Essential Security Tool: This log book is an indispensable tool for any organization that values security and accountability. It helps to prevent misunderstandings, improve communication, and ensure a smooth transition between shifts.
- Wire-O with Trans-lux cover, 100 Pages, Dimensions 8.5" x 11" - (Security-Pass-Down) Reorder SKU: LOG-100-7CW-PP(Security-Pass-Down)
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
