GOSCADA
BRIDGE & ON-CHAIN DERIVATIVES

• Premium — the price paid by the buyer to acquire the option
• Strike price — the price used when exercising the option, denominated in PLS per SCADA. The contract imposes no restriction on when you may exercise — you can exercise out-of-the-money if you choose to, though it would not be economically rational to do so
• Expiry — the deadline after which the option can no longer be exercised
• In the money (ITM) — the option would be profitable to exercise right now
• Out of the money (OTM) — exercising would not be profitable — letting it expire makes more sense
• Collateral — assets locked by the issuer to guarantee they can fulfill the contract

• Options give the buyer a right. If the market moves against them, they walk away. Loss is capped at the premium.
• Futures give both parties an obligation. Nobody can walk away. Loss can be much larger than any premium.
• Futures have no premium — both sides take on symmetric risk in exchange for price certainty.
• Choose options when you want a safety net. Choose futures when you need a guaranteed price.

The SCADA Bridge does not hold or transfer SCADA between chains. Instead, it mints new SCADA on Ethereum when wSCADA is deposited, and burns SCADA on Ethereum when the user wants to go back. This keeps total cross-chain supply constant at all times.

Every SCADA token on Ethereum is backed by an equal amount of wSCADA locked in the bridge contract. This holds true even as supplyBlock burns reduce total supply — because supplyBlock burns wSCADA collateral in lockstep with SCADA burns, keeping the ratio at exactly 1:1.

This means: if you bridged SCADA to Ethereum and haven't traded it, you can always bridge the full amount back. The wSCADA is there.

• SCADA Bridge — immutable, no owner, no admin. Handles mint/burn and wSCADA reserves on Ethereum
• OmniBridge — PulseChain's canonical bridge. Wraps tokens for cross-chain transfer via AMB validators
• Home AMB (PulseChain) — collects validator signatures for PLS→ETH messages
• Foreign AMB (Ethereum) — verifies signatures and executes claims for PLS→ETH direction

Both directions require 96 block confirmations on the source chain before OmniBridge validators process the message. This is a security parameter set by the AMB — it ensures the source transaction is deeply finalized and extremely unlikely to be reorganized. On PulseChain (4-second blocks) this takes ~6.5 minutes. On Ethereum (12-second blocks) it takes ~19 minutes.

• The SCADA Bridge contract is immutable — no owner, no admin key, no upgrade path. The code cannot be changed after deployment
• Collateral is always verifiable on-chain. Anyone can call availableWscada() to see the bridge's reserves
• The mint-and-burn model means total cross-chain supply is constant — SCADA is never duplicated or destroyed without matching collateral
• OmniBridge is PulseChain's canonical bridge infrastructure, secured by the same validators that secure the chain

• Bridging requires gas on both chains — ETH gas for Ethereum transactions, PLS gas for PulseChain transactions
• The PLS→ETH claim step requires you to pay Ethereum gas. If ETH gas is expensive, the claim cost may be significant
• The 96-confirmation wait is not optional — there is no way to speed it up. Plan accordingly
• If you close your browser mid-bridge, use the "Track Existing Bridge" feature to resume tracking by pasting your tx hash
• SCADA on Ethereum has a buy/sell tax on Uniswap V2 trades. Bridging itself is tax-free, but trading the bridged SCADA on Ethereum is not

Your bridge is safe. The cross-chain message lives on the blockchain, not in your browser. Our bridge page saves your pending bridges in local storage, so they survive page refreshes and browser restarts. If you switch devices or clear your data, paste the original relay transaction hash in the "Track Existing Bridge" input to pick up where you left off.