Beam 백서

bitpro가 원문에서 글자만 모은 내용이에요. 표·그림·수식은 빠지거나 깨질 수 있어요. 전체 6쪽 중 3쪽

ssets or token. Execute a trade : Trade assets and tokens between two profiles securely Roadmap Throughout the coming months, we’ll be releasing additional features that will help you provide a more complete marketplace experience, with features ranging from programmatic offers, auctions and extensive filtering options to allow you to create a full-fledged in-game marketplace solely by relying on the Beam marketplace. 🛠️ Feel like something is missing, and needs to be prioritized? Let’s have a chat through build@onbeam.com ! Using policies Execute a trade ## /token/gas BEAM Token Gas token BEAM as a gas token fuelling Beam Network activity Being the native gas token on the Beam Network, BEAM is the only acceptable form of payment for transaction fees on the Beam Network. To use the Beam Network, users need BEAM to interact with it (e.g. sending BEAM to another address or interacting with smart contracts on the Beam Network). In this way, BEAM functions as the fuel powering every transaction and the interaction with every application on the Beam Network, including every dApp built on top of it. Introduction Validate and secure ## /token/security BEAM Token Validate and secure BEAM to validate and secure the Beam Network After the Horizon upgrade , BEAM will be used to secure the Beam Network, and be required to validate and propose blocks on the mainnet of the Beam Network. Validators that fulfill the network criteria to stake their BEAM will be able to run a Beam node and propose blocks on the Beam Network. BEAM holders who do not wish to run their own node, will be able to contribute to securing the Beam Network by delegating BEAM tokens to validators running Beam nodes. Thus, BEAM powers the Beam Network and everything that occurs on it. The work that validators do, with the assistance of delegators, and the BEAM they stake, will seek to keep the Beam Network secure and free of centralized control. Validators and delegators that do this work for the benefit of the Beam Network and all smart contracts built on top of it, may be rewarded with BEAM and other tokens from various sources, such as from gas fees and other Beam protocols. Further info about the Horizon upgrade is available here. Gas token Governance ## /token/horizon BEAM Token Horizon Horizon The Horizon upgrade is a transformative milestone for the Beam Network, marking its transition to a proof-of-stake (PoS) blockchain. This upgrade enhances the network’s decentralization, scalability, and security, empowering users to actively participate in its validation and governance. Key features of the Horizon upgrade include: Introduction of Beam Nodes : Enables users to secure the network by running or delegating to validators. Proof-of-Stake Consensus Mechanism : Allows permissionless validation, making the network more accessible and efficient. Node Token Integration : Introduces an ERC-721 token as a key requirement for operating Beam Nodes. Reward Distribution : Validators and delegators can earn rewards, including transaction fees, protocol fees, and grants. The Horizon upgrade sets the stage for a radically decentralized and user-driven ecosystem, ensuring Beam’s evolution as a Layer 1 blockchain. Burning ## /token/governance BEAM Token Governance BEAM as a governance token As a governance token, BEAM may grant holders the ability to participate in decisions about the future of Beam protocols and to co-approve or veto certain decisions made by DAO-adjacent entities, such as the Beam Foundation. See more info about BEAM governance here . Validate and secure Payments ## /token/payments BEAM Token Payments BEAM as a means of payment BEAM is used as a significant medium of exchange within the Beam ecosystem. It is increasingly accepted as a form of payment by various applications, such as the NFT marketplace Sphere, and dApps building on Beam. Governance Distribution ## /token/distribution BEAM Token Distribution BEAM distribution Since its inception, the BEAM emissions schedule has been subject to changes, partially due to token burns and partially due to tokens being made subject to a longer lock-up period than what was originally intended. More info about the emissions schedule to come. Payments Burning ## /token/burning BEAM Token Burning Burning BEAM BEAM can be destroyed through a process typically referred to as ‘burning’. When BEAM is burned, it is sent to specific smart contracts resulting in the BEAM being permanently taken out of circulation. Burns result in a decrease in the circulating and maximum total supply of BEAM. Beam protocols may be configured to direct part of the protocol fees to ‘burn smart contracts’. More info about this will be published in connection with the Horizon upgrade . Additionally, anyone may at any time choose to burn all or some of their BEAM. Distribution Horizon ## /governance/constitution Governance Constitution BEAM Governance Constitution The BEAM Governance Constitution establishes a framework for BEAM governance, including an outline of the process for introducing and voting on a Beam Improvement Proposal (BIP). Read the BEAM Governance Constitution here . Introduction Discussions ## /governance/discussions Governance Discussions Participate in BEAM Governance discussions The Beam Governance Forum is the place where BEAM governance discussions will mainly be taking place. The Beam Governance Forum serves as a collaborative space for discussions and contributions that drive the development of the Beam ecosystem, including the Beam Network, other Beam protocols and the BEAM token. Here, the Beam community is invited to take part in shaping the future of the Beam ecosystem. The platform consists of a number of categories that encompass a broad range of Beam related topics. Each category has a pinned ‘About’ post that provides further information about its purpose. The ‘Latest’ tab will show you the most recent conversations. If you are new to the Beam Governance Forum, you may join the discussions by doing the following: Create your profile : Complete your profile setup with an avatar and a concise biography detailing your expertise and interests. Review existing discussions : Familiarize yourself with the Beam Governance Forum by browsing through threads that interest you. This will give you insight into ongoing discussions and areas of focus within the community. Contribute thoughtfully : Engage with the community through posts and responses. Note that a user must hold no less than 25,000 BEAM to post a thread in the proposal category, and that any other interaction (such as posting a thread in another category or a comment in any category) requires at least 1 BEAM. Read about the governance process : To learn more about the governance process, you can read the Beam Governance Constitution . Read more about participation in governance in the information & policies section of the BEAM Governance Forum. Constitution Proposals and voting ## /governance/proposals Governance Proposals and voting Creation of Governance proposals and voting A user must hold at least 25,000 BEAM in order to post a proposal in the proposal category of the Beam Governance Forum. When creating a new proposal, a user is recommended to use the added template as a base for the proposal. See the Beam Governance Constitution for further information about the proposal process. Submitting a Proposal to a BIP Vote A proposal may be submitted as an official Beam Improvement Proposal (BIP) vote at https://vote.onbeam.com , subject to the following criteria: Discussion period. The proposal must, at a minimum, be subject to a 2-day review and discussion period counting from the time it is first published on the Governance Forum. If the content of the proposal is materially changed, then the requirement to have a minimum 2-day review and discussion period shall restart, including for each successive time a material change is made. The author of the proposal may choose a longer discussion period. BEAM ownership. The user submitting the proposal must hold at least 750,000 BEAM. Clarity regarding the vote. It must be clearly stated what the proposal is asking the BEAM tokenholders to vote on, including what is being proposed and what the outcome of a ‘for’ vote will result in. Materially similar proposals. Any proposal submitted must not be materially similar in content or subject matter to a proposal that was subject to a BIP vote within the past 6 months and that has been rejected. “Materially similar” in this context refers to a proposal that addresses the same issue or matter, contains substantially similar solutions or outcomes, and presents only minor alterations to the previously rejected proposal. Duration of BIP votes A BIP vote shall have a duration of a minimum of 2 days. The author of the proposal may choose a longer voting period when creating the proposal. If during the voting period it becomes impossible to cast a vote because of a wide-ranging non-operability of the voting software or the relevant blockchain system, the vote shall be re-done. Voting rights Persons that were BEAM tokenholders at the time of the last recorded block number on the relevant voting blockchain system prior to the creation of a BIP vote, and who have held their BEAM on such a voting blockchain system, shall have the right to participate in a BIP vote. Each BEAM on a voting blockchain system carries an equal number of votes, unless otherwise follows from the relevant smart contract systems. Beam DAO-adjacent entities shall have a provision in their governing documents that prohibits them from participating in any BIP vote. Quorum and majority requirements A quorum for a vote on a BIP vote is reached if voting power equaling 1% or more of the circulating supply of BEAM, at the time of the last recorded Beam Network block number prior to the end of the most recent quarter (first quarter of a year ending at 24:00 UTC on 31 March) preceding the creation of the relevant vote, has been used to vote on the relevant proposal. All BIP votes require a simple majority (more than 50%) of the BEAM votes cast to succeed, unless otherwise follows from the relevant smart contract systems. Any BIP vote that either fails to (a) meet the quorum requirement or (b) obtain the relevant majority requirement, shall be considered a rejected proposal. However, if a BIP vote does not form a quorum, a repeated BIP vote may take place if the author(s) of the proposal consents and the proposal received more votes ‘for’ than ‘against’ during the BIP vote that did not meet the quorum requirements. Discussions DAO - Adjacent Entities ## /governance/dao-entities Governance DAO - Adjacent Entities DAO-adjacent entities Currently, Beam Foundation and its subsidiaries, function as so-called ‘DAO-adjacent entities’ in relation to BEAM DAO. The Beam Foundation is a memberless non-profit foundation based in the Cayman Islands, dedicated to the objectives set out in its governing documents, including the decentralization, adoption and security of the Beam ecosystem. It has a mission to make the Beam ecosystem a home for all the dApp needs of users, where users can interact with dApp related blockchain elements and other applications in a frictionless and user-friendly manner. It being memberless means that there are no ‘owners’ of it, making it compatible with crypto values, such as decentralization. As it has no members (shareholders) and is non-profit, it cannot distribute dividends - any assets it owns may be deployed solely towards furthering the growth and development of the Beam ecosystem in accordance with the scope set out in law and its governing documents. DAO-adjacent entities, such as the Foundation group entities, enable a DAO to simply be a DAO, while pushing the largest liability vectors (which would be business activities) to limited liability entities that are able to comply with regulations. Beam DAO and tokenholders will not be controllers or managers of the Foundation group (the entities are sovereign), but the Bylaws, Memorandum of Association and Articles of Association mandate certain checks and balances on the Foundation group for the purpose of holding the Foundation group accountable, as follows: Onchain : If applicable, by use of certain programmatic, smart contract-based features, BEAM holders can give onchain feedback to, and provide onchain vetoes against, certain decisions by a Foundation group company. Offchain : By (i) limiting the scope of operation of the Foundation group (i.e., the Foundation group can only operate within the parameters set out in these documents), (ii) having a co-approval right in relation to, and vetoing against, certain decisions by a Foundation group company, or (iii) enabling BEAM holders to seek enforcement actions against a Foundation group company or certain personnel via an ‘Emergency Supervisor’ in case of an “Adverse Event” (as defined in the documents). Transparency : By requiring the Beam Foundation to publish and keep publicly available the governing documents, certain reports (including treasury reports) and information as referred to in the documents. The governing documents will remain publicly available (and up-to-date) at all times to enable the Beam community to continue to exert checks and balances on the Foundation group. The structuring of the Beam Foundation and its subsidiaries is inspired by this article about ‘BORGs’ and Metalex’s work on ‘BORG’ formation . Proposals and voting ## /chain/get-started/gas Chain Get Started Gas Token Gas Token The BEAM token is the native currency used within the Beam Network to pay for transactions. This concerns every single transaction that may occur on the network from simply transferring funds to deploying smart contracts. How to get BEAM The BEAM token originates on the Ethereum blockchain . It can be obtained from various centralized- and decentralized exchanges , and can be bridged from Ethereum to Beam (and back). Network Fees The gas paid for each transaction will then be divided in two categories: Validator : Those who are validating and securing the network, and thereby ensuring its safety and performance will receive a reward in BEAM tokens in return. Burn : Part of the transaction fee used as gas will be burned and therefore permanently find their way out of circulation causing a deflationary effect. The precise distribution ratio between these categories remains under consideration. Fee Configuration genesis.json { "feeConfig" : { "gasLimit" : 8000000 , "targetBlockRate" : 2 , "minBaseFee" : 1000000000000 , "targetGas" : 50000000 , "baseFeeChangeDenominator" : 72 , "minBlockGasCost" : 0 , "maxBlockGasCost" : 100000000 , "blockGasCostStep" : 10000000 } } These parameters collectively regulate the gas token economics within Beam, influencing fees and transaction processing on the network. To learn more details about these settings, view https://docs.avax.network/build/subnet/upgrade/customize-a-subnet#fee-config . Connecting to Beam Build on Beam ## /chain/builder/starter-guide Chain Build on Beam Starter Guide Beam Starter Guide Beam is the right place for dApps and dApp developers that are looking for speed, quick settlement, security, and the open-ended possibilities that Beam unlocks. This guide will help you to get your Beam journey started. Before you begin developing on Beam, there are several prerequisites you’ll need to understand. Knowledge of the Solidity programming language Understanding of blockchain fundamentals Grasp of smart contract basics Once you’re equipped with these, you’re ready to set up your development environment. In the upcoming sections, we’ll walk you through the process of getting your development toolkit ready, creating your first smart contract, testing it, and finally deploying it on the Beam Network. Beam is fully EVM-compatible, this means that building on Beam’s execution layer is just like building on Ethereum in that developers can: Connect with the same wallets, deploy the same smart contract source code, use the same tooling, and more. Building a new dApp on Beam? Move your existing dApp to Beam How to Access Beam? You can access Beam through MetaMask, by defining a custom network. Go to MetaMask, log in, click the network dropdown, and select ‘Custom RPC’. For Beam RPC settings, consult this guide . Build on Beam Accounts ## /chain/builder/accounts Chain Build on Beam Accounts Accounts: Implementing Smart Contract Wallets Managing user accounts in your Beam application involves more than just tracking dApp users. By incorporating smart contract wallets, or ‘account abstraction’ (following EIP-4337 ), you can offer your users a more interactive and richer web3 experience. In the Beam Network, we utilize smart contracts from Openfort , which provide you with the tools to offer your users greater flexibility and security with their accounts. Here’s how you can implement different levels of control and autonomy over users’ gaming assets: Fully Managed Experience For users who want a seamless web3 experience without dealing with any blockchain complexities, you can fully manage their in-app wallets. They just enjoy using the dApp while the backend operations, including asset management, are handled by you, the developer. Co-managed Ownership Some users may seek both ownership and assurance. You can offer them an option to share their backup key with you and Beam. Using techniques such as key fragmentation or multi-signature approach, you can provide a balance of control and security to these users. Social Recovery Feature For users who prefer to trust their friends for account recovery, you can implement a social recovery feature. This feature requires the user to designate a minimum of three friends who can assist in account recovery if needed. User-Owned Accounts For the crypto-savvy users who want total control, you can offer the ability to link an Externally Owned Account (EOA) to their dApp account. While this may result in them signing many transactions, it provides total ownership. Another option is for users to move their assets into their Beam account, covering the initial gas fee, while you agree to handle the gas costs when they move them out, ensuring a smoother in-app experience while maintaining user control. In this way, user accounts in your Beam application serve as more than just player profiles; they’re gateways to an immersive blockchain experience. From AA wallets to asset management, implement the level of control that best suits your user’s needs, and bring them into the future of dApps with Beam. Starter Guide APIs ## /chain/builder/apis Chain Build on Beam APIs APIs Beam API To interact with the Beam Network, we offer you a powerful API accessible via HTTP or through dedicated server-side SDKs. Currently, SDKs are available for Node.js (TypeScript) and C# (RestSharp). If you are looking for support in another language, please contact us. To learn more about the Beam API, please see the dedicated Beam SDK docs , which include guides, references, and examples. Beam Subnet-EVM API The Subnet-EVM APIs mirror the Coreth APIs with one exception - Avalanche Specific APIs, identifiable by the ‘ avax. ’ prefix. In addition, Subnet-EVM supports standard Ethereum APIs, increasing its applicability. For in-depth information about Coreth APIs, please refer here . Moreover, Subnet-EVM introduces unique APIs not present in Coreth: eth_feeConfig : Subnet-EVM comes with an API request for getting fee config at a specific block. You can use this API to check your activated fee config. ( Details ) eth_getChainConfig : eth_getChainConfig returns the Chain Config of the blockchain. This API is enabled by default with internal-blockchain namespace. ( Details ) eth_getA
프로젝트로 돌아가기