bitpro가 원문에서 글자만 모은 내용이에요. 표·그림·수식은 빠지거나 깨질 수 있어요. 전체 4쪽 중 2쪽
125">Ratio</th><th>Purpose</th></tr></thead><tbody><tr><td>Community </td><td>58%</td><td>The purpose of community allocations in tokenomics is to activate the ecosystem and incentivize participation.<br>(e.g. maximizing network effects, Encouraging governance participation, building long-term loyalty)</td></tr><tr><td>Foundation</td><td>15%</td><td>Supports long-term project development, ecosystem growth, and community.</td></tr><tr><td>Core Contributor</td><td>13%</td><td>Rewards key team members and early contributors for ongoing contributions and innovation.</td></tr><tr><td>Investor</td><td>12%</td><td>Provides funding for investors and strategic partners.</td></tr><tr><td>Meme Treasury</td><td>2%</td><td>The Meme Treasury funds community incentives, supports creators, ensures ecosystem stability, and engages in fun activities</td></tr></tbody></table>
# Transaction Fees & Burn
How gas fees are priced on MemeCore, which part of every fee is burned, and how anyone can verify the burned amount on-chain.
***
## Transaction Fees & Burn
Every transaction on MemeCore pays a gas fee in **$M**. MemeCore implements the EIP-1559 fee market from the genesis block, so each fee is split into two parts:
* a **base fee**, set by the protocol and **burned**, and
* an optional **priority fee (tip)**, set by the sender and paid to the PoM reward contract.
```
gas fee = gasUsed × effectiveGasPrice
effectiveGasPrice = baseFeePerGas + priorityFeePerGas
burned per tx = gasUsed × baseFeePerGas
```
{% hint style="info" %}
**Example** — A simple $M transfer uses 21,000 gas. At the minimum base fee of 15 Gwei, the transaction burns `21,000 × 15 Gwei = 315,000 Gwei = 0.000315 M`. Any priority fee is paid to the PoM reward contract on top of that.
{% endhint %}
### Base fee
The base fee is the minimum price per unit of gas required for a transaction to be included in a block. It is not chosen by users: the protocol calculates it for every block from the gas used by the previous block.
* If the previous block used **more** gas than the target, the base fee goes **up**.
* If it used **less** gas than the target, the base fee goes **down**.
* The change is capped at **±12.5% per block**.
* The base fee never drops below the **minimum base fee** (see [Fee parameters](#fee-parameters)).
```
gasTarget = gasLimit / ElasticityMultiplier
delta = parentBaseFee × (parentGasUsed − gasTarget) / gasTarget / BaseFeeChangeDenominator
nextBaseFee = max(parentBaseFee + delta, MinBaseFee)
```
{% hint style="info" %}
This is a simplified version. See [EIP-1559](https://eips.ethereum.org/EIPS/eip-1559) and [`consensus/misc/eip1559/eip1559.go`](https://github.com/memecore-foundation/Go-MemeCore/blob/master/consensus/misc/eip1559/eip1559.go) in the MemeCore client for the exact implementation.
{% endhint %}
### Priority fee
The priority fee (tip) is an optional amount on top of the base fee. It is **not burned**. Priority fees flow into the reward contract together with the block reward and are distributed to validators and delegators.
### Fee burn
#### What is burned
| Fee component | Burned? | Since |
| -------------------------------------- | ------------------------------------------------- | -------------------- |
| Base fee (`gasUsed × baseFeePerGas`) | **Yes, 100%** | Genesis (block 0) |
| Blob fee (`blobGasUsed × blobBaseFee`) | **Yes, 100%** | CanPraTree hard fork |
| Priority fee (tip) | No — paid to the PoM reward contract (`coinbase`) | — |
#### How the burn works
The base fee of every block is deducted from the sender and **is not credited to any address** — not to the reward contract, not to a treasury, and not to a burn address such as `0x…dEaD`. The amount simply leaves the circulating supply at the protocol level, in the same way as on Ethereum after the London upgrade.
```
burned per block = block.gasUsed × block.baseFeePerGas (+ blobGasUsed × blobBaseFee after CanPraTree)
```
{% hint style="warning" %}
**Blob fees** — Blob-carrying transactions (EIP-4844) are supported from the CanPraTree hard fork, and their blob fee is burned as well. As of the latest measurement no blob transactions have been observed on mainnet, so blob fees have not yet contributed to the burned total.
{% endhint %}
### Fee parameters
<table><thead><tr><th width="265.8984375">Parameter</th><th width="131.39453125">Value</th><th>Notes</th></tr></thead><tbody><tr><td>Fee market</td><td>EIP-1559</td><td>Active from genesis (<code>LondonBlock = 0</code>)</td></tr><tr><td>Minimum base fee</td><td><strong>15 Gwei</strong></td><td>Since GasTree hard fork. <strong>1,500 Gwei</strong> before</td></tr><tr><td>Max base fee change per block</td><td><strong>±12.5%</strong></td><td><code>BaseFeeChangeDenominator = 8</code></td></tr><tr><td>Elasticity multiplier</td><td><strong>2</strong></td><td>Gas target = gas limit ÷ 2 (<code>DefaultElasticityMultiplier</code>)</td></tr><tr><td>Base fee destination</td><td>Burned</td><td>Not credited to any address</td></tr><tr><td>Blob fee destination</td><td>Burned</td><td>Since CanPraTree</td></tr></tbody></table>
Source: [`params/protocol_params.go`](https://github.com/memecore-foundation/Go-MemeCore/blob/master/params/protocol_params.go), [`consensus/misc/eip1559/eip1559.go`](https://github.com/memecore-foundation/Go-MemeCore/blob/master/consensus/misc/eip1559/eip1559.go) in the MemeCore client.
### Verify the burn yourself
Because burned fees are not sent to any address, you verify the burn by recomputing it from block headers rather than by checking a balance. Every MemeCore block header includes `gasUsed` and `baseFeePerGas`.
```bash
RPC=https://rpc.memecore.net
BLOCK=7850000
# Burned in a single block (wei)
GAS=$(cast block $BLOCK --field gasUsed --rpc-url $RPC)
FEE=$(cast block $BLOCK --field baseFeePerGas --rpc-url $RPC)
cast from-wei $(echo "$GAS * $FEE" | bc) # → amount in M
```
```javascript
import { JsonRpcProvider, formatEther } from "ethers";
const provider = new JsonRpcProvider("https://rpc.memecore.net");
async function burnedInRange(from, to) {
let total = 0n;
for (let n = from; n <= to; n++) {
const b = await provider.getBlock(n);
total += b.gasUsed * (b.baseFeePerGas ?? 0n);
}
return formatEther(total); // in M
}
```
# Connect to MemeCore
## | MemeCore Mainnet
<table><thead><tr><th width="255">Name</th><th>Value</th></tr></thead><tbody><tr><td>Network name</td><td>MemeCore</td></tr><tr><td>RPC</td><td><a href="https://rpc.memecore.net/">https://rpc.memecore.net/</a><br><br><strong>Privacy statement:</strong><br>We do not log, store, or track any user data without consent with exception of data publicly available on chain.</td></tr><tr><td>Web Socket</td><td>wss://ws.memecore.net</td></tr><tr><td>Chain ID</td><td>4352</td></tr><tr><td>Symbol</td><td>M</td></tr><tr><td>Block Explorer</td><td><a href="https://memecorescan.io/">https://memecorescan.io/</a></td></tr></tbody></table>
## | Insectarium Testnet
<table><thead><tr><th width="255">Name</th><th>Value</th></tr></thead><tbody><tr><td>Network name</td><td>Insectarium Testnet</td></tr><tr><td>RPC</td><td><a href="https://rpc.insectarium.memecore.net/">https://rpc.insectarium.memecore.net</a><br><br><strong>Privacy statement:</strong><br>We do not log, store, or track any user data without consent with exception of data publicly available on chain.</td></tr><tr><td>Web Socket</td><td>wss://ws.insectarium.memecore.net</td></tr><tr><td>Chain ID</td><td>43522</td></tr><tr><td>Symbol</td><td>M</td></tr><tr><td>Block explorer</td><td><a href="https://insectarium.blockscout.memecore.com/">https://insectarium.blockscout.memecore.com/</a></td></tr><tr><td>Faucet</td><td><a href="https://faucet.memecore.com/insectarium">https://faucet.memecore.com/insectarium</a></td></tr></tbody></table>
# Consensus
Here is the current architecture of the MemeCore mainnet. The Meme 2.0 structure is currently under development. Please refer to this information when accessing the current structure.
### | Consensus Architecture (PoM) <a href="#or-consensus-architecture-pom" id="or-consensus-architecture-pom"></a>
<figure><img src="https://docs.memecore.com/~gitbook/image?url=https%3A%2F%2F3586299913-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FyEyVKW0jNX3Zzer1FZWg%252Fuploads%252FR9ABrS8tmglHGht4SXyq%252Fimage.png%3Falt%3Dmedia%26token%3Dcdf12d29-9e97-4d47-874f-1c1600059e50&width=768&dpr=4&quality=100&sign=1c593db1&sv=2" alt=""><figcaption></figcaption></figure>
**Epoch**
Epochs are the concept are introduced in addition to Ethereum's PoS.
The Epoch is a parameter written in the configure file in the Geth code, and can be modified when necessary. The initial setting of Epoch could be one day.
During the Epoch, the selected validators produce blocks with a PoA consensus algorithm, which is similar to [Clique](https://eips.ethereum.org/EIPS/eip-225). After the end of each epoch, a new set of validators will be selected from the governance delegation contract.
**Consensus time**
The new designed consensus can decrease block time and therefore increase their transaction throughput. The current network's block time is 7 seconds.
**Reward generation**
A total of 30 $M tokens are minted with each block by the core Geth code and allocated to the reward contract. The number of tokens vested as rewards is subject to future modification through a hard fork, contingent upon community consensus.
**Slashing (TBA)**
We've implemented a slashing mechanism tasked with overseeing network performance metrics, including block generation counts, node downtime, and various other critical parameters. The designated Monitor Role is responsible for relaying this performance data to the slashing contract. Should the performance fall short of the established criteria, the slashing contract is programmed to execute the `Slash` function within the Validator Candidate Contract.
This punitive process unfolds in two distinct phases: Firstly, a deduction is imposed on the $M tokens staked during registration, serving as a direct financial penalty. Secondly, the penalized validator node is excluded from participation in the ensuing validation round. This exclusion inherently leads to a reduction in the $M rewards that the validator would have accrued.
### | Contract structure <a href="#or-contract-structure" id="or-contract-structure"></a>
#### Validators Registration <a href="#validators-registration" id="validators-registration"></a>
* Any EOA address can register as a validator candidate by calling the `register()` function and staking a fixed amount of $M.
* Only EOAs (not contract addresses) that haven't previously registered can use the registration function. A `registrationFee baseAmount` must be included in the transaction, and this fee can later be adjusted by the governance contract.
* The validator list has a maximum limit, initially set to 100 validators.
* Validators can delist themselves by calling the `quit` function, receiving a refund. Currently, the staked $M is refunded immediately, but a lock period of 1 month may be added to the refund process.
#### Delegation <a href="#delegation" id="delegation"></a>
**$M Delegation**
Both EOA and contract addresses can stake $M on the Validator Delegating Contract by calling the `stakeM` method and specifying the staked amount in the transaction.
**Meme Delegation**
EOA and contract addresses can stake Meme tokens by invoking the `stakeMeme` method, but they must first approve the transaction. The Meme tokens eligible for delegation are listed in the MemeWhiteList, which can be extended via the Governance contract.
**GetCandidates**
The Validator Delegating Contract provides the `getFirstFewValidators` method to query the validator set. In Phase I, the ranking is determined by a fixed formula. In Phase II, this formula will integrate native oracle prices to adjust rankings.
**Reward**
The reward distribution contract manages how rewards are divided among validators and delegators. Each M block reward is split: one part goes to the producer and is shared equally among active validators, while the other part is distributed to delegators based on a weighted formula. In Phase I, the formula is static, but in Phase II, it will use oracle-based price feeds for dynamic reward distribution. The last portion is given to validators and delegators if their supported validator produces the block.
**Claim**
To claim $M rewards, users must send a `stake(0)` or `withdraw(0)` transaction to the Reward Distribution Contract. The same process applies for ERC-20 tokens. Additional utility functions for claiming rewards can be added to improve front-end interaction.
**ERC-20 Vault**
The ERC-20 Vault will store 5% of the total supply from each ERC-20 token on MemeCore. Before minting, the ERC-20 token deployer must call the `waitlist` function in the vault, ensuring the token contract is open source and secure through multisig approval. The vault operates with a vesting algorithm, distributing tokens to users based on their staking in the Validator Delegating Contract, initially over a period of 1,000 days, which can later be changed by governance.
# Validator
### | Overview <a href="#or-overview" id="or-overview"></a>
MemeCore Chain operates with a network of validators using a Proof of Meme (PoM) consensus mechanism, designed to enable short block times and reduced transaction fees. Validators with the highest staked amounts have the chance to produce blocks. Security, stability, and finality are maintained through slashing mechanisms like double-sign detection.
The chain selects the top 7 active validators for block production based on staking rankings. Under the MemeCore Mainnet PoSA configuration, the validator set is refreshed at epoch boundaries, every 12,345 blocks (approximately 24 hours, assuming a 7-second block interval). At each epoch boundary, the validator set is retrieved from the Validator Management Contract and recorded in the block header. To qualify as a candidate for election, validators must first stake the required amount of assets into the system contract.
### | What are Validators? <a href="#or-what-are-validators" id="or-what-are-validators"></a>
Validators on the MemeCore network play a key role in maintaining security and producing blocks using the PoM consensus mechanism. These nodes handle transaction packaging and block validation, ensuring the stability of the network. In return for their efforts, validators earn $M tokens as rewards for their contribution to securing the system.
### | Economics <a href="#or-economics" id="or-economics"></a>
Validators and delegators earn two types of rewards: $M tokens and ERC-20 tokens. For instance, if the reward for producing a block is 1,000 $M, these tokens aren’t given directly to the block proposer. Instead, they are distributed proportionally among validators and delegators based on their respective stakes in the network.
Example:
Copy
```
M staker shares: 1,000 * 75% = 750 M
Meme coin staker shares: 1,000 * 24% = 240 M
Block producer shares: 1,000 * 1% = 10 M
The M staker commission rate is: 10%
The meme coin staker commission rate is: 15%
Validator rewards: (his staking reward in $M and ERC-20) + ($M and ERC-20 commission) + (10 $M for the block producer)
Delegators get: (his staking reward in $M and ERC-20) - ($M and ERC-20 commission)
```
### | Running a Validator Node <a href="#or-running-a-validator-node" id="or-running-a-validator-node"></a>
**Hardware Requirements**
The following are the minimum hardware requirements:
* CPU with 2+ cores
* 4GB RAM
* 200GB free storage space
* 8 MBit/sec download Internet service
### | Validator Management Contract Address <a href="#or-validator-management-contract-address" id="or-validator-management-contract-address"></a>
Validator management contract:`0x1234000000000000000000000000000000000002`
### | $M Staking <a href="#or-usdm-staking" id="or-usdm-staking"></a>
Send at least 7,000,000 $M from your miner address to the `register` method of the validator contract without any parameters. The staked $M will be fully refunded when quit.
# Staking/Delegating
MemeCore Chain also has an additional built-in reward contract to distribute non-$M rewards to validators and delegators.
### | Validator Election <a href="#or-validator-election" id="or-validator-election"></a>
Validators are divided into 2 different roles:
* **Active Validators:** These are the top 7 validators at any given time, selected based on their ranking. They have the ability to produce blocks and earn block rewards. The number 7 is set as the `validatorCount` in the contract, but this can be modified by the governance system in the future.
* **Candidate Validators:** These are the validators ranked below the top 7. They are not eligible to produce blocks or earn block rewards, but they can still receive delegations to improve their ranking for the next round of selection.
Rankings are updated every 10 blocks, determined by the total amount of tokens staked by delegators.
### | System Contract <a href="#or-system-contract" id="or-system-contract"></a>
* **System Reward Contract:** Delegators can stake $M and meme coins through this contract to help validators achieve a top 7 ranking. It acts as a vault, gathering rewards from each block and distributing them to delegators according to system rules.
* **Additional Reward Contract:** This contract allows external project teams to store ERC-20 rewards, which are then distributed to delegators using the same formulas as the system rewards.
There are several built-in contracts (i.e., system contracts) to support staking operations, allowing delegators to stake $M and meme coins.
* **Validator Set Contract:** Responsible for electing validators periodically, this contract also holds validator rewards temporarily.
### | Reward Distribution <a href="#or-reward-distribution" id="or-reward-distribution"></a>
The 7 active validators equally share 99% of the rewards, with the validator that produces the block receiving an extra 1%. Of the rewards received by validators, 25% is allocated to delegators who staked meme coins, and 75% to those who staked $M Token. The remaining 1% reward is a bonus for the current block-producing validator and their respective delegators.
### | Validator Operations <a href="#or-validator-operations" id="or-validator-operations"></a>
**Register Validator**
To ensure the security of the network, becoming a validator on the MemeCore Chain requires a minimum self-delegation of $M. $M holders can initiate a `RegisterValidator` transaction with the Validator Set contract to become a validator.
**Reward Collection**
When delegators claim their received rewards, a certain percentage is deducted as a fee for the validator. Validators can withdraw these fee rewards.
### | Delegator Operations <a href="#or-delegator-operations" id="or-delegator-operations"></a>
Delegators are holders of $M or Meme coins who stake their tokens with a validator to share in the rewards. They have the flexibility to choose any active or candidate validator, switch between them, undelegate their tokens, and claim rewards at any time. In exchange, they receive an `Xtoken (X$M or Xmemecoin)` as proof of their delegation, which can be used within the Memecore ecosystem.
<figure><img src="https://docs.memecore.com/~gitbook/image?url=https%3A%2F%2F3586299913-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FyEyVKW0jNX3Zzer1FZWg%252Fuploads%252F8MhpW7nWyLvOHCDJXBtk%252FDelegator%2520Operations.png%3Falt%3Dmedia%26token%3Dce587bb0-853e-457e-8c20-4290bddf220c&width=768&dpr=4&quality=100&sign=15a755fa&sv=2" alt=""><figcaption></figcaption></figure>
# Multi-reward
### | Reward distribution & Block Proposer Selection Method <a href="#or-reward-distribution-a프로젝트로 돌아가기