Jump to content

Graft

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

Contributors to this blog

  • Snider 166

GRAFT Letter to Community

Sign in to follow this  
Snider

615 views

We would to thank you all for participating in Graft project. As you all know, GRAFT had seen better days. From day one we had one single mission: to enable crypto to be used as every day money. We lived this mission every day of our lives for 2 years, and had a lot done under the hood. We admit that while working on developing new technology we didn’t pay enough attention to promoting the GRFT token. Many crypto projects out there did the opposite, they spend more money on marketing and listed on more exchanges. Some of them didn’t do any development at all. So, before we continue, I would like to list everything that we have done so far:

  1. PoW Mainnet based on privacy blockchain ( 2 years in existence )PoS layer of Supernodes (with 1,500+ staking supernodes)
  2. DHT communications, Supernode sample selection with blockchain based disqualifications
  3. Mobile and Desktop wallet and Point-of-Sale applications
  4. Verifone and Ingenico payment terminal integrations
  5. DEX design and prototype
  6. End-to-end Testnet integration
  7. Merchant tokens solution based on a DAG-style blockchain written from scratch
  8. Listed GRFT on 3 exchanges: TradeOgre, HotBit, STEX

Each of these deliverable are complete to a various degree. Some are close to being finished. Others need substantial work.

Thinking in retrospect, we should have been more balanced in our approach and pay more attention to promoting the coin. None of us, however, could have foreseen such a steep downturn in the crypto market, that wiped out the value of many alt coins, including Graft.

As funds dried up, so did the development. From 10+ core developers and multiple contractors at the peak, we now only have 2 core developers and several part-time contractors.. We spent the last 6 months trying to find a solution. We contemplated shutting down many times, but it would be a shame to have all this work go to waste. So, we decided on a different approach. We started looking for people who would breath new life into our project. But first we wanted to make sure that a) our ideas have merit and b) the development direction is good. We started talking to the market — individuals, merchants, large companies, and various government entities who could possibly benefit from what we’re developing and got a solid confirmation that we are, in fact, on the right track.

With that in mind we decided to NOT give up.

So, now we are looking for new blood, new approaches, new partnerships, new everything. We come to you hat in hand. We really need your help. We are not looking for money, just your constructive advice.

Dear Community, please put yourselves in our shoes, and help us find a way forward.

Thanks in advance.

Kindly

Graft core team.

P.S. Please use GRAFT’s main TG channel to participate in the discussion.



The post GRAFT Letter to Community 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.40 TH
    • Avg Hashrate
      892.19 MH
    • Total Miners
      2685
    • Miners Paid
      44745
    • Total Payments
      1560148
    • Total Hashes
      9.23 EX
    • Blocks Found
      1840447
  • 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...