Jump to content

Haven

Sign in to follow this  
  • entries
    29
  • comments
    0
  • views
    5539

Haven Announces July 20th xUSD Launch Details

Sign in to follow this  
Snider

138 views

1*U-SjCfduK9l2BdJnLZYAGw.png

We’re excited to share additional details about the hard fork process that will be used to launch the world’s first private stablecoin, xUSD, on July 20th. Today we published the mainnet release code to enable xUSD functionality on Haven’s network.

Haven’s Apollo v1.0.0 is set to fork on July 20th at block height 640640, or roughly 15:00 GMT+1. Functionality for xUSD transactions will be enabled automatically 10 blocks later during a second fork at block height 640650.

This mechanism is being used to ensure that pricing records are already recorded in previous blocks for use when xUSD transactions go live. Pricing records will continue to be pulled from Chainlink’s oracle and displayed here.

This fork will automatically upgrade databases and is a one way operation. If your service is critical (such as a node or mining pool) please make a backup first before performing this upgrade. Additional details regarding installation and the fork process can be found in the Apollo release “Read Me” document.

Our team has completed several successful tests of this fork process on Haven’s stagenet. We are confident this release will enable a smooth transition to launch xUSD on Haven’s mainnet. Today’s updated code has also been shared with all exchanges supporting XHV.

Haven users don’t have to do anything to prepare for the fork. To use xUSD after the fork, you only need to download the mainnet CLI or desktop Vault, which will be the first wallets to support xUSD upon launch. We are completing testing of the desktop Vault and plan to release it in the coming days (well in advance of July 20th).

As always, please stop by Haven’s Discord or join the conversation on Twitter. The future of financial privacy begins July 20th!

stat?event=post.clientViewed&referrerSource=full_rss&postId=4fcd98d92226

View the full article

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...