Search

Search for projects by name or address

Gluon logo
Gluon

Badges

About

Gluon aims to be a Layer 2 scalable trading engine built on top of Ethereum, unlocking low fees and high frequency trading.


  • Total Value SecuredTVS
    $30.76 K0.69%
  • Past day UOPSDaily UOPS
    No data
  • Type
    Plasma

  • Purpose
    Exchange

  • Tokens breakdown

    Sequencer failureState validationData availabilityExit windowProposer failure

    About

    Gluon aims to be a Layer 2 scalable trading engine built on top of Ethereum, unlocking low fees and high frequency trading.


    Total
    Canonically BridgedCanonically Bridged ValueCanonical
    Natively MintedNatively Minted TokensNative
    Externally BridgedExternally Bridged ValueExternal

    ETH & derivatives
    Stablecoins
    BTC & derivatives
    Other
    LeverJ trading platform appears to be in a maintenance mode as the team moved to build NFT trading platform. Social medias associated with the project are silent since mid 2021.
    Sequencer failureState validationData availabilityExit windowProposer failure
    Sequencer failure
    Force via L1

    Users can force the sequencerA party responsible for ordering and executing transactions on the rollup. The sequencer verifies transactions, compresses the data into a block, and submits the data related to it to enable state reconstruction to Ethereum L1 as a single transaction. The data can be either transaction data or state diffs. to include a transaction by submitting a request through L1Layer 1 (L1) is a blockchain that is self-reliant on its validator set for its security and consensus properties. Ethereum is an example of a layer 1. Blockchains started receiving the moniker of layer 1 once layer 2 became a meaningful area of development.. If the sequencer censors or is down for , users can use the exit hatch to withdraw their funds.

    State validation
    Fraud proofs (!)

    Fraud proofs allow actors watching the chain to prove that the state is incorrect. Because the data is not present on chain the security of fraud proofs is severely weakened.

    Data availability
    External

    Proof construction and state derivation rely fully on data that is NOT published onchain.

    Exit window
    None

    There is no window for users to exit in case of an unwanted upgrade since contracts are instantly upgradable.

    Proposer failure
    Use escape hatch

    Users are able to trustlessly exit by submitting a Merkle proof of funds.

    Data is not stored on chain

    Note: This section requires more research and might not present accurate information.

    The transaction data is stored on a plasmaPlasma is an offchain scaling solution that is able to support offchain data availability by allowing users to exit even when the data is unavailable. Usually, though, Plasma projects require users to frequently monitor the chain (e.g. at least once per week) to ensure that they can exit in time if necessary. There are attempts to support general smart contracts, but the exit mechanism is often limited to simpler applications. chain and is not recorded on the Ethereum main chain.

    • Funds can be lost if the external data becomes unavailable (CRITICAL).

    Fraud proofs
    Note: This section requires more research and might not present accurate information.

    After some period of time, the published state rootA cryptographic hash succinctly representing a state using a Merkle tree. is assumed to be correct. For a certain time period, usually one week, anyone can submit a fraud proofAlso referred to as a fault proof, it is the construction of an assertion that fraud was perpetrated on an optimistic rollup. More concretely, that an invalid state transition took place according to the protocol rules. The submitter of a fraud proof would expect a reward from the optimistic rollup protocol for helping maintain the integrity of the system. that shows that the state was incorrect.

    • Funds can be stolen if there is no one that checks the published state. Fraud proofs assume at least one honest and able validator.

    2025 July 14, 12:45 UTC
    11changes

    Discovery rerun on the same block number with only config-related changes.

    New and verified contracts

    + Status: CREATED
    contract SpotData (0x0d283D685F0A741C463846176e4c8EFF90D3F9EC)
    +++ description: None
    + Status: CREATED
    contract RegistryData (0x0fC25C7931679B838209c484d49Df0Cb9E633C41)
    +++ description: None
    + Status: CREATED
    contract SpotLogic (0x2D627FF93d32f5FEBb04d68409A889895B4aef2D)
    +++ description: None
    + Status: CREATED
    contract RegistryLogic (0x385827aC8d1AC7B2960D4aBc303c843D9f87Bb0C)
    +++ description: None
    + Status: CREATED
    contract DerivativesData (0x563052914Fd973a2305763269A106a7B0B6D50Cc)
    +++ description: None
    + Status: CREATED
    contract Gluon (0x75ACe7a086eA0FB1a79e43Cc6331Ad053d8C67cB)
    +++ description: None
    + Status: CREATED
    contract ApiKeyRegistry (0x7B70aCD346892736f9f6c7F4f196B07400a50Da0)
    +++ description: None
    + Status: CREATED
    contract StakeLogic (0x84e34fD82FC368F1a072075114AdC4b552a7a1F4)
    +++ description: None
    + Status: CREATED
    contract StakeData (0xaB3AC436D66CBEeDc734ed2c1562c3a213c9bc77)
    +++ description: None
    + Status: CREATED
    contract LegacyTokensExtension (0xDA88EfA53c85Afa30564bb651A2E76b99a232082)
    +++ description: None
    + Status: CREATED
    contract DerivativesLogic (0xDfBFe895e07e5115773Cb9631CB2148114589caC)
    +++ description: None
    2024 December 12, 15:26 UTC
    3changes

    Ignored not needed values in config.

    contract StakeLogic (0x84e34fD82FC368F1a072075114AdC4b552a7a1F4) {
    +++ description: None
    values.currentIntervalIndex:
    - 23
    + 24
    values.getToBeDistributed.2:
    - 2730626699
    + 2730244557
    values.getToBeDistributed.1:
    - "1346902354215947912554"
    + "1346505840564614195006"
    }
    2024 December 10, 11:07 UTC
    11changes

    Provide description of changes. This section will be preserved.

    Initial discovery

    + Status: CREATED
    contract SpotData (0x0d283D685F0A741C463846176e4c8EFF90D3F9EC)
    +++ description: None
    + Status: CREATED
    contract RegistryData (0x0fC25C7931679B838209c484d49Df0Cb9E633C41)
    +++ description: None
    + Status: CREATED
    contract SpotLogic (0x2D627FF93d32f5FEBb04d68409A889895B4aef2D)
    +++ description: None
    + Status: CREATED
    contract RegistryLogic (0x385827aC8d1AC7B2960D4aBc303c843D9f87Bb0C)
    +++ description: None
    + Status: CREATED
    contract DerivativesData (0x563052914Fd973a2305763269A106a7B0B6D50Cc)
    +++ description: None
    + Status: CREATED
    contract Gluon (0x75ACe7a086eA0FB1a79e43Cc6331Ad053d8C67cB)
    +++ description: None
    + Status: CREATED
    contract ApiKeyRegistry (0x7B70aCD346892736f9f6c7F4f196B07400a50Da0)
    +++ description: None
    + Status: CREATED
    contract StakeLogic (0x84e34fD82FC368F1a072075114AdC4b552a7a1F4)
    +++ description: None
    + Status: CREATED
    contract StakeData (0xaB3AC436D66CBEeDc734ed2c1562c3a213c9bc77)
    +++ description: None
    + Status: CREATED
    contract LegacyTokensExtension (0xDA88EfA53c85Afa30564bb651A2E76b99a232082)
    +++ description: None
    + Status: CREATED
    contract DerivativesLogic (0xDfBFe895e07e5115773Cb9631CB2148114589caC)
    +++ description: None

    The system has a centralized operator

    Note: This section requires more research and might not present accurate information.

    The operatorAn operator is the entity charged with managing a rollup and progressing its state. A rollup operator can be a centralized sequencer, proposer, prover, challenger, pauser of admin that is able to perform upgrades. is the only entity that can propose blocksAn ordered list of transactions and chain-related metadata that gets bundled together and published to the L1/DA layer. Nodes execute the transactions contained within blocks to change the rollup chain’s state. Protocol rules dictate what constitutes a valid block, and invalid blocks are skipped over.. A live and trustworthy operator is vital to the health of the system.

    • MEV can be extracted if the operator exploits their centralized position and frontruns user transactions.

    Users can independently exit the system

    Note: This section requires more research and might not present accurate information.

    Independent exit allows the users to escape censorship by withdrawing their funds. The system allows users to withdraw their funds by submitting a transaction directly to the contract onchain.

    • Users can be censored if the operator refuses to include their transactions. However, there exists a mechanism to independently exit the system.

    Regular exit

    Note: This section requires more research and might not present accurate information.

    The user executes the withdrawal by submitting a transaction on L1Layer 1 (L1) is a blockchain that is self-reliant on its validator set for its security and consensus properties. Ethereum is an example of a layer 1. Blockchains started receiving the moniker of layer 1 once layer 2 became a meaningful area of development. that requires a merkle proof of funds.

    The mass exit problem is unsolved

    Note: This section requires more research and might not present accurate information.

    In case the operatorAn operator is the entity charged with managing a rollup and progressing its state. A rollup operator can be a centralized sequencer, proposer, prover, challenger, pauser of admin that is able to perform upgrades. is malicious all users need to exit within a predetermined time frame. Users that do not manage to do this will lose their funds.

    • Funds can be stolen if users are unable to withdraw in a mass exit event.

    A dashboard to explore contracts and permissions
    Go to Disco
    Disco UI Banner

    Ethereum

    RegistryLogic0x3858…Bb0C
    RegistryData0x0fC2…3C41
    StakeLogic0x84e3…a1F4
    StakeData0xaB3A…bc77
    SpotLogic0x2D62…ef2D
    DerivativesLogic0xDfBF…9caC
    DerivativesData0x5630…50Cc
    LegacyTokensExtension0xDA88…2082

    The current deployment carries some associated risks:

    • Funds can be stolen if a contract receives a malicious code upgrade. There is no delay on code upgrades (CRITICAL).