Add support for Goliath Mainnet (Chain ID 327) — parallel to iOS issue #11

[465media]

Summary

Please add support for Goliath Mainnet, a new EVM-compatible Layer 1 blockchain launched by Onyx Protocol. This is a platform-parallel request to tangem-app-ios issue #11 — the same chain-support gap affects Android users of Tangem Wallet who have bridged XCN to Goliath.

Why this affects Android users

Although I'm filing from the Android perspective, the root cause appears to be shared across platforms (the supported-chains allowlist is at the SDK / app-config level, not iOS-specific). Any Tangem Wallet user — iOS or Android — who has bridged XCN from Ethereum to Goliath via the official app.onyx.org bridge is currently unable to sign transactions on chain 327.

The WalletConnect error returned is identical across platforms: "This network eip155:327 is not supported by Tangem Wallet and cannot be connected."

Network Details

Parameter | Value -- | -- Network Name | Goliath Mainnet Chain ID | 327 EIP-155 Chain ID | eip155:327 Currency Symbol | XCN RPC URL | https://rpc.goliath.net Block Explorer | https://explorer.goliath.net Validator Dashboard | https://validators.goliath.net

Why this should be straightforward to add

Goliath is fully EVM-compatible — the transaction signing format is identical to Ethereum and every other EVM chain Tangem already supports on Android (Arbitrum, Base, Optimism, Polygon, BNB Smart Chain, etc.). The signing logic itself doesn't need to change; the integration is adding chain 327 to the supported network list along with the RPC/explorer metadata.

Official Resources

• Documentation: https://docs.goliath.net
• Mainnet RPC: https://rpc.goliath.net
• Block Explorer: https://explorer.goliath.net
• Whitepaper: https://onyx.org/Goliath.pdf
• Onyx Protocol (parent project): https://onyx.org

Cross-references

• Sibling issue on iOS: Add Goliath Mainnet (Chain ID 327) EVM Network Support tangem-app-ios#11
• Onyx governance proposal for funding a community/SDK-based interim solution: [link once posted]

Request

1. Add Goliath Mainnet (Chain ID 327) to Tangem's supported networks on Android
2. Enable WalletConnect signing for transactions on this network
3. Coordinate with the iOS team on issue [B2B / Integration Request] Rabby Wallet devs are trying to reach you for native SDK integration #11 so platform rollout stays in sync

Happy to assist with testing on Android once a beta build is available.

Summary Please add support for Goliath Mainnet, a new EVM-compatible Layer 1 blockchain launched by Onyx Protocol. This is a platform-parallel request to tangem-app-ios issue #11 — the same chain-support gap affects Android users of Tangem Wallet who have bridged XCN to Goliath. Why this affects Android users Although I'm filing from the Android perspective, the root cause appears to be shared across platforms (the supported-chains allowlist is at the SDK / app-config level, not iOS-specific). Any Tangem Wallet user — iOS or Android — who has bridged XCN from Ethereum to Goliath via the official app.onyx.org bridge is currently unable to sign transactions on chain 327. The WalletConnect error returned is identical across platforms: "This network eip155:327 is not supported by Tangem Wallet and cannot be connected." Network Details ParameterValueNetwork NameGoliath MainnetChain ID327EIP-155 Chain IDeip155:327Currency SymbolXCNRPC URLhttps://rpc.goliath.net/Block Explorerhttps://explorer.goliath.net/Validator Dashboardhttps://validators.goliath.net/ Why this should be straightforward to add Goliath is fully EVM-compatible — the transaction signing format is identical to Ethereum and every other EVM chain Tangem already supports on Android (Arbitrum, Base, Optimism, Polygon, BNB Smart Chain, etc.). The signing logic itself doesn't need to change; the integration is adding chain 327 to the supported network list along with the RPC/explorer metadata. Official Resources

Documentation: https://docs.goliath.net/
Mainnet RPC: https://rpc.goliath.net/
Block Explorer: https://explorer.goliath.net/
Whitepaper: https://onyx.org/Goliath.pdf
Onyx Protocol (parent project): https://onyx.org/

Cross-references

Sibling issue on iOS: tangem/tangem-app-ios#11
Onyx governance proposal for funding a community/SDK-based interim solution: [link once posted]

Request

Add Goliath Mainnet (Chain ID 327) to Tangem's supported networks on Android
Enable WalletConnect signing for transactions on this network
Coordinate with the iOS team on issue #11 so platform rollout stays in sync

Happy to assist with testing on Android once a beta build is available.

[465media]

Update — and a stronger argument than the original post.
I've now empirically validated that the Tangem signing capability handles chain 327 correctly. Used a third-party app (Megnat — github.com/vilicvane/megnat) that's built on tangem-sdk-android and supports custom EVM chains. Paired my existing Tangem card, added Goliath as a custom chain (chain ID 327, RPC https://rpc.goliath.net/), connected to app.onyx.org via WalletConnect, and signed bridge transactions back from Goliath to Ethereum end-to-end across multiple incremental transactions. Bridge confirmed. Funds landed on Ethereum side. Same Tangem card, same NFC signing flow, same hardware — only the chain config differs.
This is evidence the integration lift is purely chain metadata + RPC config, not a card or SDK limitation. The signing primitives already work.
Additional context worth surfacing:

1. Onyx (the protocol behind Goliath) has active developer-grant funding.
   (This is also why a third party like Megnat being able to handle chain 327 with the existing SDK matters — Onyx has resources to fund integration work if Tangem's own roadmap is constrained.)
   Per public governance records (OIP-63 allocated 100M XCN for development and marketing initiatives), Onyx runs dev grants and bounty programs. This is relevant because Tangem engineering doesn't have to be the sole funder of Goliath integration work if that's an internal prioritization blocker — there is an upstream party with direct economic incentive to see this ship, and they have money allocated for exactly this category of integration.
2. tangem-sdk-ios is MIT-licensed and designed for third-party signing integrations.
   If Goliath native support in the official Tangem app isn't near-term, the SDK itself (https://github.com/tangem/tangem-sdk-ios) appears to be the intended extension point — per the README, it exists to "facilitate support for Tangem cards in third-party applications." Could Tangem clarify whether a third-party iOS app built on tangem-sdk-ios could sign EIP-155 transactions for an arbitrary EVM chain (chain 327 specifically), using a current-issue Tangem card, without any card-firmware or attestation changes? If yes, an Onyx-funded community app becomes a viable interim unblock while native support moves through Tangem's roadmap.
3. Specific technical question re: EIP-712 typed-data signing.
   Some modern bridges support gasless withdrawals where the user signs a structured message (EIP-712) and a relayer submits the actual on-chain transaction. Question for the Tangem team: does the current app reject chain 327 only for transaction signing, or also for EIP-712 typed-data signing? If typed-data signing has a separate code path that isn't gated on the supported-chain-list check, there may be an immediate escape hatch that Onyx + Superbridge could wire up server-side without any app changes on Tangem's side at all. Worth a one-sentence answer from someone on the wallet-integrations team if possible.
   Cross-references:

Onyx governance proposal (being drafted in parallel): [link once posted]
Parallel filing on tangem-app-android for affected Android users: [link once filed]

Happy to provide a clean WalletConnect trace, the exact error payload, or the Goliath RPC/explorer configuration needed for a minimal test rig if that helps eng reproduce.