Jump to content

Graft

Sign in to follow this  
  • entries
    166
  • comment
    1
  • views
    29205

Contributors to this blog

  • Snider 166

GRAFT and Lyra – why Lyra, why now, how it affects Graft Network and GRFT coin

Sign in to follow this  
Snider

395 views

Why Lyra?

While working on various GRAFT Network components over the past two years, we felt that working with Monero code base was quite restricting and that we could eventually run into roadblocks and limitations when it came to providing the performance necessary for high volume payments, or building out some of the functionality (not to mention the heft of dealing with the older convoluted code base), so we started an R&D experiment of creating a blockchain from scratch using the latest approaches and techniques in blockchain design. This development came together quicker than expected and opened up various possibilities, among which was an opportunity to launch it separately as a solution for merchant tokens and tokens in general.

GRAFT and Lyra – path forward

Both technologies have their own strengths at the moment. The existing GRAFT chain is privacy-centric and has implemented staking, communication, has a decentralized network of supernodes with consensus mechanism. Lyra is capable of token issuance, super-fast transactions, very light clients, and intra-chain token conversion.

Together they complement each other and can work in concert to provide the most effective solution available today. image1.png

Lyra Permissioned Network is a spin-off network set up to establish commercial market presence and to bootstrap the project with real life usage. Screen-Shot-2019-09-13-at-7.30.08-AM.png

On the token side of things:

GRFT will remain the staking and voting currency for the decentralized GRAFT and Lyra Networks. It will take advantage of the decentralization and staking mechanism that exists on GRAFT Network today and due to its privacy features is a great match for that.

LYRA will be the gas currency for Lyra transactions on Lyra part of the network.

Lyra permissioned is a separate network, with its own economics, and with LYPE being the staking and the gas token of the network.

Summary

GRAFT Network is not going anywhere – it is being supplemented with a newer blockchain technology that’s capable of removing the obstacles that we would otherwise face. GRFT (or its equivalent on the Lyra chain) remains the backbone currency of the decentralized network.

If you look at the top 20 blockchains by the market capitalizations, most of them represent novel blockchain technology approach developed from scratch. With Lyra, we think GRAFT gets a great additional technology track it can rely on for solving problems we set out to address, more market traction potential faster, and can be further noticed and appreciated by the blockchain community at large.

The post GRAFT and Lyra – why Lyra, why now, how it affects Graft Network and GRFT coin appeared first on Graft Blockchain.


View Original Post

Sign in to follow this  


0 Comments


Recommended Comments

There are no comments to display.

Guest
Add a comment...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

  • HashVault Latest Blocks

  • HashVault Stats

    • Global Hashrate
      2.35 TH
    • Avg Hashrate
      875.90 MH
    • Total Miners
      2685
    • Miners Paid
      44744
    • Total Payments
      1560140
    • Total Hashes
      9.23 EX
    • Blocks Found
      1840425
  • Posts

    • Hey guys. Can somebody help me? I wanted to have some fun and start mining Monero.  This is my config:    {     "autosave": true,     "donate-level": 2,     "cpu": true,     "opencl": true,     "cuda": true,     "pools": [         {             "url": "pool.hashvault.pro:3333"         },         {             "url": "pool.hashvault.pro:443",             "user": "-------------",             "keepalive": true,             "tls": true         }     ] }   I generated on website. Can you help me with user? What should I put there? A wallet address? (i have Coinomi wallet). Where to get it? Don't have any serious expectations about mining but i have a PC with two RTX 3060 so maybe i will dig something in free time just to be happy, even if it will be worth 1$ 🙂 Thank you in advance.
    • А куда пул вообще пропал? Нужно было посмотреть txid своих старых выплат, а страница тупо пропала.
    • Dear Community,   Reading the "Getting Started" section in the Pool area and some threads on the Forum, I still have a little question.  Whom do you recommend mining solo?  The hash rate seems to be the same whether I do SOLO mining or not.  Thanks! Bee *** My machine is a simple workstation with a slim linux running: * ABOUT XMRig/6.7.0 gcc/9.3.0 * LIBS libuv/1.38.1 OpenSSL/1.1.1i hwloc/2.2.0 * HUGE PAGES supported * 1GB PAGES unavailable * CPU Intel(R) Xeon(R) CPU E3-1280 V2 @ 3.60GHz (1) 64-bit AES L2:1.0 MB L3:8.0 MB 4C/8T NUMA:1 * MEMORY 1.1/15.6 GB (7%) * DONATE 1% * ASSEMBLY auto:intel * POOL #1 pool.hashvault.pro:3333 algo auto * COMMANDS hashrate, pause, resume, results, connection * OPENCL disabled * CUDA disabled  
    • Update: Having applied the Script from the thread linked to above, I get another outcome. Is that as it is supposed to be?? Thanks again Bee alpinehost:/home/alp# chown root /usr/share/hugepages.sh alpinehost:/home/alp# /usr/share/./hugepages.sh enable Huge pages enabled alpinehost:/home/alp# sysctl -a | grep hugep sysctl: error reading key 'net.ipv6.conf.all.stable_secret': I/O error sysctl: error reading key 'net.ipv6.conf.default.stable_secret': I/O error sysctl: error reading key 'net.ipv6.conf.eth0.stable_secret': I/O error sysctl: error reading key 'net.ipv6.conf.lo.stable_secret': I/O error vm.nr_hugepages = 9 vm.nr_hugepages_mempolicy = 9 vm.nr_overcommit_hugepages = 0 alpinehost:/home/alp# The vm.nr_hugepages changed dramatically. What does it mean anyways?
    • Dear Community,    I would like to have these Hugepages supported now :-) I am thus referring to this thread here, which seems to be closed. I have tried the following to enable hugepages AND get them working until 1 GB.  See me output: Thanks so far! Bee *** Question: Why is HUGEpages 1 GIg not available?  How do I set the value correct? My output: sysctl -a | grep hugep sysctl: error reading key 'net.ipv6.conf.all.stable_secret': I/O error sysctl: error reading key 'net.ipv6.conf.default.stable_secret': I/O error sysctl: error reading key 'net.ipv6.conf.eth0.stable_secret': I/O error sysctl: error reading key 'net.ipv6.conf.lo.stable_secret': I/O error vm.nr_hugepages = 2349 vm.nr_hugepages_mempolicy = 2349 vm.nr_overcommit_hugepages = 0 *** and in xmrig *** ABOUT XMRig/6.7.0 gcc/9.3.0 * LIBS libuv/1.38.1 OpenSSL/1.1.1i hwloc/2.2.0 * HUGE PAGES supported * 1GB PAGES unavailable * CPU Intel(R) Xeon(R) CPU E3-1280 V2 @ 3.60GHz (1) 64-bit AES L2:1.0 MB L3:8.0 MB 4C/8T NUMA:1 * MEMORY 3.2/15.6 GB (21%) * DONATE 1% * ASSEMBLY auto:intel * POOL #1 pool.hashvault.pro:3333 algo auto * COMMANDS hashrate, pause, resume, results, connection * OPENCL disabled * CUDA disabled  
×
×
  • Create New...