ETH Price: $1,914.35 (+0.47%)
BaseScan Transaction Action
Transaction Hash:
0xaa876d76d54170b2a651f5faa9362a2878d1808ddafc7c89581aad4f749725ca
Status:
Success
Block:
28076723 Confirmed by Sequencer
Timestamp:

Sponsored:

To:
0x8768c789C6df8AF1a92d96dE823b4F80010Db294 (Seamless Protocol: Governor Short Proxy)

Value:
0 ETH ($0.00)
Transaction Fee:
0.00000200112759778 ETH
Gas Price:
0.003078726 Gwei (0.000000000003078726 ETH)
ETH Price:
$2,066.62 / ETH
Gas Limit & Usage by Txn:
883,552 | 639,677 (72.4%)
Gas Fees:
Base: 0.002080395 Gwei |Max: 0.005163749 Gwei |Max Priority: 0.000998331 Gwei

L2 Fees Paid:
0.000001969390211502 ETH
L1 Fees Paid:
0.000000031737386278 ETH
L1 Gas Price:
0.000000000389361892 ETH (0.389361892 Gwei)
L1 Gas Used by Txn:
35,923
L1 Fee Scalar:
0

Other Attributes:
Txn Type: 2 (EIP-1559) Nonce: 94 Position In Block: 135
Input Data:

Private Note:
To access the Private Note feature, you must be Logged In
Invoked Transactions
  Type Trace Address From   To Value Gas Limit
AA Txn Hash Method Position From Internal Txns Token Txns NFT Txns Txn Fee (ETH) Gas Limit
Transaction Receipt Event Logs
438
Address
0x8768c789c6df8af1a92d96de823b4f80010db294 (Seamless Protocol: Governor Short Proxy)
Name

ProposalCreated (uint256 proposalId, address proposer, address[] targets, uint256[] values, string[] signatures, bytes[] calldatas, uint256 voteStart, uint256 voteEnd, string description)View Source

Topics
  • 0 0x7d84a6263ae0d98d3329bd7b46bb4e8d6f98cd35a7adb45c274c8b7fd5ebd5e0
Data
  • proposalId (uint256) :88361888157421848022762560333612898952555172089004355994399727441859041539641
  • proposer (address) :0x6D0C9128165A7BF2A2072319129D49D8F458fe0A
  • targets (address[]) :0x57460DC21bf1574b8e6E00D372b8Ca5Ec41b3955
    0x785c979EE8709060b3f71aEf4f2C09229DB90778
    0x1C7a460413dD4e964f96D8dFC56E7223cE88CD85
  • values (uint256[]) :0
    0
    0
  • signatures (string[]) :


  • calldatas (bytes[]) :1E83409A000000000000000000000000639D2DD24304AC2E6A691D8C1CFF4A2665925FEE
    1E83409A000000000000000000000000639D2DD24304AC2E6A691D8C1CFF4A2665925FEE
    A9059CBB000000000000000000000000A1B5F2CC9B407177CD8A4ACF1699FA0B99955A2200000000000000000000000000000000000000000001A784379D99DB42000000
  • voteStart (uint256) :1743115593
  • voteEnd (uint256) :1743374793
  • description (string) :# [SIP-44] Protocol Rewards Refresh Q2 2025 ## Summary This proposal seeks to extend platform reward emissions beyond their current end date of March 31, 2025 through Q2 2025 (April 1 - June 30). The proposal maintains our quarterly cadence while preserving monthly flexibility for adjustments. The total budget of 2 million SEAM will be sourced from the short governor timelock and master emissions vesting contracts. The proposed quarterly reward allocations are: 1. **Seamless Vaults & Leverage Tokens (625,000 SEAM)** - Incentivize growth of Seamless Vaults on Morpho - Support upcoming launch of [Leverage Tokens](https://x.com/SeamlessFi/status/1902451468415987889) 2. **Legacy Lending Platform (625,000 SEAM)** - Primarily distributed as esSEAM to incentivize long-term alignment - Maintain competitive yields for lenders and borrowers - Pending the result of [this](https://snapshot.box/#/s:seamlessprotocol.eth/proposal/0x901e2aed03877d64a0414496f69b7febb76272cf4a1526c6d3b8813dac455074) Snapshot Labs vote, these rewards may be returned to the DAO in accordance with the sunset plan timeline. 3. **Safety Module (375,000 SEAM)** - Encourage protocol security through staking incentives - Strengthen alignment between token holders and protocol safety 4. **Strategic Growth Reserve (375,000 SEAM)** - Flexible budget for emerging opportunities - Usage subject to community approval via Snapshot vote ## Context and Motivation This proposal aligns with the broader token emissions strategy outlined [here](https://seamlessprotocol.discourse.group/t/gp-7-expanding-protocol-reward-categories-increasing-token-emission-budget-for-seamless/605). NOTE: the GP7 proposal was already discussed and approved via governance process, snapshot labs results [here](https://snapshot.box/#/s:seamlessprotocol.eth/proposal/0x113a9f75eb623fcccdc2b4400ecb0e125b95c0085bf0c8b44c5f136b27c29c2d). As such, this current proposal will move straight to onchain governance. The key drivers for continuing emissions are: 1. **Market Timing:** The current macro environment and crypto market sentiment create an opportune moment to accelerate growth and capture market share through strategic token emissions. 2. **Product Evolution:** Our expanding product suite - including new markets, ILMs, and innovative offerings - requires competitive incentives to drive initial adoption and sustainable usage. 3. **Strategic Token Utilization:** With approximately 55% of token supply [reserved for rewards](https://docs.seamlessprotocol.com/governance/seam-tokenomics), front-loading emissions during this growth phase allows us to: - Maximize market presence and TVL capture - Establish Seamless as the premier lending platform on Base - Build toward sustainable fee generation and token value accrual - Create a framework for gradual emissions reduction over time The reward schedules will be implemented based on recommendations from ecosystem partners and contributors. While this represents a maximum quarterly budget, actual emissions may be lower based on market conditions and performance metrics. ## Resources & References - [Governance Discussion](https://seamlessprotocol.discourse.group/t/gp-7-expanding-protocol-reward-categories-increasing-token-emission-budget-for-seamless/605) - [Proposal Implementation](https://github.com/seamless-protocol/gov-proposals/tree/main/proposals/sip_44) - Built using [Seamless Governance Proposals tools](https://github.com/seamless-protocol/gov-proposals)
:

:

:

:

:

:

:
:

:

:

:

                
Authority Delegated Address Nonce Validity yParity r s
Loading...
Loading
Loading...
Loading

A transaction is a cryptographically signed instruction that changes the blockchain state. Block explorers track the details of all transactions in the network. Learn more about transactions in our Knowledge Base.