All Projects → lukso-network → LIPs

lukso-network / LIPs

Licence: other
LUKSO Improvement Proposals. Repository for the LUKSO Blockchain Improvement Proposals (LIPs) and LUKSO Standards Process (LSP).

Projects that are alternatives of or similar to LIPs

ERC-1484
ERC-1484 Reference Implementation
Stars: ✭ 28 (-28.21%)
Mutual labels:  erc, eip
ethereum-erc20
Fungible token implementation for the Ethereum blockchain.
Stars: ✭ 27 (-30.77%)
Mutual labels:  erc, eip
ethereum-evm-illustrated
Ethereum EVM illustrated
Stars: ✭ 170 (+335.9%)
Mutual labels:  evm
lua-analyzer
A language server for lua written in rust
Stars: ✭ 56 (+43.59%)
Mutual labels:  lsp
ZYX-20
A Zyx Network client based on the go-ethereum fork
Stars: ✭ 0 (-100%)
Mutual labels:  evm
democracy
Tools for peer-to-peer privacy with Ethereum and AZTEC
Stars: ✭ 36 (-7.69%)
Mutual labels:  evm
atom-ide-scala
Scala & Dotty support for Atom IDE (🧟‍♂️ zombie repo)
Stars: ✭ 47 (+20.51%)
Mutual labels:  lsp
lsp-ltex
lsp-mode ❤️ LTEX
Stars: ✭ 30 (-23.08%)
Mutual labels:  lsp
erc1363-payable-token
Code implementation for the ERC-1363 Payable Token
Stars: ✭ 83 (+112.82%)
Mutual labels:  eip
vim-lamp
💡Language Server Protocol client for Vim.
Stars: ✭ 34 (-12.82%)
Mutual labels:  lsp
easy-hls-nix
Easy Haskell Language Server tooling with Nix!
Stars: ✭ 56 (+43.59%)
Mutual labels:  lsp
I40KG
Contains the development for the Industry 4.0 standards knowledge graph (I40KG). Its current collaborative development is driven by VoCol - http://vocol.iais.fraunhofer.de/sto/
Stars: ✭ 50 (+28.21%)
Mutual labels:  standards
lxtk
Language Client/Server Toolkit
Stars: ✭ 22 (-43.59%)
Mutual labels:  lsp
aerial.nvim
Neovim plugin for a code outline window
Stars: ✭ 485 (+1143.59%)
Mutual labels:  lsp
Metrix
Decentralized, Anonymous, Fast & Secure Cryptocurrency
Stars: ✭ 41 (+5.13%)
Mutual labels:  evm
c4-common-issues
A collection of common security issues and possible gas optimizations in solidity smart contracts
Stars: ✭ 85 (+117.95%)
Mutual labels:  evm
navigator.lua
Source code analysis & navigation plugin for Neovim. Navigate codes like a breeze🎐. Exploring LSP and 🌲Treesitter symbols a piece of 🍰. Take control like a boss 🦍.
Stars: ✭ 781 (+1902.56%)
Mutual labels:  lsp
zerover
0️⃣ Minimalist versioning scheme for devs who can't be bothered.
Stars: ✭ 141 (+261.54%)
Mutual labels:  standards
intx
intx – extended precision integer library
Stars: ✭ 83 (+112.82%)
Mutual labels:  evm
emerald-web3-gateway
The Web3 Gateway for the Oasis Emerald ParaTime.
Stars: ✭ 19 (-51.28%)
Mutual labels:  evm

LIPs

LUKSO Improvement Proposals (LIPs) and LUKSO standard proposal (LSPs) describe standards for the LUKSO platform, including core protocol specifications, client APIs, and smart contract standards.

A browsable version of all current and draft LIPs can be found on the official LIP folder.

Contributing

  1. Review LIP-1.
  2. Fork the repository by clicking "Fork" in the top right.
  3. Add your LIP to your fork of the repository. There is a template LIP here.
  4. Submit a Pull Request to LUKSO's LIPs repository.

Your first PR should be a first draft of the final LIP. It must meet the formatting criteria enforced by the build (largely, correct metadata in the header). An editor will manually review the first PR for a new LIP and assign it a number before merging it. Make sure you include a discussions-to header with the URL to a discussion forum or open GitHub issue where people can discuss the LIP as a whole.

If your LIP requires images, the image files should be included in a subdirectory of the assets folder for that LIP as follow: assets/lip-X (for lip X). When linking to an image in the LIP, use relative links such as ../assets/lip-X/image.png.

When you believe your LIP is mature and ready to progress past the draft phase, you should do open a PR changing the state of your LIP to 'Final'. An editor will review your draft and ask if anyone objects to its being finalised. If the editor decides there is no rough consensus - for instance, because contributors point out significant issues with the LIP - they may close the PR and request that you fix the issues in the draft before trying again.

LIP Status Terms

  • Draft - an LIP that is undergoing rapid iteration and changes.
  • Last Call - an LIP that is done with its initial iteration and ready for review by a wide audience.
  • Accepted - a core LIP that has been in Last Call for at least 2 weeks and any technical changes that were requested have been addressed by the author. The process for Core Devs to decide whether to encode an LIP into their clients as part of a hard fork is not part of the LIP process. If such a decision is made, the LIP wil move to final.
  • Final (non-Core) - an LIP that has been in Last Call for at least 2 weeks and any technical changes that were requested have been addressed by the author.
  • Final (Core) - an LIP that the Core Devs have decided to implement and release in a future hard fork or has already been released in a hard fork.
  • Deferred - an LIP that is not being considered for immediate adoption. May be reconsidered in the future for a subsequent hard fork.

Preferred Citation Format

The canonical URL for a LIP that has achieved draft status at any point is at https://github.com/lukso-network/LIPs/tree/master/LIPs.

Note that the project description data, including the texts, logos, images, and/or trademarks, for each open source project belongs to its rightful owner. If you wish to add or remove any projects, please contact us at [email protected].