Evmos chain

Overview

Evmos

Evmos is a scalable, high-throughput Proof-of-Stake blockchain that is fully compatible and interoperable with Ethereum. It's built using the Cosmos SDK which runs on top of Tendermint Core consensus engine.

Note: Requires Go 1.17+

Installation

For prerequisites and detailed build instructions please read the Installation instructions. Once the dependencies are installed, run:

make install

Or check out the latest release.

Quick Start

To learn how the Evmos works from a high-level perspective, go to the Introduction section from the documentation. You can also check the instructions to Run a Node.

Community

The following chat channels and forums are a great spot to ask questions about Evmos:

Contributing

Looking for a good place to start contributing? Check out some good first issues.

For additional instructions, standards and style guides, please refer to the Contributing document.

Careers

See our open positions on Cosmos Jobs, Notion, or feel free to reach out via email.

Comments
  • imp: enable revive rules

    imp: enable revive rules

    Description

    I have set all severity: error flags to a warning. This in the meantime will enable us to tackle each of the lint issues in individual PRs.

    Closes: #XXX


    All items are required. Please add a note to the item if the item is not applicable and please add links to any relevant follow up issues.

    PR review checkboxes:

    I have...

    • [ ] added a relevant changelog entry to the Unreleased section in CHANGELOG.md
    • [ ] included the correct type prefix in the PR title
    • [ ] targeted the correct branch (see PR Targeting)
    • [ ] provided a link in the PR description to the relevant issue or specification
    • [ ] reviewed "Files changed" and left comments if necessary
    • [ ] confirmed all required CI checks have passed

    Code maintenance:

    I have...

    • [ ] written unit and integration tests
    • [ ] added relevant godoc and code comments.
    • [ ] updated relevant documentation (docs/) or specification (x/<module>/spec/)

    Reviewers Checklist

    All items are required. Please add a note if the item is not applicable and please add your handle next to the items reviewed if you only reviewed selected items.

    I have...

    • [ ] confirmed the correct type prefix in the PR title
    • [ ] confirmed all author checklist items have been addressed
    • [ ] confirmed that this PR does not change production code
    good first issue help wanted Type: CI C:Types 
    opened by fedekunze 34
  • chore: sdk v46

    chore: sdk v46

    Description

    • sdk v46
    • ibc-go v5-rc0

    This PR updates EVMOS to cosmos-sdk v0.46.1, tendermint v0.34.21, and ibc-go v5.0.0-rc1

    The changes are coupled together because ibc-go v4.0.0 is not compatible with cosmos-sdk v0.46.*

    One way to reduce the number of files changed in this PR would be to make a PR containing only the path change from github.com/evmos/evmos/v8 to github.com/evmos/evmos/v9


    All items are required. Please add a note to the item if the item is not applicable and please add links to any relevant follow up issues.

    PR review checkboxes:

    I have...

    • [ ] added a relevant changelog entry to the Unreleased section in CHANGELOG.md
    • [ ] included the correct type prefix in the PR title
    • [ ] targeted the correct branch (see PR Targeting)
    • [ ] provided a link in the PR description to the relevant issue or specification
    • [ ] reviewed "Files changed" and left comments if necessary
    • [ ] confirmed all required CI checks have passed

    Code maintenance:

    I have...

    • [ ] written unit and integration tests
    • [ ] added relevant godoc and code comments.
    • [ ] updated relevant documentation (docs/) or specification (x/<module>/spec/)

    Reviewers Checklist

    All items are required. Please add a note if the item is not applicable and please add your handle next to the items reviewed if you only reviewed selected items.

    I have...

    • [ ] confirmed the correct type prefix in the PR title
    • [ ] confirmed all author checklist items have been addressed
    • [ ] confirmed that this PR does not change production code
    opened by faddat 25
  • ERR failed init node error=

    ERR failed init node error="error during handshake: error on replay: wrong Block.Header.AppHash.

    ERR failed init node error="error during handshake: error on replay: wrong Block.Header.AppHash. Expected F24F64FA2766CC94E640C503CA7462D133107DAABBEB57D7C6C619312892C14F, got 7D698782C45C70274523B407864801BF5BEEBD2C8E5FDA5E03D9CE19E05B4E1E" Error: error during handshake: error on replay: wrong Block.Header.AppHash. Expected F24F64FA2766CC94E640C503CA7462D133107DAABBEB57D7C6C619312892C14F, got 7D698782C45C70274523B407864801BF5BEEBD2C8E5FDA5E03D9CE19E05B4E1E

    version:3.0.0 mac go:1.8

    chain-id:evmos_9001-2

    Status: Stale 
    opened by craft0909 18
  • Implement Ledger support on CLI

    Implement Ledger support on CLI

    Description

    This PR implements Ledger support for the Evmos CLI.

    Adding support for Ledger keys on the CLI allows users to opt into an additional layer of security if desired, thereby creating a safer and more secure experience for Evmos CLI users.

    Example Usage on LocalNode:

    1. Connect a Ledger device to your laptop using USB (Bluetooth is not supported)
    2. Start a local Evmos node using ./init.sh
    3. Unlock the Ledger and open the Ethereum Ledger app
    4. Add the Ledger as an Evmos key using evmosd keys add myledger --ledger; it should display the Ledger device's default Ethereum address (copy this value)
    5. Send funds to your Ledger account using evmosd tx bank send mykey [your Ledger address] 100000000000000000aevmos --fees 200aevmos
    6. Check the balance of your Ledger account using evmosd query bank balances [your Ledger address]
    7. Send funds from your Ledger account using evmosd tx bank send myledger evmos1e4etd2u9c2huyjacswsfukugztxvd9du52y49t 1000aevmos --fees 200aevmos
    8. Check the balances of your Ledger account and the destination account using evmosd query bank balances [your Ledger address] and evmosd query bank balances evmos1e4etd2u9c2huyjacswsfukugztxvd9du52y49t

    Example Usage in Production:

    Follow steps 1, 3, and 4 from above to connect your Ledger device and add it as a key. Then, perform all CLI functions with the field --from=myledger to sign off using the device.

    Testing

    • Ledger keys have been tested to support: sending & staking tokens, submitting governance proposals, and voting on governance proposals
    • Software keys continue to work as expected

    All items are required. Please add a note to the item if the item is not applicable and please add links to any relevant follow up issues.

    PR review checkboxes:

    I have...

    • [ ] added a relevant changelog entry to the Unreleased section in CHANGELOG.md
    • [ ] included the correct type prefix in the PR title
    • [ ] targeted the correct branch (see PR Targeting)
    • [ ] provided a link in the PR description to the relevant issue or specification
    • [ ] reviewed "Files changed" and left comments if necessary
    • [ ] confirmed all required CI checks have passed

    Code maintenance:

    I have...

    • [ ] written unit and integration tests
    • [ ] added relevant godoc and code comments.
    • [ ] updated relevant documentation (docs/) or specification (x/<module>/spec/)

    Reviewers Checklist

    All items are required. Please add a note if the item is not applicable and please add your handle next to the items reviewed if you only reviewed selected items.

    I have...

    • [ ] confirmed the correct type prefix in the PR title
    • [ ] confirmed all author checklist items have been addressed
    • [ ] confirmed that this PR does not change production code
    opened by austinchandra 15
  • fix: IBC attestation ordering

    fix: IBC attestation ordering

    Description

    Closes: ENG-192


    All items are required. Please add a note to the item if the item is not applicable and please add links to any relevant follow up issues.

    PR review checkboxes:

    I have...

    • [ ] added a relevant changelog entry to the Unreleased section in CHANGELOG.md
    • [ ] included the correct type prefix in the PR title
    • [ ] targeted the correct branch (see PR Targeting)
    • [ ] provided a link in the PR description to the relevant issue or specification
    • [ ] reviewed "Files changed" and left comments if necessary
    • [ ] confirmed all required CI checks have passed

    Code maintenance:

    I have...

    • [ ] written unit and integration tests
    • [ ] added relevant godoc and code comments.
    • [ ] updated relevant documentation (docs/) or specification (x/<module>/spec/)

    Reviewers Checklist

    All items are required. Please add a note if the item is not applicable and please add your handle next to the items reviewed if you only reviewed selected items.

    I have...

    • [ ] confirmed the correct type prefix in the PR title
    • [ ] confirmed all author checklist items have been addressed
    • [ ] confirmed that this PR does not change production code
    backport/3.0.x 
    opened by fedekunze 14
  • ENG 453 mint and allocation

    ENG 453 mint and allocation

    Description

    This PR implements two different inflation mechanisms:

    1. Linear Team Vesting

    • Initial supply of 200M is minted once at genesis and sent to unvested team account . This prevents triggering multiple taxable events that would occur if we would mint the team vesting provision daily.
    • Each epoch (each day) a constant team vesting provision is sent from the unvested team account to the team account.

    2. Exponential Inflation - The Half Life

    • Exponential inflation is calculated for staking, usage incentives and community pool, not for team vesting.
    • Inflation is minted in daily epochs. After each period of 365 epochs (one year) the amount of rewards per epoch is recalculated with the calculation below:
    f(x) describes the total inflation per year
    
    periodProvision = exponentialDecay       *  bondingRatio
    f(x)            = (a * (1 - r) ^ x + c)  *  ((2 - b) / 2)
    
    epochProvision = periodProvision / epochsPerPeriod
    
    • each param can be customised ( a, r, c, b, epochsPerPeriod)
    C:Proto C:CLI Type: Docs 
    opened by danburck 14
  • feat(tests): e2e tests for chain upgrades

    feat(tests): e2e tests for chain upgrades

    Description

    Closes https://linear.app/evmos/issue/ENG-581/improve-upgrade-e2e-tests-usability

    Adding e2e upgrade manager abstraction && e2e tests revamping.

    After some attempts to support chain_init I decided to rework e2e tests, as I found that a log of code can be deprecated. For now major changes on e2e package are done, and TestUpgrade implemented for single node only.

    Base e2e package structure and upgrade stages described in tests/e2e/README.md

    • [x] Upgrade tests

    All items are required. Please add a note to the item if the item is not applicable and please add links to any relevant follow up issues.

    PR review checkboxes:

    I have...

    • [ ] added a relevant changelog entry to the Unreleased section in CHANGELOG.md
    • [ ] included the correct type prefix in the PR title
    • [ ] targeted the correct branch (see PR Targeting)
    • [ ] provided a link in the PR description to the relevant issue or specification
    • [ ] reviewed "Files changed" and left comments if necessary
    • [ ] confirmed all required CI checks have passed

    Code maintenance:

    I have...

    • [ ] written unit and integration tests
    • [ ] added relevant godoc and code comments.
    • [ ] updated relevant documentation (docs/) or specification (x/<module>/spec/)

    Reviewers Checklist

    All items are required. Please add a note if the item is not applicable and please add your handle next to the items reviewed if you only reviewed selected items.

    I have...

    • [ ] confirmed the correct type prefix in the PR title
    • [ ] confirmed all author checklist items have been addressed
    • [ ] confirmed that this PR does not change production code
    Type: Build C:CLI Type: Tests 
    opened by 4rgon4ut 12
  • Err=

    Err="incompatible: peer is on a different network. Got evmos_9001-2, expected evmos_9001-1"

    Summary of Bug

    While syncing node from start getting error as incompatible: peer is on a different network. Got evmos_9001-2, expected evmos_9001-1

    Version

    v4.0.1

    Steps to Reproduce

    Steps followed from https://docs.evmos.org/validators/mainnet.html

    Screenshots

    image

    For Admin Use

    • [ ] Not duplicate issue
    • [ ] Appropriate labels applied
    • [ ] Appropriate contributors tagged
    • [ ] Contributor assigned/self-assigned
    Status: Stale 
    opened by ghost 12
  • [ENG-128] Fee distribution module - x/fees

    [ENG-128] Fee distribution module - x/fees

    Description

    ~~Distributes gasUsed * baseFee to developers (contract owners) and validators.~~ Distributes gasUsed * gasPrice (legacy tx), gasUsed * effectiveGasPrice (dynamic tx) to developers (contract deployers) and validators.

    Closes: https://linear.app/tharsis/issue/ENGO-370/fee-distribution-module Closes: https://github.com/tharsis/evmos/issues/437

    Related PRs: https://github.com/tharsis/evmos/pull/461 https://github.com/tharsis/evmos/pull/464 https://github.com/tharsis/evmos/pull/469 https://github.com/tharsis/evmos/pull/471


    All items are required. Please add a note to the item if the item is not applicable and please add links to any relevant follow up issues.

    PR review checkboxes:

    I have...

    • [ ] added a relevant changelog entry to the Unreleased section in CHANGELOG.md
    • [ ] included the correct type prefix in the PR title
    • [x] targeted the correct branch (see PR Targeting)
    • [x] provided a link in the PR description to the relevant issue or specification
    • [ ] reviewed "Files changed" and left comments if necessary
    • [ ] confirmed all required CI checks have passed

    Code maintenance:

    I have...

    • [x] written unit and integration tests
    • [ ] added relevant godoc and code comments.
    • [ ] updated relevant documentation (docs/) or specification (x/<module>/spec/)

    Reviewers Checklist

    All items are required. Please add a note if the item is not applicable and please add your handle next to the items reviewed if you only reviewed selected items.

    I have...

    • [ ] confirmed the correct type prefix in the PR title
    • [ ] confirmed all author checklist items have been addressed
    • [ ] confirmed that this PR does not change production code
    opened by loredanacirstea 12
  • [ENG-447] protobuf workspaces migration

    [ENG-447] protobuf workspaces migration

    Description

    • migrating protobuf code generator to protobuf workspaces
    • ticket: ENG-447
    • purpose: current proto build configuration for proto and swagger files "not reliable" (as per ticket), this PR creates a Buf Workspace in the repository and changes the iterative use of protoc -> buf build and buf generate.

    All items are required. Please add a note to the item if the item is not applicable and please add links to any relevant follow up issues.

    PR review checkboxes:

    I have...

    • [ ] added a relevant changelog entry to the Unreleased section in CHANGELOG.md
    • [ ] included the correct type prefix in the PR title
    • [ ] targeted the correct branch (see PR Targeting)
    • [ ] provided a link in the PR description to the relevant issue or specification
    • [ ] reviewed "Files changed" and left comments if necessary
    • [ ] confirmed all required CI checks have passed

    Code maintenance:

    I have...

    • [ ] written unit and integration tests
    • [ ] added relevant godoc and code comments.
    • [ ] updated relevant documentation (docs/) or specification (x/<module>/spec/)

    Reviewers Checklist

    All items are required. Please add a note if the item is not applicable and please add your handle next to the items reviewed if you only reviewed selected items.

    I have...

    • [ ] confirmed the correct type prefix in the PR title
    • [ ] confirmed all author checklist items have been addressed
    • [ ] confirmed that this PR does not change production code
    C:Proto Type: Build Type: CI 
    opened by adisaran64 11
  • Panic while running mainnet node- `panic: UnmarshalJSON cannot decode empty bytes`

    Panic while running mainnet node- `panic: UnmarshalJSON cannot decode empty bytes`

    Summary of Bug

    Trying to run a node for RPC request, getting error panic: UnmarshalJSON cannot decode empty bytes

    Version

    Latest clone from github

    Steps to Reproduce

    Unzip the snapshot to /data directory evmosd start --home /data

    Screenshots

    image

    For Admin Use

    • [ ] Not duplicate issue
    • [ ] Appropriate labels applied
    • [ ] Appropriate contributors tagged
    • [ ] Contributor assigned/self-assigned
    opened by ghost 10
  • fix(upgrade): ICA Host params

    fix(upgrade): ICA Host params

    Description

    Closes: #XXX


    All items are required. Please add a note to the item if the item is not applicable and please add links to any relevant follow up issues.

    PR review checkboxes:

    I have...

    • [ ] added a relevant changelog entry to the Unreleased section in CHANGELOG.md
    • [ ] included the correct type prefix in the PR title
    • [ ] targeted the correct branch (see PR Targeting)
    • [ ] provided a link in the PR description to the relevant issue or specification
    • [ ] reviewed "Files changed" and left comments if necessary
    • [ ] confirmed all required CI checks have passed

    Code maintenance:

    I have...

    • [ ] written unit and integration tests
    • [ ] added relevant godoc and code comments.
    • [ ] updated relevant documentation (docs/) or specification (x/<module>/spec/)

    Reviewers Checklist

    All items are required. Please add a note if the item is not applicable and please add your handle next to the items reviewed if you only reviewed selected items.

    I have...

    • [ ] confirmed the correct type prefix in the PR title
    • [ ] confirmed all author checklist items have been addressed
    • [ ] confirmed that this PR does not change production code
    opened by fedekunze 0
  • fix: localize WithKeyTable in each module's migration logic

    fix: localize WithKeyTable in each module's migration logic

    Description

    This PR localizes the WithKeyTable method from the Subspace in the migration folder of each of the modules that have deprecated x/params. It's used solely for migration and is part of the LegacySubspace interface. Previously it was all added in the app.go.

    Closes: #XXX


    All items are required. Please add a note to the item if the item is not applicable and please add links to any relevant follow up issues.

    PR review checkboxes:

    I have...

    • [ ] added a relevant changelog entry to the Unreleased section in CHANGELOG.md
    • [ ] included the correct type prefix in the PR title
    • [ ] targeted the correct branch (see PR Targeting)
    • [ ] provided a link in the PR description to the relevant issue or specification
    • [ ] reviewed "Files changed" and left comments if necessary
    • [ ] confirmed all required CI checks have passed

    Code maintenance:

    I have...

    • [ ] written unit and integration tests
    • [ ] added relevant godoc and code comments.
    • [ ] updated relevant documentation (docs/) or specification (x/<module>/spec/)

    Reviewers Checklist

    All items are required. Please add a note if the item is not applicable and please add your handle next to the items reviewed if you only reviewed selected items.

    I have...

    • [ ] confirmed the correct type prefix in the PR title
    • [ ] confirmed all author checklist items have been addressed
    • [ ] confirmed that this PR does not change production code
    opened by Vvaradinov 0
  • upgrade: incentivized testnet airdrop claim

    upgrade: incentivized testnet airdrop claim

    Description

    Closes: #1237 (Linear)

    This PR introduces the upgrade handler logic and corresponding tests meant to distribute the rewards for completing the Mars Meteor Missions during the Olympus Mons incentivized testnet.

    Spec for Evmos team members: here


    All items are required. Please add a note to the item if the item is not applicable and please add links to any relevant follow up issues.

    PR review checkboxes:

    I have...

    • [ ] added a relevant changelog entry to the Unreleased section in CHANGELOG.md
    • [ ] included the correct type prefix in the PR title
    • [ ] targeted the correct branch (see PR Targeting)
    • [ ] provided a link in the PR description to the relevant issue or specification
    • [ ] reviewed "Files changed" and left comments if necessary
    • [ ] confirmed all required CI checks have passed

    Code maintenance:

    I have...

    • [ ] written unit and integration tests
    • [ ] added relevant godoc and code comments.
    • [ ] updated relevant documentation (docs/) or specification (x/<module>/spec/)

    Reviewers Checklist

    All items are required. Please add a note if the item is not applicable and please add your handle next to the items reviewed if you only reviewed selected items.

    I have...

    • [ ] confirmed the correct type prefix in the PR title
    • [ ] confirmed all author checklist items have been addressed
    • [ ] confirmed that this PR does not change production code
    opened by adisaran64 1
  • Bug fixes 1181 build tags fix

    Bug fixes 1181 build tags fix

    Description

    Closes: #1181


    All items are required. Please add a note to the item if the item is not applicable and please add links to any relevant follow up issues.

    PR review checkboxes:

    I have...

    • [ ] added a relevant changelog entry to the Unreleased section in CHANGELOG.md
    • [ ] included the correct type prefix in the PR title
    • [ ] targeted the correct branch (see PR Targeting)
    • [ ] provided a link in the PR description to the relevant issue or specification
    • [ ] reviewed "Files changed" and left comments if necessary
    • [ ] confirmed all required CI checks have passed

    Code maintenance:

    I have...

    • [ ] written unit and integration tests
    • [ ] added relevant godoc and code comments.
    • [ ] updated relevant documentation (docs/) or specification (x/<module>/spec/)

    Reviewers Checklist

    All items are required. Please add a note if the item is not applicable and please add your handle next to the items reviewed if you only reviewed selected items.

    I have...

    • [ ] confirmed the correct type prefix in the PR title
    • [ ] confirmed all author checklist items have been addressed
    • [ ] confirmed that this PR does not change production code
    opened by ekhvalov 0
  • Update hardhat.md

    Update hardhat.md

    clarity on obtaining, privateKey, values. Update hardhat info based on new version

    Description

    Closes: #XXX


    All items are required. Please add a note to the item if the item is not applicable and please add links to any relevant follow up issues.

    PR review checkboxes:

    I have...

    • [ ] added a relevant changelog entry to the Unreleased section in CHANGELOG.md
    • [ ] included the correct type prefix in the PR title
    • [ ] targeted the correct branch (see PR Targeting)
    • [ ] provided a link in the PR description to the relevant issue or specification
    • [ ] reviewed "Files changed" and left comments if necessary
    • [ ] confirmed all required CI checks have passed

    Code maintenance:

    I have...

    • [ ] written unit and integration tests
    • [ ] added relevant godoc and code comments.
    • [ ] updated relevant documentation (docs/) or specification (x/<module>/spec/)

    Reviewers Checklist

    All items are required. Please add a note if the item is not applicable and please add your handle next to the items reviewed if you only reviewed selected items.

    I have...

    • [ ] confirmed the correct type prefix in the PR title
    • [ ] confirmed all author checklist items have been addressed
    • [ ] confirmed that this PR does not change production code
    opened by 4coffeeihadbreakfast 0
  • Ledger Authz TX for REStake not working | signature verification failed

    Ledger Authz TX for REStake not working | signature verification failed

    Summary of Bug

    I'm attempting to send the following authz transaction with my Ledger for compounding my staking rewards:

    evmosd tx authz grant evmos18fzq4nac28gfma6gqfvkpwrgpm5ctar2z9mxf3 generic --msg-type /cosmos.staking.v1beta1.MsgDelegate --from ledger --ledger --chain-id evmos_9001-2 --node https://rpc.cosmos.directory:443/evmos --keyring-backend file --fees 5000000000000000aevmos

    However, after running this, I get the following error:

    signature verification failed; please verify account number (2991546) and chain-id (evmos_9001-2): unauthorized

    I was told that this was a sig verification problem that would be fixed on v10.0.0, but it has not been resolved.

    Version

    v10.0.0

    Steps to Reproduce

    evmosd keys add ledger --ledger --keyring-backend file
    
    evmosd tx authz grant evmos18fzq4nac28gfma6gqfvkpwrgpm5ctar2z9mxf3 generic --msg-type /cosmos.staking.v1beta1.MsgDelegate --from ledger --ledger --chain-id evmos_9001-2 --node https://rpc.cosmos.directory:443/evmos --keyring-backend file --fees 5000000000000000aevmos
    

    Screenshots

    image

    Additional context

    Attempting to use REStake.io to auto redelegate my staking rewards for me using authz permissions, but code is not letting me.


    For Admin Use

    • [ ] Not duplicate issue
    • [ ] Appropriate labels applied
    • [ ] Appropriate contributors tagged
    • [ ] Contributor assigned/self-assigned
    opened by mrgarbagegamer 4
Releases(v10.0.1)
WAMpage - A WebOS root LPE exploit chain

WAMpage WAMpage - A WebOS root LPE exploit chain This exploit is mainly of interest to other researchers - if you just want to root your TV, you proba

David Buchanan 45 Dec 2, 2022
Nouns On-Chain Proposal Simulation and Analysis

Nouns Diligence Nouns On-Chain Proposal Simulation and Analysis For Voters Technical reports for all reviewed proposals can be found in the reports fo

Nouns 23 Dec 26, 2022
On-chain generative NFT collection

ETH Time ETH Time is a new NFT collection created to explore new ways of generating NFTs on-chain. It is inspired by existing projects such as Zora's

null 3 Feb 13, 2022
Chain Link External Inititator Template

Chain Link External Inititator Template AWS Lambda Ready Pre-Deployment 1) Install the Serverless Framework globally npm install serverless -g 2) In

0xD1x0n 4 May 6, 2022
Scans your computer for node modules that are potentially vulnerable to supply chain attacks

Scans your computer for node modules that are potentially vulnerable to supply chain attacks. You still need to review the code of modules that are not vulnerable, but this helps.

Brandon Nozaki Miller 4 Apr 11, 2022
A website for tracking community support for BIP21 QR codes that support on-chain and lightning bitcoin payments.

BIP21 Microsite This is a WIP microsite to promote the usage of a BIP21 payment URI QR code that can include lightning invoices or offers. Wallet supp

Stephen DeLorme 16 Nov 27, 2022
Gas-efficient on-chain batched shuffling for NFTs

Batch NFT reveal This repository contains a gas-efficient implementation of an on-chain shuffling algorithm used to reveal NFTs in batches. The main b

Tubby Cats 97 Dec 12, 2022
Stays: book accommodation on-chain, pay in crypto, and help local communities

Stays: on-chain bookings Installation Make sure you have node and nvm installed: nvm use v16 npm install -g yarn npm install -g lerna yarn install ler

Winding Tree 8 Jun 2, 2022
This SDK helps developers get started with the on-chain tools provided by Metaplex.

Metaplex JavaScript SDK ⛔️ DO NOT USE IN PRODUCTION, THIS SDK IS IN VERY EARLY ALPHA STAGES! This SDK helps developers get started with the on-chain t

Metaplex Foundation 263 Dec 27, 2022
Danger is near (play to earn game, gamefi on near chain testnet) - user play as a fireknight in a PIXELVERSE world who go to forest and kill monster.

Danger is near (play to earn game, gamefi on near chain testnet) - user play as a fireknight in a PIXELVERSE world who go to forest and kill monster. User can earn $DANGER token and score to compete with others user.

Jason Factor 21 Dec 30, 2022
DecentraMix.io is a cross-chain, non-custodial, universal privacy-preserving protocol with the decentralized governance

DecentraMix.io is a cross-chain, non-custodial, universal privacy-preserving protocol with the decentralized governance. DecentraWorld applies zkSNARKs to enable transactional privacy for all DeFi components by breaking the on-chain link between depositor and recipient addresses.

DecentraWorld Ecosystem 65 May 7, 2022
A decentralized protocol for indexing and querying data from DecentraMix's on chain contracts across all supported blockchains.

A decentralized protocol for indexing and querying data from DeMix contracts across all supported blockchains.

DecentraWorld Ecosystem 92 May 3, 2022
Lucid is a library, which allows you to create Cardano transactions and off-chain code for your Plutus contracts in JavaScript and Node.js.

Lucid is a library, which allows you to create Cardano transactions and off-chain code for your Plutus contracts in JavaScript and Node.js.

Berry 243 Jan 8, 2023
Multi-chain sniper bot to buy and sell tokens on ETH compatible chains. Features include instant or mempool sniping, rug protection, and sell management.

An open-source defi sniper. defi-sniper is free to download. NEW Community telegram group: https://t.me/+aBLUmP1UnypiNTVh Premium Services Now Availab

spacemonk 6 May 3, 2022
On-chain query batcher for CosmWasm-enabled chains

multiquery On-chain query batcher for CosmWasm. Similar to SCB 10X's multicall contract, but supports any serializable query request, not limited to W

null 7 Dec 6, 2022
simple dashboard for cross-chain greeks

Oh My Greeks Simple platform for cross-chain Greeks Intro We need a place to see all my on-chain greeks.. aggregated nicely. Hosting Currently hosting

Anton Cheng 9 Aug 12, 2022
An ERC-721 like NFT contract with Plutus scripts and Lucid as off-chain framework

Gatsby minimal TypeScript starter ?? Quick start Create a Gatsby site. Use the Gatsby CLI to create a new site, specifying the minimal TypeScript star

Berry 10 Sep 23, 2022
Ethereum chain sniperbot for tokens. This bot sniffs the mempool for pending transactions for trading enabled and also liquidity add functions.

Ethereum chain sniperbot for tokens. This bot sniffs the mempool for pending transactions for trading enabled and also liquidity add functions.

null 12 Dec 5, 2022
chain-syncer is a module which allows you to synchronize your app with any ethereum-compatible blockchain/contract state. Fast. Realtime. Reliable.

Chain Syncer Chain Syncer is a JS module which allows you to synchronize your app with any ethereum-compatible blockchain/contract state. Fast. Realti

Miroslaw Shpak 10 Dec 15, 2022