Jump to content

Haven

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

Entries in this blog

Snider
0*ebL_QJQdwwj8f7F5

We are very excited to announce that Haven Protocol has been listed on BKEX!

Trading goes live today at 20:30 (UTC+8).

This is a critical step to expanding access to financial privacy for our users throughout Asia, and will allow access for the first time to the wider Chinese community that has shown a lot of interest in Haven. BKEX is the 4th largest exchange in China. We hope this will assist some of the Chinese investors who have shown long term interest in the project and struggled to find a suitable exchange to use.

As the first listing of an XHV/USDT pair, this listing with BKEX marks another important step for the project, and we also hope that the USDT pairing will allow a new angle for traders by spreading our pricing across more platforms and pairs.

We would like to encourage our regular users to join in the trading competition, Twitter rewards program, and take advantage of a small deposit bonus for XHV deposits on BKEX, further details of which are below.

Trading Contest

During the contest all users who who trade the XHV/USDT pair on BKEX and reach a minimum qualifying trading volume will be given ranking rewards that go towards the following prizes, awarded at the end of the contest to users with the most trading volume:

1*2itplDRqQ-RS_sN_--xa2A.png

Deposit Bonus

For the duration of the contest, all users who deposit a minimum of 500 XHV to BKEX will receive a bonus of 10 USDT. The pool for this is 6500 USDT so it will be distributed on a first come first served basis until the pool is used up.

Twitter Sharing Bonus

During the contest, users who follow the BKEX official Twitter account https://twitter.com/ComBkex and retweet and comment the listing tweet, register relevant information to the form link, will receive 2 USDT. This will be available for the first 300 users who complete the above on a first come first served basis.

stat?event=post.clientViewed&referrerSou

View the full article

Snider
1*h0m8XvAV3h2l45UvDjViMA.png

Over the last month, a number of third-parties have asked us to create a resilient, long-term fee structure for xUSD transactions on the Haven network.

We’ve agreed to do so and the reason is clear: in order for xUSD to be used regularly by millions of people, on the largest platforms in the world, we must implement a solution that ensures fees paid by users are flexible and transparent.

So, the first announcement we’re making today during Haven’s multi-week “Announcement Season” is the Haven 2.0 Fee Structure. These fees are designed to thwart economic attacks and manipulation attempts, while maintaining Haven’s stable storage use case and long-standing promise that “1 xUSD will always be redeemable for $1 worth of XHV”.

Today we are sharing details of a more refined fee structure that will be self-sustaining and fair to all users as Haven’s network grows. Most importantly, this structure will be less attractive to anyone wishing to negatively impact Haven’s network functions and economic stability.

The Haven 2.0 Fee Structure will be implemented soon on Haven’s mainnet via a hard fork to be announced at a later date. Haven’s xUSD fee structure will continue to be iterative moving forward based on the network’s growth and health.

Details of the updated fee structure are as follows:

xUSD exchange unlock times will be: 6 hours, 48 hours, 120 hours (5 days), and 240 hours (10 days).

A standard base fee, based on transaction weight, will be included for every xUSD exchange. This is identical to all transactions (such as transfers) performed on the Haven network.

A conversion fee will be charged based on the selected unlock time and the difference in spot and moving average (24 hours) price of XHV. Each conversion fee will include 0.2% of the value exchanged, multiplied by the priority number of the unlock time from the table below, plus the following:

  • 6 hour exchanges will pay 110% of the spot/MA difference plus 5% of the value exchanged as a speed fee. However, if the funds used as inputs are more than 30 days old, a reduced 2% speed fee will apply.
  • 48 hour exchanges will pay 100% of the spot/MA difference plus 2% of the value exchanged as a speed fee. However, if the funds used as inputs are more than 30 days old, a reduced 0.8% speed fee will apply.
  • 120 hour exchanges will pay 75% of the spot/MA difference. No speed fee will be charged.
  • 240 hour exchanges will pay 25% of the spot/MA delta. No speed fee will be charged.

Finally, since the purpose of the Haven Vault is stable storage, short term trading will be discouraged via a separate speculation fee:

  • 6 hour xUSD to XHV exchanges: If the Vault inputs used are less than 24 hours old, 50% of the XHV profit made on those inputs will be charged as a speculation fee, 40% if less than 28 hours old, and 10% if less than 120 hours old.
  • 48 hour xUSD to XHV exchanges: If the Vault inputs used are less than 120hrs old a 10% speculation fee will be charged.
  • 120 and 240 hour exchanges: no speculation fee will be charged.

In summary, the total fee paid for any xUSD exchange will be made up of the following: Base fee + conversion fee + speed fee (if applicable) + speculation fee (if applicable).

As always, xUSD exchange fees will be automatically calculated and previewed for users in their Vault before transaction confirmation.

1*11g4NH-3KF1tbWp1BtwXHA.png

By implementing this model of varying fees based on unlock priority, the cost of any exchange based manipulation effort increases to such an extent that it no longer makes financial sense for a bad actor, while still ensuring users operating as good actors in the system can retain their desired full value from xUSD exchanges by opting for longer unlock times.

Finally, after the full suite of Haven’s private xAssets are released, a mechanism to provide trading fee credits will be implemented. These fee credits will be applied to wallets which utilize offshore trading functions (xAsset -> xAsset) and will not be transferable between wallets.

For example, when a user makes a trade between xUSD and xCNY, a small (~0.1%) trading fee will apply. 50% of that fee will then be credited to that user’s wallet as fee credits to be used only for moving between xUSD and XHV (on and offshore). Fee credits will therefore allow users of offshore trading and storage to reduce or remove onshore and offshore fees for their individual wallets.

We look forward to implementing this updated fee structure in the near future to ensure anyone in the world, on platforms large and small, can use Haven’s xUSD with confidence and ease.

Note: special thanks to Haven community member DougieWatts for suggesting a fee mechanism based on the age of Vault inputs to encourage xUSD storage on the network.

stat?event=post.clientViewed&referrerSource=full_rss&postId=e68123730902

View the full article

Snider
1*E0aW26yAuqk1S6pDG-90Og.png

The Haven team is thrilled with the successful launch of xUSD. For the first time, a USD stablecoin with Monero-grade privacy protections is now available to anyone in the world.

In just two weeks we have seen the use of xUSD skyrocket. This demonstrates that users are demanding a private stablecoin option in the market, and that Haven’s unique mint and burn protocol for xUSD exchanges is working flawlessly.

Unfortunately, the successful launch of xUSD also brought with it significant attempts to gain control of XHV supply by large holders focused on manipulation. We were surprised by the scale of these large manipulation attempts — at times involving 12% of the XHV supply — which began on the very first block after xUSD went live.

These attempts have continued because the current xUSD fee structure — while built to discourage manipulation — was circumvented by bad actors with large XHV holdings to reduce their market exposure, despite XHV volatility. The primary flaw in the existing xUSD fee structure is that it focuses too much on traders and not enough on mass adoption: xUSD investors and users.

This flaw needs to be fixed, at least in the short term, to protect the majority of Haven investors. The Haven team has recognized that the xUSD exchange structure must be modified to prevent attacks like this from continuing. Our current fee system is not set up to absorb large manipulation attempts of this scale.

As the Haven network matures, additional exchanges are added, and liquidity increases, these attempts will become less frequent and less successful. But at this early stage in xUSD’s existence, we believe it is important to implement a change to the xUSD fee structure to protect the long-term growth and adoption of Haven.

Here’s how the new fee structure will work:

The price quote for xUSD exchanges will not change. It will continue to be the 24-hour (720 block) Moving Average of XHV/USD as quoted by Chainlink’s decentralized oracle.

Unlock time options for xUSD exchanges will change to:

  • 6 hours (180 blocks)
  • 24 hours (720 blocks)
  • 48 hours (1440 blocks)
  • 7 days (5040 blocks)

xUSD exchange fees for these new unlock options will be as follows:

  • 6 hours: 20% of amount exchanged
  • 24 hours: 10% of amount exchanged
  • 48 hours: 5% of amount exchanged
  • 7 days: 0.2% of amount exchanged

We want to provide private stable money for everyone, not just a group of large XHV holders. This new fee structure is better suited for investors who buy XHV to privately lock in their crypto gains, and sell xUSD on the market to users who want to pay with it.

The most basic reason for this change is this: make manipulation unprofitable again. So that investors and honest actors can use the xUSD stablecoin to privately pay, transact, and lock in crypto gains without having to fear that some malicious actors might dramatically inflate XHV supply overnight.

A fork will be required to implement this change. We have not established a block height for the fork yet, but development work is almost complete and it will likely take place this week. All Haven pools have already been notified. We will continue to share additional details as we approach the fork.

Importantly, this change has the full support of the Haven community. We have been encouraged by our growing community who obviously want to see xUSD succeed on a much larger scale than we initially realized. We look forward to working together with our community as the ecosystem develops.

Several community members have also approached us with interesting ideas to discourage bad actors in more elegant manners, at least in theory. We will implement this change first, which can be done immediately, as protection of the network is paramount. But we greatly appreciate the input and will study all new ideas for their possible benefits and feasibility.

There will always be trade-offs between convenience for all Haven users and protection of the network from bad actors. We will continue to evaluate these trade-offs as the Haven ecosystem grows and respond accordingly in consultation with our community. Keep in mind: the future of financial privacy is just beginning.

stat?event=post.clientViewed&referrerSource=full_rss&postId=d80b1ae919e

View the full article

Snider
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

Snider
1*QB75gl4AxOteHOWWXshZqQ.png

The Haven team is thrilled to announce we will launch the first private stablecoin, xUSD, on Haven’s mainnet on July 20, 2020.

Below are some additional details about the launch of xUSD that we’d like to share:

  1. The launch will require a hard fork of Haven’s chain to implement the xUSD exchange code. We will announce the exact block height for this fork as we get closer to July 20th.
  2. All pools and exchanges will be required to update their nodes and wallets to incorporate the new xUSD code. We are in communication with all known exchanges and pools and will be happy to assist in preparation for the hard fork.
  3. The launch on July 20th will continue to be supported by Chainlink’s decentralized pricing oracle. The pricing record created by Chainlink’s oracle that will be used for each block header can be found here. We plan to add additional decentralized pricing oracles in the future.
  4. After xUSD launch, the circulating supplies of XHV and xUSD will fluctuate dynamically as a result of the mint & burn process at the core of Haven’s protocol. An updated block explorer will be released at mainnet launch that will publicly track the block-by-block supply of both XHV and xUSD.
  5. For Haven’s users — there is nothing you need to do to prepare for the hard fork. However, once xUSD is live on the network, you will need to use the latest version of the desktop Haven Vault or Command Line Interface (CLI) wallet for any xUSD exchanges or transfers. The Vault has undergone significant changes over the last few weeks, and we are confident it is ready for you to use as the first wallet to support xUSD. Stay tuned for announcements about mainnet Vault releases.
  6. The web-based Haven Vault will continue to serve as a user-friendly way to store and transact XHV. It will be updated for xUSD functionality at some point after July 20th.

Over the last several weeks, we have benefited from the help of our growing community to test the updated xUSD exchange code (released publicly on June 2nd) and the desktop Haven Vault. Since a community-led takeover in January 2019, the development of Haven has truly been a team effort, and we’d like to thank every community member who has given their time to this project. We also appreciate the assistance provided by developers in the Monero community to review and test the xUSD exchange code.

As many know, July 20th is celebrated around the world as Moon Day to commemorate the first time man first walked on the moon in 1969. When Neil Armstrong stepped down onto the moon’s cratered surface with the words, “That’s one small step for man, one giant leap for mankind, ” he proved we can move beyond our limits with new technology and the spirit to reach for the stars.

Haven hopes to provide another giant step for mankind. Against a backdrop of increasing economic instability and growing invasions of privacy around the world, July 20, 2020 will mark the beginning of a new option for financial freedom: the launch of the first private stablecoin xUSD on Haven’s synthetic asset ecosystem.

This technological leap ensures everyone around the world is able to easily access and privately protect their wealth. Prepare for launch, mint & burn!

Come join our community on Discord, Twitter, GitHub, and Medium. You can read more about Haven in this FAQ or the white paper.

stat?event=post.clientViewed&referrerSource=full_rss&postId=856b04c62065

View the full article

Snider
1*IR54Q-IdMR3mJSz2WFtYoQ.png

As described in the first deep dive post on May 15, Haven’s team spent the last several months redesigning Haven’s codebase. As a result, we have modified Monero’s commitment structure to implement the use of “colored coins” and enable a more secure and reliable xUSD exchange process.

The team began testing this new structure in private several weeks ago. During testing, we identified one key bug resulting from the modifications to Monero commitments: some onshore transactions failed due to the new “proof of value” verification process.

There are a maximum of 13 significant figures (digits) available for values smaller than 1 used on the Haven network. The problem is that XHV has a variable exchange rate and a variable number of coins being exchanged, including decimal parts. When multiplying (XHV coins) x (exchange rate) or dividing (XHV coins) / (exchange rate) for xUSD transactions, the resulting number may have too many significant digits to fit within the available 13, and the transaction would fail.

You can think of the problem this way: when exchanging XHV for xUSD, we used to say “offshore 100 XHV and turn it into xUSD.” To do this, we calculated how many xUSD we would get for 100 XHV. Let’s say the current exchange rate is 1 XHV = $0.33. In this example, we would get 33.3333333333333 xUSD (the fraction is recurring) for 100 XHV.

The problem arises when we go to verify the transaction’s value. On receipt of the 33.3333333333333 xUSD, we would say “convert that back to XHV to check the transaction used the correct amount of XHV to send.” But here’s the rub: 33.3333333333333 x 3 = 99.9999999999999. That does not equal the 100 XHV we sent. And the transaction would be rejected.

To resolve this problem, we have made two key changes to the xUSD code.

First, we are limiting all XHV and xUSD transactions generated in the Haven wallet to 4 decimal places to avoid the rounding errors which resulted in rejected transactions. Amounts generated automatically by the daemon (specifically block rewards for mining) are unchanged.

Second, we are reversing the “onshore” command in the code (xUSD to XHV) to require the amount being exchanged always be expressed in XHV. This will ensure xUSD exchange calculations are always multiplying (not dividing) a value, which will ensure values do not exceed 13 digits.

Both of these solutions were needed to resolve the bug that rejected some “onshore” xUSD transactions. We cannot allow transaction values to overflow 13 digits at any time, so we can never divide a decimal by another decimal to begin with — hence the need to reverse onshore commands in the code. When multiplying decimals, you end up with the sum of the number of decimal places of the two values. For example: (4.1234) x (4.123) = 17.0007782. So even though reversing onshore commands fixed the primary issue, we still need a limit to the number of decimals we can hold safely.

These two solutions have now been implemented and are being tested by the team in private. Once we are satisfied they work, and there are no additional bugs, we will provide the mainnet release candidate to the public for testing. We will also release an updated Haven Vault (GUI) for public testing in preparation for mainnet launch.

At that time, we plan to make available on Haven’s public GitHub repo the entire xUSD codebase we have been developing for more than a year. We believe public disclosure of the xUSD code is critical to Haven’s success in the long term and will provide an opportunity to strengthen the project through the assistance of other interested developers.

You’ll be able to view the xUSD code here when it is released. We will post a separate announcement when the code is shared to GitHub.

After sufficient public testing, we intend to announce a hard fork date and launch xUSD live on Haven’s mainnet. We have been in communication with exchanges and pools to ensure a successful mainnet launch.

As always, come join the Haven community and be part of the future of financial privacy. You can join our Discord and follow us on Twitter.

stat?event=post.clientViewed&referrerSource=full_rss&postId=3a1756571bbb

View the full article

Snider

The following is authored by @cryptodweab, Haven’s Project Lead

1*K6RLe1H4IUtirS1IzCRblw.png

Neac (Haven’s Protocol Lead) and I have spent the last several months preparing for the mainnet launch of xUSD. Throughout our testing, we’ve focused on how to most securely verify xUSD exchanges to ensure a smooth launch and long term success for this first private stablecoin.

This work has resulted in extensive redesigning of Haven’s codebase. As we learned in our testnets, Monero’s structure proved uniquely challenging for signing and verifying xUSD transactions. It has been tedious, slow, and at times downright frustrating. But we’re proud to say we’ve developed an innovative solution that will ensure the accuracy, reliability, and privacy of xUSD transactions now and in the future. Below is a deep dive into the process that led us to this solution.

Haven’s first testnet calculated an approximate value to tell users how much xUSD they would receive for the XHV they requested to exchange. This is because in Monero (and Cryptonote), when users submit a transaction, they are sending a commitment to a number of coins: both inputs and outputs. These inputs and outputs need to be equal or the transaction will always fail.

This Monero structure became a problem for Haven when we began implementing xUSD exchanges. Initially, we could not guarantee the final amount of xUSD exchanged would equal the approximate amount of xUSD quoted before a transaction was submitted. This is because the XHV price changes dynamically. The XHV price (and thus, the xUSD exchange rate) could change between the time a user submitted a transaction and when the transaction was confirmed.

The first way we approached a solution to this challenge was by no longer looking for equality of inputs and outputs. But in order to prevent manipulation, we needed the sender to be unable to specify a false amount. So we decided to take this step out of the sender’s hands entirely and give that responsibility to the miner.

This solution, implemented in a subsequent testnet, added a delay in providing the exact xUSD exchange rate. The sender would have to wait for a block to be mined, and the miner had to include the exchange price in the block header. However, there were holes in this solution — nasty ones.

Imagine an adversarial attacker with both the money and the knowledge of this part of Haven’s code. After setting up the infrastructure to obtain 51% of Haven’s hash, they could become both the miner and sender and thus set their own xUSD exchange rates. This possibility was, shall we say, suboptimal!

So in the next testnet, we decided to move the responsibility back to the sender, but only so they could take the last verified pricing record already in Haven’s chain (the pricing record from the top block) and specify which block they used in the transaction. This could be checked and verified by miners and daemons, who could also check that inputs vs. outputs were equal not in coins, but in dollar value (critical for xUSD).

This proof of value became the key to Haven’s success. But the model described above also proved vulnerable to attack. Several lessons came out of the next few xUSD testnets conducted with our team and community. First, we learned that a shorter chain could game the system. Second, we learned we needed a way to show the circulating supply of xUSD (and future xAssets) or we could never determine the health of Haven’s network.

The next stage of development took us down a different path. As stated above, proving a transaction’s value was the key, and we needed to replace the proof of Monero inputs = outputs with the proof of dollar value for xUSD exchanges.

We tried over a dozen different proofs, checks, and validations. But we found that unless you’re actually sending XHV and no other type of asset, which in private testing is what we were doing, the whole system gets confused after a few backwards and forwards transactions. The more complex the exchanges, the harder it got to verify a transaction’s dollar value. Then throw in multiple transactions, which needed to span large amounts of inputs, and things got really tangled.

These challenges were all related to the way commitment signatures work, which is an absolute requirement in Monero. Unless your commitments are valid, you can never verify the money hasn’t been created from nowhere.

At this point, we decided to review the old model of “colored coins” which has previously been layered on top of Bitcoin, creating a new set of information about coins being exchanged. Using colored coins, transactions could be “colored” with specific attributes. This effectively turns colored coins into tokens, which can be used to represent anything. But — and this is critical — colored coins can only work if you’re not tied to Monero’s commitment structure.

So that is the challenge we undertook: modifying Monero’s commitment structure to allow for the use of “colored coins” which can distinguish between XHV, xUSD, and future xAssets on a single Monero-based chain. And I’m proud to share that for the first time, we’ve done exactly that.

We had to replace Monero’s multilayered linkable spontaneous anonymous group (MLSAG) signatures with the newer compact linkable spontaneous anonymous group (CLSAG) signatures to accomplish this. But with a little help from one of Monero’s top developers, Sarang Noether, the solution is now working as intended. We’d like to thank Sarang for his assistance in helping us navigate this new encryption scheme.

So the result of all this testing and tinkering is the following: we have created a new transaction structure with genuine inputs as XHV and genuine outputs as xUSD. To convert from XHV to xUSD, we actually give XHV as inputs and xUSD as outputs. Daemons then check that the number of outputs is equal based on the exchange rate given in the block the sender specified as the pricing record. This is done purely by summing the commitment masks and the exchange rate independently retrieved by verifiers.

The logic is that a verifier will always get its own exchange rate. So the only way a sender can get a transaction through is to know both that exact exchange rate and the exact number of inputs (which only they can know since it’s in their wallet and unreadable elsewhere). The verifier then sums the output commitments, and taking into account their independently gained exchange rate, compares that to the inputs. They must be equal to pass. Of course, all values are encrypted so no one can see or alter the amounts.

Note: the sender can only use an already verified pricing record, which are all currently created via Chainlink’s XHV oracle. Daemons read the pricing record number in the transaction and get the record (the actual price) from the block header. This means prices are already immutable at time of use.

This is exactly the type of solution we were searching for after contemplating how to address challenges associated with xUSD exchange verification in the very first testnet. This solution is working nicely in our private testing and will be shared in our next public stagenet in the coming days.

Assuming no other issues are identified in testing, this is the solution we will use to launch xUSD live on Haven’s mainnet. As a part of the launch process, we look forward to sharing publicly the xUSD exchange code we’ve developed in private over the last year to create the first-ever private stablecoin.

In the meantime, come join the Haven community and be part of the future of financial privacy. You can join our Discord and follow us on Twitter.

stat?event=post.clientViewed&referrerSource=full_rss&postId=8b5c7bd5f42

View the full article

Snider
1*waoRW8p43wTFiOKjyphXFg.png

In spite of global uncertainty and volatility, it has been a very productive week for Haven’s xUSD stagenet in large part due to community participation.

A silver lining in last week’s market volatility is that we’ve had an ideal environment to test the xUSD exchange process, the Chainlink pricing oracle, xUSD exchange time locks, and the xUSD fee structure and calculation.

As a result of our testing, we’ve identified the following three issues that have now been fixed:

1) Fees for low priority xUSD exchanges were being calculated incorrectly. The low priority fee was being calculated using a 0.7% delta percentage instead of the required 0.28%. (See below for more detail on xUSD exchange fee calculations).

2) Large xUSD exchanges (generally over 10,000 XHV) were being split, resulting in some failed transactions, as a result of a broken RPC mechanism.

3) Circulating supply totals were affected by the above transaction issue.

The calculation of xUSD exchange fees, based on the variable time lock structure, is a key feature that warrants additional discussion in this post. This feature was implemented to prevent manipulation of Haven’s exchange process, particularly in times of significant market volatility, like we saw this past week.

As described in Haven’s whitepaper, the formula for calculating xUSD exchange fees uses a percentage of the delta between the XHV 12-hour moving average and the XHV spot price. You can find these quotes updated in real-time, utilizing Chainlink’s decentralized price feeds, on the Haven oracle here. “xUSD” is the spot price and “unused1” is the 12-hour MA.

The fee formula uses the following percentages for each xUSD exchange unlock priority:

  • High priority (60 blocks, ~2 hours): 100% of delta
  • Medium priority (180 blocks, ~6 hours): 63.61% of delta
  • Normal priority (540 blocks, ~18 hours): 16.37% of delta
  • Low priority (1,620 blocks, ~2 days): 0.28% of delta

The simplest way to determine the xUSD exchange fee is by using this calculation:

[Amount of XHV] x [Priority fee %] x [Delta of MA/spot] / [MA price].

An example: the 12-hour MA is $0.40 and the spot price is $0.30. The delta is $0.10. The fee for a low priority exchange of 1000 XHV would be calculated as:

[1000XHV x 0.0028 x $0.10 / $0.40] = 0.7 XHV.

That’s less than a 0.1% fee for exchanging 1000 XHV to xUSD. Fees obviously rise significantly as the delta between spot and 12 hour MA grows during volatility, and as you use a higher priority.

The delta between a $0.30 spot and $0.40 MA is significant: 33% of the spot price. A delta of this size occurred frequently during Bitcoin’s volatility last week. Right now the spread is much smaller: $0.1911 spot and $0.1880 MA: just 1.6%. This is an example of the feature working well to prevent manipulation, especially in times of significant volatility.

The testing over the past week supports the protocol design as an effective deterrent against manipulation. It would be incredibly difficult and expensive to game the xUSD exchange process, particularly in times of market volatility.

To implement the necessary changes identified in testing, we’ve restarted the stagenet from the genesis block, including the explorer and circulating supply totals. Previous stagenet wallet addresses will still work, but balances will be reset. We’d recommend creating a new wallet and starting from scratch.

Team and community members are happy to provide test funds in Discord for anyone who’d like to participate in the stagenet.

Below are links to the updated stagenet Haven Vault. Thanks to everyone for your help and contribution!

MacOS: https://github.com/haven-protocol-org/haven-web-app/releases/download/v1.2.0/Haven-macos-x64-1.2.0.zip

Windows: https://github.com/haven-protocol-org/haven-web-app/releases/download/v1.2.0/Haven-win-1.2.0.Setup.exe

stat?event=post.clientViewed&referrerSource=full_rss&postId=ad81b211d238

View the full article

Snider
1*p6VDL7N_5CflzKiOFNG_hg.png

We are excited to announce that Haven is collaborating with Chainlink to provide a decentralized oracle service for XHV, xUSD, and all future xAssets.

Haven is a Monero-based protocol for creating private stablecoins and assets. Haven’s first private stablecoin, xUSD, will allow anyone to store and transfer their money with complete privacy.

While initially planned as a future network upgrade, Chainlink’s services will now be used for the mainnet launch of Haven’s first private stablecoin, xUSD. This is an important step towards our goal of decentralization and censorship resistance and reinforces Haven’s commitment to private decentralized finance.

During protocol development, the Haven team has been conscious of the need to remove any perceived control over the price feeds that underpin the network. To achieve this, the design intends to allow for a variety of oracle providers, which is scalable over time.

In the early stages, we had discussions with the Zel team about a solution. Due to project timing and logistics, that work has been temporarily put on hold. Furthermore, over the last few months, the vision for Haven expanded from only providing private stablecoins to also adding the ability for more complex decentralized finance applications.

The need for versatile and well-distributed data providers is something deemed essential for the launch of xUSD on mainnet. Chainlink is now able to assist Haven with this crucial piece of project infrastructure.

Chainlink is rapidly becoming one of the most respected and capable oracle solutions in the crypto space. They have a reputation for security and reliability, used by large enterprises, major exchanges, and other DeFi projects. We feel this is a great match for the ambitions of Haven and the projected growth we anticipate over the coming months and years.

Importantly, Haven is the first Monero-based project to collaborate with Chainlink on oracle services.

Today we are launching the xUSD stagenet for public testing before mainnet launch. This stagenet incorporates a custom Chainlink oracle for XHV to xUSD exchanges. xUSD will act as the base layer for building out the Haven network to be a leading provider of private decentralized finance. More information about participating in the stagenet can be found here.

Johann Eid, Product Manager on Chainlink, stated, “We’re excited to foster the growth of a privacy-focused project like Haven by providing their critical protocol with secure, decentralized price data. Their private stablecoin network contributes to user’s privacy in a DeFi ecosystem and we’re glad Chainlink can help make that a reality via quality market data sourcing.”

About Chainlink

If you’re a developer and want to connect your smart contract to existing data and infrastructure outside the underlying blockchain, reach out to Chainlink here! They can help you quickly and securely launch your data-enabled application or Chainlink Price Reference Data Contract on mainnet today. You can also visit the developer documentation or join the technical discussion on Discord. Learn more by visiting the Chainlink website or follow them on Twitter or Reddit.

Chainlink is a decentralized oracle network that enables smart contracts to securely access off-chain data feeds, web APIs, and traditional bank payments. Chainlink is consistently selected as one of the top blockchain technologies by leading independent research firms such as Gartner. It is well known for providing highly secure and reliable oracles to large enterprises (Google, Oracle and SWIFT) and leading smart contract development teams such as Polkadot/Substrate, Synthetix, Loopring, Aave, OpenLaw, Etherisc, Conflux, and many others.

stat?event=post.clientViewed&referrerSource=full_rss&postId=28fce90b3797

View the full article

Snider
1*Pihbeoc-Jg22mT5gaAMt5g.pngThe Haven Vault has been updated for xUSD stagenet

Today Haven is launching a stagenet for its first private stablecoin, xUSD. The stagenet deploys a new daemon and utilizes a Chainlink pricing oracle. Below are some additional details and instructions for participating.

Testnet vs. stagenet

We’ve built out a more complete testing suite to accommodate different tiers of testing. This is in keeping with standard software production processes. The network inherited by the current Haven team (early 2019) used an incomplete testnet (e.g. no wallet address for governance, code lacking the proper logic, etc).

Moving forward, our development environments will look like this:

Mainnet = live production environment.

Stagenet = staging area for (typically public) testing of code for next release.

Testnet = (normally private) area for testing of internal-only code/new features.

We spent several days trying to reboot the existing testnet to implement the new daemon and Chainlink oracle, but this resulted in a large number of legacy transactions. So the decision was made to prepare a clean stagenet for public launch and for protocol upgrades going forward.

Stagenet is technically a step closer to mainnet launch, both in terms of features and consensus rules.

Participate in the xUSD stagenet

We would like to invite anyone interested in trying out the xUSD exchange process to join the stagenet. Below are some important instructions for participating. Please read them carefully.

You can download the stagenet Haven Vault here:

MacOS: https://github.com/haven-protocol-org/haven-web-app/releases/download/v1.1.0/Haven-macos-x64-1.1.0.zip

Windows: https://github.com/haven-protocol-org/haven-web-app/releases/download/v1.1.0/Haven-win-1.1.0.Setup.exe

Please note: this is only a stagenet using test addresses and test XHV. Do not send any real XHV to a stagenet address. All Haven stagenet addresses begin with “hvs…”.

To receive test funds, you can either enable background mining of XHV (under the “Settings” tab) or you can join the testing channel in Haven’s Discord and post your Vault address. There are many active team and community members in this channel who would be happy to send you test funds.

Please try out all the features included in the Vault. The most important are the exchange functions: XHV to xUSD and xUSD to XHV. The stagenet explorer can be found here. The decentralized pricing oracle, utilizing values provided by Chainlink, can be found here.

Chainlink oracle

We have successfully deployed a custom XHV/USD oracle with the Chainlink team. We are using this oracle for today’s stagenet testing and will use it for the mainnet launch of xUSD. More details about our collaboration with Chainlink will be available shortly.

Supply transparency

Providing a public and transparent way to calculate the circulating supply of xUSD (and future xAssets) has been a key development priority for the Haven team over the last few months. It also proved to be a significant technical challenge. The circulating supply solution is now fully coded and RPC calls are working as planned in stagenet testing.

This was accomplished by adding a publicly verifiable supply amount to each xUSD exchange transaction. By adding a second amount (which, prior to masking is identical to the first amount), any wallet or interested party can sum up the unspent outs for xAsset exchange transactions to audit circulating supply for both.

Once on mainnet, this can be done via the Haven explorer and be made available publicly. We believe this solution offers the minimal possible amount of visible data points while staying true to the principle of auditability for private cryptocurrencies. Importantly, this does not compromise the privacy of user addresses, balances, or transactions.

xUSD exchange fees

xUSD exchange fees were implemented to punish manipulation attempts, not to tax network usage. These fees were proven to be very low in the previous xUSD testnet. For most exchange transactions, fees are zero or very close to zero. We will handle these fees transparently and discuss their current future use with the community.

In the new daemon, XHV to xUSD exchange fees are now being successfully directed to the Haven governance wallet. The inputs and outputs from wallets are all matching up as we hoped and we’re seeing xUSD in the governance wallet as planned.

The correct implementation of fees has been complicated but is complete. For example, the team discovered xUSD to XHV fees were being paid for in xUSD, but then landing (as the same number not the same value) in the miner_tx as XHV. This has been corrected.

Governance wallet funds are used to support our full-time developers and costs associated with project infrastructure, legal, and marketing activities. We plan to continue consulting with the Haven community about the use of these funds moving forward.

Timing for mainnet launch of xUSD

Today’s stagenet launch of xUSD, utilizing a new daemon and the Chainlink oracle, is a critical step forward in our preparations for mainnet launch.

There is more testing to do over the coming days, but we expect to be able to announce a xUSD mainnet launch date soon, barring any unforeseen delays.

stat?event=post.clientViewed&referrerSource=full_rss&postId=f77b68691e1c

View the full article

Snider
1*R2JYtV7Vjm8R01KuMzZJgg.png

The Haven Currency

The base currency for the Haven network is XHV. Haven is a Proof-of-Work (PoW) cryptocurrency based on the CryptoNote protocol with a block time of two minutes.

Haven is built on top of Monero, which is widely considered to be the leader in privacy technology. Haven inherits all of Monero’s privacy features. It extends this functionality by providing private, stable currencies and commodities (xAssets) which can only exist through the “burning” of the Haven base currency (XHV). The first private stablecoin to be launched on Haven’s mainent will be xUSD.

How many XHV coins are there?

The real-time circulating supply can be found here. As of January 28, 2020, the circulating supply of XHV is 11,546,892.

When xUSD (and future xAssets) are launched live on the Haven network, the circulating supply of XHV will fluctuate dynamically according to market supply and demand.

As people find utility in using xUSD (and future xAssets), XHV will need to be burned. It is important to keep in mind that the initial supply of every newly integrated xAsset will always be zero. Therefore, a reduction in supply of XHV can be expected in the short term. But in some market cycles, the supply of XHV could be increased. Proof-of-Work mining will always provide XHV liquidity and secure the Haven network.

Modeling of different supply scenarios in bull and bear markets can be found in our Whitepaper. Haven’s tail emission is the same as Monero.

Was there an ICO (Initial Coin Offering)?

No, there was no ICO.

How is the project funded?

Most of Haven’s team work on a voluntary basis and receive no payment for their input into the project. However, Haven’s core developers do receive compensation in the form of XHV due to the large number of hours they dedicate to working on the project. This funding comes from a 5% governance fee raised from the mining of XHV. It is spent on essential infrastructure and development costs for the project.

All governance funds are deposited into a team owned multi-signature wallet. This wallet is visible to anyone, and the financial decisions are made by a remuneration group made up of Haven’s team and community members.

Multi-signature governance wallet:

hvxy3f2PhAhimkeLf617BsbVn6UTbofVcMzofXGsSNLoMFr2SrSxRJ9f52Am1QLVddKetXPKHoTLbBaLNT1kMU6Q3kYRc3t6pF

Private wallet viewkey:

b8679ce8084f489cc070537941f683ecfaac65321c2e6e73891d7ae10bc3e102

What can Haven be used for?

Storage

Anyone who wants to store value outside of the traditional banking system can do so without giving up their privacy and control. Only you can access and use your money with Haven.

Trading

Traders can enter the Haven network and either use their Vault as a secure storage method or trade XHV and xAsset pairs. After mainnet launch of xUSD, Haven will offer a range of fiat currencies over time (like xEUR), as well as xBTC (Bitcoin) and other high profile commodities (xGOLD and xSILV). This will provide traders a range of benefits in the Haven Vault:

  • Infinite liquidity
  • Zero spread/slippage
  • No counterparty risk
  • No KYC/AML requirements
  • No limit on trading amounts
  • Full control of private keys
  • Private transactions and account balances

Payments

Haven could be used for any purchases where privacy and security is a priority and instant settlement is not required. As the Haven network grows and more projects are built on top of the protocol, payment use cases will expand.

Haven’s privacy features

How are my funds protected?

Haven uses the same robust privacy features as Monero including ring signatures, ring confidential transactions (Ring CT), stealth addresses, and bulletproofs.

Are Haven transactions private?

These Monero-based features hide the sender, amount, and receiver in every transaction. All transactions are private by default and there is no way to accidentally make a transparent transaction. Further information on Haven’s privacy features can be found in the Whitepaper.

As part of these privacy features, Haven has a unique way of processing transactions. This may seem confusing to new users but can be explained by the following:

Alice has 20 XHV in her vault. She has received 2 lots of 10 XHV from friends.

She sends 5 XHV to Bob.

The 5 XHV she sends is taken from one of the 10 XHV amounts she received.

This 10 XHV gets locked up until the transaction is complete and Alice receives her change of 5 XHV (less the tx fee).

You can think of it like giving out a note and waiting for the change in coins.

Why does Haven need privacy?

Like any other traditional financial account, the Haven Vault will contain sensitive information that a user would not want to be made available publicly. This is especially true for personal financial data that, if stolen, can be used by unscrupulous parties to potentially steal those funds. The privacy features of Haven makes this much less likely to happen.

IMPORTANT

Although Haven transactions are private and anonymous, they should not be used for illicit or illegal purposes that may violate a user’s local or national laws.

Storing and Using Haven

Where can I obtain XHV?

Haven (XHV) is available to purchase from a number of exchanges, including Bittrex, TradeOgre, Citex, VCC Exchange, and Abra. As a Proof-of-Work cryptocurrency, it can also be mined. The current list of exchanges and mining pools are on our website. We are always working to add additional exchange and fiat on-ramp options.

How do I exchange XHV for xUSD?

Haven utilizes a unique “mint and burn” process to exchange XHV for xUSD (and vice-versa). You can exchange (burn) XHV for the equivalent USD value worth of xUSD. 1 xUSD will always be worth $1 of XHV at the current market price. This process will always take place instantly inside your private Haven Vault. All transactions utilize Monero features to maintain your privacy.

Here’s an example: you buy 200 XHV at $2 each. You then exchange 200 XHV in your private Haven Vault and receive 400 xUSD (the 200 XHV is burned). Later, you decide to exchange your xUSD back to XHV, but the price of XHV is now $4. Your Haven Vault would burn the 400 xUSD and you would receive 100 XHV.

How do I store my money?

Your funds are stored in a digital vault called the Haven Vault. You can think of this as a private account that only you control. You can access the web-based Haven Vault (optimized for mobile platforms) here. The Haven Vault will be available for all major operating systems including Windows, MacOS and Linux after the launch of xUSD on Haven’s mainnet. There are different options according to your needs:

Web Vault

This is the simplest method for those using computers who do not wish to run their own node. The Vault’s architecture ensures the security of your seed or keys, as they are never submitted to a server or sent across the internet.

Desktop Vault

This is downloaded as an app on your computer and provides a simple-to-use Vault for storing XHV and all Haven assets. This Vault gives you the option of using a local or remote node. It also includes a “smart miner” that helps decentralize and secure the Haven network while giving you the possibility of earning some XHV as a reward.

CLI Vault (Command Line Interface)

This is generally used by those with a greater technical background and a working knowledge of the terminal on their computer.

Mobile Vault

This is for those who prefer the convenience of keeping their funds stored on a mobile device. The Web Vault is compatible with all mobile devices and native mobile apps will be developed in the future. You will also be able to store your XHV on hardware wallets such as Ledger Nano S after integration work is completed.

I see there are different nodes, what are they?

A node is basically a computer that connects you to a network. Haven is a peer-to-peer network. There are generally two different types of nodes that you can use to connect to the Haven network. Each has pros and cons that will be explained below:

Remote Node

A remote node is a 3rd party computer that syncs to the Haven network on your behalf. Because you don’t need to download and update the chain every time you open your Vault, syncing and updating your balances take a fraction of the time it would take using local node. This can be helpful if you have limited storage space on the device you use your Vault with.

Choose this option if you want to quickly open a Vault and for sending/checking balances and only from trusted third parties. There can be risks associated with using a remote node as it increases the chances of somebody being able to identify your IP address to trace transactions from your Vault address. The current list of trusted remote nodes available to users will be on the Haven website.

Local Node

A local node means that you are using your own computer to connect to the Haven network. With a local node, you are in control of all the data on the chain and there is less risk of anyone being able to see if you have a Vault open or determine your IP address. Local nodes are in your control so you don’t have to worry about them being down when you want to login to your Vault and move funds around.

During major market movements there is a possibility that high traffic volume can cause issues with a remote node leaving you stuck trying to find another one or syncing your own. This will not happen if you use a local node.

The drawback to using a local node is that you will have to download and regularly sync (update) the blockchain. This can take some time and will use a significant amount of storage space on your device. It is, however, by far the most secure method of using Haven for longer term wealth storage and is recommended for any significant amounts being stored.

Can I send my money to anyone I want?

Yes, as long as they have a Haven Vault you can send XHV or xAssets to anyone in the world quickly, securely and cheaply. You will need to know their Haven Vault address to do this.

Can I get some help using the wallets?

Absolutely, there will be Vault user guides on our website once xUSD goes live on the Haven mainnet. These will go through the set-up, use, and recovery of Vault addresses step-by-step instructions to enable even non-technical users to be able to take control of their money and be sure it is secure and easily accessible. You can also get in touch on Twitter or join our Discord group where the team and community members are always happy to help.

Is it safe to use Haven?

Your Vault is protected by a password (or seed phrase for the Web Vault) that you set and must remember in order to access your funds. During the process of setting up the Vault, you will also be given a 25 word seed phrase. Should you lose your password you can restore your wallet and access your funds using this combination of words. It is essential that you keep one or more copies of the seed phrase somewhere safe.

IMPORTANT

You are responsible for your funds and no one else can help you recover them should you lose your password or seed phrase.

How can I ‘cash out’ my XHV?

You can exchange your XHV for BTC, USD or other traditional currencies where exchanges (such as Bittrex) have the facility to do so.

stat?event=post.clientViewed&referrerSource=full_rss&postId=a86bed3148a2

View the full article

Snider
1*_2W0_VTZL-6G2zQ2AeBniw.png

On the heels of a public test phase, the Haven team has been busy preparing for the mainnet launch of xUSD. The bulk of our work has focused on completing development of a new Haven daemon to make key enhancements and address issues identified by community members in the public testnet.

We’re excited to share these improvements and grateful for the community participation that led to them. The following is an in-depth look at what’s happening.

A New Haven Daemon

The Haven daemon is a program operating in the background that synchronizes a Vault with the Haven network, scans for incoming transactions, and sends new transactions. Most importantly, the daemon also enables xUSD exchanges by retrieving the exchange price from the pricing oracle and submitting it along with each xUSD transaction.

In advance of xUSD mainnet launch, updates have been made to the daemon to enable (1) support of additional xAssets in the future; (2) supply transparency of xAssets; and (3) a new mechanism by which pricing records are embedded in each transaction.

Here’s a little more information on issue (3): previous versions of the Haven daemon, including the version currently running on the public xUSD testnet, provide a quote of the XHV to xUSD exchange price at the time a user submits a transaction. However, the final exchange price for each transaction is not included in the block header until that block is actually mined.

This gap in time — between when a user submits a transaction and when the transaction is mined — is usually not very long. Under normal circumstances, it averages only a few minutes. But under heavy network activity, this gap can grow significantly. That means some transactions are forced to wait behind other transactions before being given a final price by being added to a block.

If left unresolved, this could create a situation where the xUSD exchange price a user sees in their Vault is not the same as the final transaction price.

While the new daemon will be invisible to users in their Haven Vault, this update makes a significant and crucial change to the xUSD exchange process. The new Haven daemon changes the time at which pricing information is taken for xUSD exchange transactions.

Pricing information will now be included for each transaction at the time of a user’s submission in the Haven Vault, instead of when a transaction is mined. As a result, the xUSD exchange rate will always be accurate and equal to the price displayed to a user at the time of a transaction.

Development work on this entirely new Haven daemon has been time consuming. It is now coded and has been deployed for private team testing with success.

As stated above, the new daemon will also enable the use of additional xAssets in the future (such as xEUR, xGOLD, xBTC, etc) and allow for the implementation of a transparent supply of xAssets.

As you may recall, the Haven community and team elected to enable visibility of all XHV and xAsset circulating supply numbers while retaining full privacy for transactions, balances, and addresses. This will allow more efficient monitoring of the Haven network, greater user confidence to enter the Haven network, and more precise analysis on coin metrics websites.

In final preparation for the xUSD mainnet launch, these significant changes to the Haven codebase will require us to fork the testnet in the coming days and deploy the new Haven daemon for testing. We look forward to the feedback from this round and appreciate your participation.

The updated code for the new daemon will be released to pools and exchanges when we announce the date for xUSD mainnet launch. It will then be released publicly as open source code, along with the xUSD exchange codebase, when xUSD goes live on Haven’s mainnet.

Supply transparency and testnet fixes

The solution to enable supply transparency of xUSD and future xAssets will be detailed in a Medium post soon. This post will include technical explanations and a summary of how we plan to maintain Monero’s privacy standards while enabling the desired supply transparency.

We’re also working to address a small number of UI issues identified by the community in the xUSD testnet, including displaying total Vault balances, improving transaction status messages, and making it easier to identify asset balances when exchanging. Finally, we’re addressing an issue identified in testnet that in some cases shortens xUSD unlock times if a user is not fully synced to the blockchain.

Haven would like to thank our community members who helped identify and discuss these issues during the xUSD testnet. Our collective efforts have made the Haven network more secure and reliable in preparation for mainnet launch of xUSD.

Next steps

Carefully completing all of the work outlined above is essential to successfully launching xUSD. In the coming days, the testnet will be forked to deploy the new Haven daemon. We will then announce the specific xUSD launch date in Part 2 of this Medium article.

The nature of building innovative new technology is that work does come up with unknown time requirements for completion. With that being said, we are on track to complete the mainnet hard fork and launch xUSD in February or early March.

stat?event=post.clientViewed&referrerSource=full_rss&postId=46d614382d4d

View the full article

Snider
1*xy9jQiA-5VwtRzr4jjBBnQ.png

Today the Haven team is excited to release the final stage of the xUSD public testnet in preparation for mainnet launch. All xUSD offshoring and onshoring exchange functions have been successfully integrated into a new desktop Haven Vault.

The desktop Vault shares the same simple, intuitive user interface as the web-based Haven Vault. This desktop vault will serve as the first place xUSD is launched on Haven’s mainnet.

We would like to invite anyone interested in trying out the xUSD exchange process to join the testnet. Below are some important instructions for participating. Please read them carefully.

You can download the testnet Haven Vault here:

Please note: this is only a testnet using test addresses and test XHV. Do not send any real XHV to a testnet address. All Haven testnet addresses begin with “xvt…”.

If you participated in the first stage of Haven’s xUSD testnet using the command line interface (CLI) wallet, please delete any old testnet folders on your machine to ensure you’re able to properly synch with the testnet chain.

To receive test funds, you can either enable background mining of XHV (under the “Settings” tab) or you can join the testnet channel in Haven’s Discord and post your Vault address. There are many active team and community members in this channel who would be happy to send you test funds.

Please try out all the features included in the Vault. The most important functions are the xUSD offshore (XHV to xUSD) and onshore (xUSD to XHV) exchange functions.

Exchanging (or offshoring) XHV for xUSD works like this: You select the amount of XHV to exchange and see the current exchange rate. The xUSD value is calculated in real time and then you confirm the exchange. The pending exchange transaction displays until the transaction is confirmed. In the interim, the amount of time left to unlock the newly-minted xUSD is displayed in the history tab for each transaction.

The onshore process (exchanging xUSD for XHV) happens in the exact same manner, only with the assets reversed. At any point, you can toggle between XHV and xUSD balances. Separate tabs for each asset show transaction details, price history, time left to unlock pending transactions, and more.

Additional xUSD exchange functions are now included in an “Advanced” field in the “Exchange” tab. These include selecting different xUSD unlock times and exchanging XHV for xUSD directly to another address.

The Haven Vault runs automatically on its own local node in the background. The option to select a remote node, which allows for faster synching of the Haven blockchain, will be available for mainnet launch of xUSD. However, synching the Haven Vault with this testnet should only take 10–15 minutes. The testnet explorer can be found here.

As mentioned previously, there is a “Start Mining” option now included in the “Settings” tab. Please consider enabling this function to help the testnet network. If you select this option, testnet XHV funds will be mined directly to your Vault address in the background. Note: if you enable the mining function from a laptop computer, it will be need to be plugged in to a power source to work.

Haven’s developers have worked through a number of troubleshooting tasks in the Haven Vault over the last few weeks. However, there may be some small things you notice that don’t look right. You may also have requests for additional features in the Vault.

Please point these out to the team in our Discord channel by tagging your message with either #bug or #feature. Give the team as much information or screenshots as possible so they can log any issues and keep track of them. After all, this is why we are conducting a robust xUSD testnet before approaching mainnet launch.

Finally, if you have any questions about the new Haven Vault, the xUSD testnet, or how offshoring and onshoring exchanges work, please ask them either in the Haven Discord or on Twitter.

stat?event=post.clientViewed&referrerSource=full_rss&postId=c3625a35705

View the full article

Snider
1*PZV8vxkWUUB-y1vUb5trxw.png

xUSD: The First Private Stablecoin from Haven

The Haven team and community has made significant progress over the last year building the first truly private stablecoin: xUSD. The mainnet launch of xUSD is now just weeks away. This post provides a detailed look into the preparations being made for the launch.

When xUSD goes live, the Haven network will provide anyone in the world with access to xUSD exchange liquidity in the Haven Vault; fully anonymous addresses, balances, and transactions using Monero-based privacy features; and complete control over their money at all times.

xUSD will serve as the foundation for a completely private, decentralized finance ecosystem in the months and years to come.

Most importantly, Haven will become the secure place to control and store your money in private stablecoins.

Development of Desktop Haven Vault

Over the last month, Haven’s developers integrated all the offshoring and onshoring functions into a new desktop Haven Vault. The desktop Vault shares the same simple, intuitive user interface as the web-based Haven Vault. The desktop Vault will serve as the first place xUSD is launched on Haven’s mainnet.

Exchanging (or offshoring) XHV for xUSD works like this: Users select the amount of XHV to exchange and see the current exchange rate. The xUSD value is calculated in real time and the user confirms the exchange. The pending exchange transaction displays until the transaction is confirmed. In the interim, the amount of time left to unlock the newly-minted xUSD is displayed in the history tab for each transaction.

The onshore process (exchanging xUSD for XHV) happens in the exact same manner, only with the assets reversed.

At any point, users can toggle between XHV and xUSD balances. Separate tabs for each asset show transaction details, price history, time left to unlock pending transactions, and more.

It is important to note xUSD can only be exchanged directly against XHV. As XHV is Haven’s base currency, burning XHV is the only way to create xUSD. 1 xUSD will always be worth $1 worth of XHV.

Final Phase of Public Testnet

In November, the Haven community conducted the first public testnet of xUSD and Haven’s offshore exchange functions. For the first time, users tested offshore (XHV to xUSD) and onshore (xUSD to XHV) exchanges in a command line interface (CLI) wallet. The xUSD testnet has now been live for over a month and has grown to over 50,000 blocks. Hundreds of XHV to xUSD and xUSD to XHV exchanges have been successfully completed.

The final phase of the public testnet will be conducted using the native desktop Haven Vault as described above. Both macOS and Windows builds of these Vaults have been completed and tested internally by the team. A video of this initial round of testing can be found here. A final round of minor fixes to the user interface are being completed now. Public release of the desktop Haven Vault testnet will begin in the coming days. A Linux version of the desktop Haven Vault will be available closer to mainnet launch.

Time-Lock Structure for xUSD Exchanges

Haven uses a unique time-lock structure to determine unlock times for xUSD exchanges within the Haven Vault. The use of this function is designed to reduce the incentive for bad actors while offering optimal conversion times for users.

Without these time-locks, someone looking to manipulate the xUSD exchange process could utilize infinite liquidity in the Haven Vault and rapidly exchange between XHV and xUSD with no restrictions. Instant unlocking of xUSD transactions, while appealing to users, would encourage attempts to manipulate the exchange process.

We have considered several other options to deter manipulation of the xUSD exchange process — such as defined percentage-based fees for each xUSD exchange — but decided the use of time-locks would be most beneficial to users.

Haven offers four different unlock times for users to select:

· Unimportant — xUSD is unlocked in 1,620 blocks or about 2 days

· Normal — xUSD is unlocked in 540 blocks or about 18 hours

· Elevated — xUSD is unlocked in 180 blocks or about 6 hours

· Priority — xUSD is unlocked in 60 blocks or about 2 hours

xUSD transaction fees are calculated using a decay formula based on the difference between the XHV exchange price (which uses a moving average, described below) and the current spot price. Fees start at almost zero for the slowest unlock times and increase for the faster unlock times. This results in higher fees in times of high price volatility for faster transactions. A more detailed explanation of this formula can be found in the Haven whitepaper.

During the final public testnet, the default xUSD exchange time-lock will be set at “priority” (about 2 hours). The default xUSD exchange time-lock for mainnet launch is still under consideration by the Haven team, and can be implemented readily when deemed safe and optimal. Unlock times can always be changed by users in their Vault.

Moving Averages for xUSD Exchanges

In addition to the time-lock structure, Haven also utilizes a moving average to determine price quotes for xUSD exchanges.

The ongoing testnet uses a 12 hour moving average to determine XHV price when exchanging to xUSD. A 12 hour moving average is short enough to provide certainty for users (by staying closer to the XHV spot price), but long enough to deter exchange-based manipulation for the sake of xUSD exchanges. Longer moving averages (such as several days) have been considered by the Haven team. However, a longer moving average would make it more difficult for users to effectively plan their exchange decisions.

This tool, combined with the use of the time-lock structure, will make it tremendously costly and time consuming to manipulate XHV’s price or the xUSD exchange process. As Haven approaches the mainnet launch of xUSD, we will continue to discuss the structure of these modest limitations in order to balance user experience with protection of the Haven network.

Deployment of Decentralized Pricing Oracle

The purpose of Haven’s pricing oracle will be to create a real-time pricing record containing exchange rates (against XHV) for xUSD at the time each block is mined. During the public xUSD testnet, pricing information is updated every 30 seconds via the Haven oracle and presented to the Haven daemon upon request.

These pricing records are then embedded into the Haven blockchain in every block header. By including this information in every block, the protocol guarantees transaction values cannot be tampered with or altered in any way. Haven’s pricing information will be immutable.

Haven has partnered with Zel to utilize their decentralized nodes as a pricing oracle. However, due to time and resource constraints, we are still evaluating the feasibility of using the Zel network for mainnet launch of xUSD.

It should be noted that Haven’s pricing oracle will not be fully decentralized at mainnet launch. The oracle will be hosted initially either by Zel or the Haven team. It is the priority of the entire Haven community to deploy multiple layers of pricing oracles after mainnet launch in order to achieve complete decentralization of the Haven network. This will also require Haven to be listed on additional exchanges to allow the oracle(s) to process additional pricing data points.

In the future, we plan to never rely solely on one oracle system, but rather allow the network to add, swap, and remove decentralized oracle systems (such as Blocknet).

Web-Based Haven Vault Update

The web-based Haven Vault does not yet have xUSD functionality. After development of the desktop Haven Vault is completed (with full xUSD exchange functionality), the Haven team will work to further build out the web-based Haven Vault. This will likely happen after the mainnet launch of xUSD due to the team’s time and resource constraints. There are several important technical reasons we chose this path.

First, the web-based Haven Vault currently used on mainnet (which is also optimized for mobile platforms) was developed using OpenMonero. Previous versions of Haven’s desktop and command line interface (CLI) wallets did not use OpenMonero, but instead relied directly on the use of remote procedure calls (RPCs).

RPCs function in the same way as application programming interfaces (APIs). They provide a user interface wrapper with access to existing functionality in a codebase. In Haven’s case, RPC calls allow remote access for the xUSD exchange functions already written in the core codebase, which was previously only usable by the old CLI wallets.

With this in mind, the work required to create a desktop Haven Vault using RPC was significantly less than the work required to recreate the Haven code (which actually generates and calculates xUSD exchange transactions) for the web-based Haven Vault. Even while the web-based Haven Vault is being updated to include xUSD, it will remain available on mainnet for storing and sending XHV.

Supply Transparency Solution

After the mainnet launch of xUSD, the circulating supply of XHV will fluctuate dynamically based on burning of XHV for xUSD, and the minting of XHV when burning xUSD. In some market cycles, XHV supply will be reduced. In others, supply will increase.

It is important to note that with activation of xUSD on Haven’s mainnet, there will be zero xUSD in existence. That means the initial XHV supply change will be deflationary by design. The Haven whitepaper models several of these supply scenarios in detail.

The Haven community expressed a desire to enable visibility of all XHV and xUSD circulating supply numbers while retaining full privacy for user transactions, balances, and addresses. There are several benefits to enabling supply transparency, including:

· Allowing more efficient monitoring of the Haven network, which means attempted attacks and large-scale manipulation can be detected and mitigated much faster.

· Giving users greater confidence to enter the Haven network with the ability to view the number of XHV and xUSD in circulation at any given moment.

· Allowing for greater visibility, and therefore more precise analysis, on coin metrics websites.

We have identified a solution to implement supply transparency in the codebase. This solution is currently being refined and tested by the team. It will be released publicly before the mainnet launch of xUSD.

Public Code Release

Most of Haven’s development’s work — both on the protocol and related software — has been conducted publicly on our Github. However, several key pieces of Haven’s codebase related to the xUSD exchange process have been intentionally kept private.

Throughout the development process, the Haven team has sought and received advice from experts in the cryptographic community to vet these portions of the codebase and make them as secure and reliable as possible. The entire codebase, including the pieces related to xUSD exchanges, will be released publicly in advance of mainnet launch. This will ensure all pools and exchanges have time to prepare for the hard fork that will be required for Haven to launch xUSD on its mainnet.

New Exchange Listings

Haven was added to two new exchanges and a fiat on-ramp over the last two months:

In November, Haven was selected for listing on the Abra investment app, alongside DAI and USDT. It is exciting to see growing interest in the first private stablecoin. This listing provides a fiat on-ramp and direct access to XHV withdrawals and deposits anywhere in the world.

In December, Haven was listed on VCC Exchange. This new Singapore-based exchange shares its liquidity and security infrastructure with Bittrex and gives users in Vietnam trading pairs in VND.

Also in December, Haven was added to Citex. Based in South Korea, Citex will offer expanded access to Haven in Asia.

These listings are a credit to the hard work of our volunteer team and active community.

Additional Whitepaper Translations

We have added several new translations of the Haven Whitepaper. Spanish, Vietnamese, and an updated Chinese translation are now live on our website. Many thanks to the community members who helped with this effort. Please continue to reach out to the Haven team on Discord if you are able to assist with additional translations as we continue to grow awareness of the project.

Mainnet Launch Date

Given all the ongoing development work described above, the mainnet launch of xUSD is still on target for late January or early February 2020.

As the final public testnet progresses and development of the xUSD exchange codebase is completed, the Haven team will announce an official mainnet launch date.

This announcement will provide ample time for pools and exchanges to prepare for the hard fork that will be necessary to launch xUSD on Haven’s mainnet.

In Closing

We are thrilled with the progress that has been made to this point. Haven has always been a unique, innovative, and ambitious concept. None of this progress would have been possible without the active support of Haven’s largely volunteer team and community, which has provided support for code development, technical implementation, graphic design, economic modeling, and marketing over the last year.

Come join the conversation on Twitter, Discord, Reddit, and Telegram and see what Haven can do for your financial privacy and freedom.

stat?event=post.clientViewed&referrerSource=full_rss&postId=c50e3b556649

View the full article

Snider

Haven November 2019 Update

Haven November 2019 Update

1*avBJJQzMbEpPyAVxjjxgfg.pngLogin screen for the new Haven Vault

As Haven approaches its first major project milestone — launching the first private stablecoin (xUSD) on mainnet — we want to keep everyone updated regularly on the team’s progress.

The public offshore testnet is progressing well. Stage 2 is now ongoing with thousands of offshore (XHV to xUSD) and onshore (xUSD to XHV) transactions completed. The testnet now has more than 20,000 blocks mined and is open to anyone wishing to participate using a CLI wallet. Follow this guide to participate.

Over the last few weeks, several additional features have been added to the public offshore testnet including:

  • Offshore XHV to xUSD directly to 3rd party addresses
  • Transfer xUSD directly to 3rd party addresses
  • Updated variable Monero-based time locks for offshore transactions: xUSD transaction fees will increase based on the time selected (number of blocks) for unlocking each transaction

Each of these new features has been tested extensively by the Haven community. We have received invaluable feedback which has helped our developers in bug hunting and improving Haven’s system performance. Keep it coming!

November also marked the launch of our new website. It now includes complete updated documentation to learn more about Haven, an updated FAQ, and translations of Haven’s whitepaper in three languages.

We are also very excited that Haven’s new web wallet — Haven Vault — has launched on mainnet and is now available for anyone to use. Here is a short video of the Haven Vault in action. The Vault is built from the ground up using React and is designed specifically to allow all offshoring and decentralized finance functions to be integrated seamlessly in the future. The Vault’s architecture ensures the security of your seed or keys, as they are never submitted to a server or sent across the internet.

As the project progresses and more features are added, the codebase for Haven Vault will serve as the hub for the entire Haven network. It will allow our team to build native desktop and mobile wallets while keeping the same framework in place. To that end, work is almost complete on the first desktop wallets that will incorporate all offshore functions for additional testing before mainnet launch. More information will be announced on this topic very soon.

Haven’s community-led team continues to make critical progress toward our most important goal: releasing offshore functions and the world’s first private stablecoin (xUSD) to Haven’s mainnet. We have found that arbitrary deadlines for these goals do not help the team or our community. Our goal is to always deliver updates the right way based on successful realization of the tech to bring safe and useful tools to the public. That being said, given the significant progress made over the last two months, we are confident offshore functions and xUSD will be ready for use on Haven’s mainnet in January 2020.

The team is now also beginning to plan for Haven’s future goals, including Ledger integration, the addition of other private stable coins (xEUR and xBTC for example), and the creation of decentralized finance applications for xUSD (such as Haven Loans).

Finally, we were pleased this month to see Haven selected for listing on the Abra investment app, alongside other stablecoins such as DAI and Tether. It is exciting to see the growing interest in a private stablecoin option. We look forward to Haven being available for purchase by Abra users in the near future. The team continues to communicate with other exchanges to discuss Haven’s future listing options.

Haven has also become more active on social media platforms including Twitter, Discord, Reddit, and Bitcointalk. Come and join the conversation and see what you and Haven can do for financial freedom.

The need for fully private and decentralized ways to store and transact your money has never been more clear. Haven will be an essential tool for those who want to control their own money, in private, independent ways, without third parties like banks, exchanges, corporations, and oppressive regimes.

stat?event=post.clientViewed&referrerSource=full_rss&postId=b46cee796e01

View the full article

Snider

Haven Offshore Update — October 2019

It’s been nine months since the Haven community took over the project’s development. After many long discussions, late nights, and extensive community contributions, Haven has reached the first major project milestone.

We are pleased to announce the Haven offshore testnet has now been launched for public access. This will be rolled out in several stages in order to carefully manage offshore testing and subsequent development:

Stage 1 — Closed offshore testnet (COMPLETE)

The first closed offshore testnet was conducted by Haven team members and long term community project supporters. This allowed for initial testing and bug fixing under controlled conditions before opening up to a wider audience.

Stage 2 — Public offshore testnet (ACTIVE)

The testnet’s key functions — offshore and onshore transactions of xUSD — are now open for anyone to try. This phase is being carried out using only the Command Line Interface (CLI) wallet, which allows for faster responses to any further bugs found using just a single platform. Please read the following guide to participate in the offshore testnet, and stop by the Haven Discord to ask questions.

1*eWksOv8MG2FTyBFo15csmA.jpeg

Stage 3 — Integrated wallet testnet (IN DEVELOPMENT)

While Stage 2 is ongoing, team members are continuing to integrate the offshore code into the backend of the new Haven web wallet. This work is almost complete. Once finished, this will open up the offshore testnet to a much wider audience with a simple-to-use wallet and UI. In the future, this web wallet will be the primary hub for the entire Haven network.

There are several important pieces of protocol architecture that will be used during the offshore testnet in order for Haven to launch with a robust and secure network:

Moving averages

Moving averages are being used to determine price quotes and offshore transaction fee levels in order to balance efficiency and protection of the network. These will be tested and calibrated during the course of the Offshore Testnet leading to an optimal moving average prior to mainnet.

Time-lock decay function

Additionally, Haven uses a unique time-lock decay function in conjunction with moving averages to determine fees and unlock times for transactions within the Haven vault. The use of a time-lock decay function is designed to measure and reduce the incentive for bad actors while offering optimal conversion times for users.

Circulating supply transparency

The Haven community expressed a desire earlier this year to enable visibility of all XHV and xUSD circulating supply numbers while retaining full privacy for user balances and addresses. There are several benefits to enabling supply transparency, including:

· Allowing more efficient monitoring of the Haven network, which means attempted attacks and large-scale manipulation can be detected and mitigated much faster.

· Giving users greater confidence to enter the Haven network with the ability to view the number of XHV and xAssets in circulation at any given moment.

· Allowing for greater visibility, and therefore more precise analysis, on coin metrics websites.

Decentralized pricing oracle

Testing and integration of the Haven pricing oracle will take place during the offshore testnet. After mainnet launch, Haven plans to utilize ZEL Protocol nodes in order to ensure the integrity of price-data.

Hardware wallet support

Hardware wallets will be supported for use with the Haven web wallet to give users additional options for storage. The first release will be for Haven’s base currency (XHV) with plans to add other xAssets at a later date.

Further technical details of the issues discussed above can be found in Haven’s updated white paper.

As the project has progressed, Haven now benefits from the help of numerous long-term community members who have volunteered to assist with everything from analyzing Haven’s economics, translating the white paper and other documents, and marketing.

Everyone is encouraged to get involved by making a positive contribution — without the Haven community there is no Haven! Join the community conversation on Discord, Twitter, Reddit, Bitcointalk, and Telegram.

Together we look forward to delivering the world’s first private, decentralized finance network.

stat?event=post.clientViewed&referrerSource=full_rss&postId=49057d6329de

View the full article

Snider

The Haven team is proud to announce we have been selected by Zel Technologies to be added to the ZelCore ecosystem. We are excited to partner with an innovative cryptocurrency project which also emphasizes privacy and security for its users.

What does this mean for Haven? A lot! Most importantly, this partnership means Haven will be added to the ZelCore multi-asset wallet. This advanced wallet will allow Haven users to access, store, transfer, and even trade XHV within a secure wallet. ZelCore is available for macOS, iOS, Windows, Android, and Linux users.

0*ZbN59V7bdr_ldj9ZHome screen in the ZelCore multi-asset wallet

The ZelCore wallet allows users to have multiple encrypted wallets and accounts on the same device and access the same account on multiple devices, all while maintaining complete privacy. ZelCore does not store or transmit any personal user data. ZelCore supports over 100 additional cryptocurrencies as a complete store and asset management system.

With the premium service ZelCore+, Haven users can trade XHV with their custodial wallets directly in ZelCore via API linking, utilizing full TradingView features. Users will then have the option for 1-click withdrawal to their ZelCore Haven address.

0*oUPMYT1G2TYRQVRhAdvanced trading features available to ZelCore+ users

The ZelCore team is also developing a fully decentralized exchange. Haven’s addition to the ZelCore ecosystem will allow XHV to be traded on this platform in the future.

As a new ZelCore asset, Haven will also be able to take advantage of the recently-launched ZelLabs project. ZelLabs provides the projects included in ZelCore with additional technical expertise, business development and education, and co-marketing opportunities.

0*7fA7LRWEa3CC3JWX

Finally, the Haven team will be able to utilize ZelNodes, which is a 3-tier decentralized network of incentivized compute power. Fully scalable, ZelNodes processes sidechains to create a high-TPS mesh to run DApps and smart contracts. For Haven, ZelNodes could provide additional resources for the Haven network, such as pricing Oracles which will be used for offshoring functions.

The Haven and ZelCore teams are finalizing integration work and plan to launch Haven live on ZelCore later this month. We look forward to partnering with Zel’s strong group of developers to ensure the continued growth of both ZelCore and Haven.

stat?event=post.clientViewed&referrerSource=full_rss&postId=ab3bb530153f

View the full article

Snider

Haven Protocol — April 2019 Update

Since January, the Haven Protocol project has undergone many organizational changes. We have grown considerably and are excited to share our progress with the community. Moving forward, we will post regular updates covering any changes and progress in the following three areas:

  • Team Structure and Roles
  • Development and Design Progress
  • State of Governance Funds

Team Structure and Roles

Leadership Team

@News.Cutter — Leads growth, marketing and strategy. News.cutter has been closely involved in marketing and growth strategies for Haven since autumn 2018.

  • Digital Startup Generalist with broad experience
  • Growth / Funnel Optimization
  • Social Media
  • Digital Marketing
  • User-Driven Product
  • Design Behavioral Design
  • User Experience Design
  • User Interface Design

@NBourbaki — Leads our development effort, bringing his vast and rock solid experience along with a methodical approach to delivery.

  • 35 years of software development and leadership roles
  • 10 years Consultant software engineer for top 10 consultancy
  • 10 years Senior Manager in top 5 consultancy
  • 7 years VP of software development for major SAS provider
  • 5 years Principal Private Equity
  • 3 years VP of technology for international SAS provider
  • Agile and Kanban development methodologies
  • C, C++, Assembler (370, x86, AVR)
  • BS Mathematics/Computer Science

@Dweab — Leads on governance and operations. After spending the past 10 years building and leading technology delivery teams, @dweab joined the Haven team after volunteering to publish the iOS app, and slowly got more and more involved.

  • 20+ years of commercial Software development and leadership roles
  • 10+ years VP and C-level roles
  • 2 major tech startups
  • 2 x winner of UK Government Innovation award
  • Ex VP/Director tech/Innovation of UK PLC
  • Product & Commercial focus, Tech background
  • Agile/Kanban/FDD development methodologies
  • Fortran, C, C++, Assembler (X86), PHP, Javascript….+ Others
  • BSc (Honors) Mathematics

Development Team

@Radvd — Open source software engineer. 10+ years of industry experience using C/C++/Python. https://github.com/radvd

@Juan Two — Experienced Front End crypto developer. Juan Two is a long time contributor to Haven and will be leading the UX/UI side of development and bringing the UX visions of the team to reality.

Operations, Communications and Support Team

@rarecommons — Strategic innovation, technical communication, economics, engineering, MSc. Helping out with: economic systems and marketing.

@Madlentil — Serial entrepreneur. Interest in the bigger picture for where we can take Haven over the next few years. Helping out with documentation, technical writing and ideas/feedback.

@luge — UX and Design/ Product specialist. Luge will bring several layers of help to the team and will assist Dweab in managing operations in general.

@Nickm4 — Medium and Twitter communications, marketing and Windows support.

@AHawk — Medium and Twitter communications, Discord support and community moderator.

Community Managers

@Le_Hibou_Crypto$ Official Telegram moderator.

@jriggs28 — Discord community moderator.

@TheCrazyMiner — Discord community moderator.

Consultants

@Paladin [Imperdin] (https://github.com/imperdin ) — A well known figure in mining and cryptographic circles. Imperdin kindly donates his time to consult, improve, validate and challenge the design of our offshore solution. This kind of input from someone known as a cryptographic and blockchain expert in the ‘real world’ is highly valuable to the team, and has increased progress in creating a solid, secure solution.

Team Changes

@radvd https://github.com/radvd — Rad has joined the Haven team recently and now leads our core blockchain development, allowing nbourbaki to focus purely on offshore. Rad brings great strength of experience and we’re delighted to welcome him to the team.

@Havendev and @Donjor — Both Havendev and Donjor willingly transitioned Haven Protocol’s code and assets to Dweab and members of the new team in January 2019. While communications with Havendev and Donjor are still open, both are no longer involved in development. All major communications and updates will be relayed through members of the new team or Haven Protocol’s Medium and Twitter accounts.

Development Progress

Completed Upgrades

Haven Protocol v3.2.2 — The development team scheduled a hard fork for block 290,587. This hard fork implemented the new team’s multi-signature governance wallet and patched a critical Monero vulnerability. Additionally with the rollout of v3.2.2, the Haven Protocol team has launched new seed nodes, created new block explorers and taken over communications with exchanges. These measures ensure the continuity of the new team’s efforts and cut all reliance on the previous development team. The release for v3.2.2 can be found here:

https://github.com/haven-protocol-org/haven-legacy/releases/tag/3.2.2

Rebase Updates

Haven Protocol is being rebased on Monero v14.0.2. This means that the Haven codebase will now include all of Monero’s recent updates, bug fixes and most importantly, bulletproofs.

Testnet — The testnet for the Haven rebase is scheduled to begin on April 15th. The rebase testnet will allow for ample testing and feedback before the launch to mainnet.

Mainnet — The mainnet rebase requires a hard fork to implement these upgrades. The hard fork is scheduled for block 318,921, or May 2nd.

All community members are encouraged to participate in the testnet, review the rebase and post feedback in the #rebase-feedback Discord channel. The rebase code can be found here:

https://github.com/haven-protocol-org/haven/releases/tag/4.0.0-rc2

We will be releasing another announcement prior to May 2nd with instructions for the community to prepare for the hard fork.

Offshore Updates

Since January, the new development team has been assessing the code received from the previous developers and has been making strides to reach our next round of Offshore testnet.

Our main focus has been the development of the new Oracle. In short, the Oracle is the arbiter of price. The Oracle provides the Haven Protocol blockchain with pricing data that is pulled from exchanges. This data is then normalized, averaged by volume weight, cryptographically signed and broadcast to miners for inclusion in new blocks. The signature allows for validation from the source to the blockchain.

The team is confident we can deliver a working Offshore feature and has provided the following updates regarding development of the new Oracle.

Completed:

  • Completed the high-level cryptographic design.
  • Completed prototyping of data pulls and public key signatures.
  • Completed network messaging, including message formats and cryptographic signatures.
  • Expanded database schema. Now includes raw data that allows for data validation and monitoring stats to help gauge stability and reliability of data sources.
  • Completed OracleMon to simplify monitoring of OracleSrc.

In Progress:

  • OracleSrc is in stability testing. Testing includes expanded logging, instrumentation, additional logic for data source availability and multiple recovery modes.
0*5LrlhFzXLVRU_2B3

OracleSrc — pulls pricing information from exchanges and forex, creates a weighted average price, stores both the computed information and raw data to MySql, constructs a pricing record, signs that record and broadcasts the signed record to all OracleRouters.

  • OracleSrc outputs are being recorded in MySQL and discrete log files to allow analysis by the team.
0*6_zzqjKe45mfuVmT

MySql pricing record

0*q3_oCwmfnJpd8-3U

MySql raw table

0*ueKqkiRICcJTixyL

MySql stats

  • OracleSrc data output is being reviewed by the team on a daily basis.
  • OracleNode is in stability testing. Testing includes irregular operations and fault injection testing. OracleNode has achieved 4 weeks of availability with no unrecoverable errors.
0*41veRcpV4uX744B8

OracleNode — receives network director list of active routers, determines the closest router by geolocation and connects to that router to receive pricing records.OracleNodes validate all pricing records via public key.

  • Integration of OracleNode with Network Director and OracleRouter is in progress.
  • Geolocation tagging of OracleRouters is in progress. This will allow OracleNodes to determine the best router connections and recovery modes if a connected router goes offline.
0*j5t3RH3-xO6s3A9H

OracleRouter — receives OracleSrc pricing records and distributes to all OracleNodes that are connected

0*cahbpBwKkzC5jnwc

OracleMon — monitors Oracle functions and provides summary of uptime and errors.

Next Steps:

  • Finalization of the OracleRouter network, discovery logic and stability testing.
  • Completion of Network Director and stability testing.
  • Integration with the blockchain, miner, wallets, sub-addresses and finalization of consensus rules. Integration will be based on the rebased Haven code.
  • Review current sub-address scheme used in original offshore testnet.
  • Create the offshore modifications for miners.
  • Internal testnet of offshore.

Design Progress

Branding Overhaul

With a new team and new products comes a new, refreshed brand. The wordmark and logo will have a slight refresh and a new design framework for marketing and communications.

Web Wallet

The team is creating an easy-to-use web wallet for the Haven community. This wallet will allow all users with a web browser to access their Haven wallets. Users will be able to check their XHV balances, send/receive XHV and offshore funds once the offshore feature is released.

Website

The Haven Protocol website and block explorer will also undergo a refresh to improve user experience and fully represent the direction of the new team.

Mobile Wallets

Native iOS and Android application design will enable users to use Haven in the real world and on the go. Users who are currently awaiting the updated mobile wallets and need to transfer funds are able to restore their wallets using the Desktop GUI or CLI wallets.

State of Governance Funds

The governance fee will remain at 5%. All governance funds are now being deposited into a team owned multisig wallet. Our goal is to be 100% transparent as to where these funds are spent. We plan to use governance funds for development, marketing, exchange listings and legal fees. We are always open to the ideas of the community so please talk through any opportunities to further Haven Protocol with us in Discord or on Twitter.

Governance Fee Details:

Haven Protocol Project Balance

+ 714.24 XHV — Daily incoming governance fee

- 7,000 XHV — March/April development cost

- — — — — — — — — — — — — -

+ 28,605.75 XHV — Project Balance April 2019

New Team Multi-Signature Governance Wallet : hvxy3f2PhAhimkeLf617BsbVn6UTbofVcMzofXGsSNLoMFr2SrSxRJ9f52Am1QLVddKet XPKHoTLbBaLNT1kMU6Q3kYRc3t6pF

Wallet viewkey:

b8679ce8084f489cc070537941f683ecfaac65321c2e6e73891d7ae10bc3e102

Conclusion

Haven Protocol is here to stay. Team members may come and go but our vision stays the same. Our team is here because we all believe in making the Haven Protocol Offshore a reality. We are excited about the progress we have made and look forward to sharing this project with the community.

stat?event=post.clientViewed&referrerSource=full_rss&postId=ca2e911176c8

View the full article

Snider

Update from the Haven Protocol [XHV] Development team — Jan 2019

As many of you have noticed, the Haven Protocol team has expanded over recent days. The following update is written by Dweab.

Further updates with more details about the new members’ roles will be released soon. The new team was formed around the shared desire for transparency and to realize the goals of the algorithmic stablecoin in development. Yesterday, the existing assets/code were released to the new team for review and onboarding/walk-throughs were started between @havendev, @donjor, @dweab and @nbourbaki.

These will continue today and we will be looking methodically at the current codebase to ensure that next steps and future plans align with the code we now have in hand. Over the past few days a side stream has been running to create our new team GitHub repository, take the latest version of Monero and rebase Haven onto it. This is meant to ensure quick merging of upstream security patches in the future, and includes the addition of bulletproofs. As you would expect, now that we’ve had a quick look through and a high level overview of how it all works, we have a much better understanding of where effort will need to be focused. To keep everyone informed the high level view is that:

  • Yes, the offshoring code exists
  • Yes, the testnet worked in its intended form and was a valuable prototype of the system
  • No, it wasn’t ready for release to mainnet and more testnets and development effort were required
  • No, recent security updates and bulletproofs were not integrated, and transfer into a new codebase is needed for future development(edited)

Since testnet was run, and particularly in recent weeks other projects have started the process of creating their versions of the Haven idea. We applaud this, and appreciate each one for the alternative paths their implementations are taking. This is a huge compliment to the overall concept, and also an indication of the desire for the functionality. This also has had several of us working through a complete end to end consensus mechanism even before receiving the code — particularly around the oracle. This thinking is being explored in detail and our improved model will be discussed with the community to gain input, validation and support for the model. In further accordance with our mission, and with the goal of transparency and communication, the new Haven Protocol developers are eager to share the initial findings and next steps to be taken now that they have received the XHV source code:

1*3XSPFlI56rMZlcAWBvSsqA.pngHigh level review of original testnet

Next steps — Gap analysis to product vision, rebase, bulletproofs and security To move from where we are to full release, as a new and greatly expanded team, we will be working with @havendev and @donjor over the coming days to do a full gap analysis and create an updated roadmap which will be released as soon as possible.
Goal: Development of a high-level plan and estimate for completion. This includes updates to testnet, test plan, and mainnet launch

What will need to be fixed?

Instead of fixing an incomplete solution. We believe the best course of action is to rewrite the Oracle

What will need to be added?

  • Oracle P2P network and protocol Hashing for confirmation of pricing information
  • More detailed pricing data committed to the blockchain
  • Expanded RPC interface for the Oracle

Main question: How far off are we to a complete solution?

We have an end-to-end solution for a new version of the oracle which needs to be coded and tested, reusing as much of the codebase as possible. We are in the process of determining the skills available on the development team and the work that needs to be completed. We may need to reach out for more help if the team doesn’t have all the skills or knowledge necessary to complete this solution.

Slightly off topic for a dev update, but important to note:
To make funding of the project visible to the community and secure successful development of the project, all available project funds and future governance fees will be transferred to a multi-sig wallet with regular public viewpoints and reporting on the use of funds. The keys will be held by a combination of public and anonymous team members ensuring that at least one public and one unknown member is needed for every withdrawal.

This mechanism should ensure that no unknown person or persons are in full control of funds at any time, and that any known person is not able to be forced to provide access since an unknown person is required as well. To build a transparent community, the most recent development updates can be found in the Discord channel #dev-updates (Join here: https://discord.gg/s5kqbVA) to keep the Haven Protocol community informed about the progress. To achieve an accelerated product launch it’s planned to only include one stable fiat currency, XUSD, in our mainnet release for now. The newly assembled development team is excited to continue working on this revolutionary idea and is eager to use the world’s first decentralized algorithmic stable coin!

stat?event=post.clientViewed&referrerSource=full_rss&postId=e1619b205834

View the full article

Snider

We have decided to rework our roadmap, Pushing back Offshore Storage Mainnet release to Q1 2019.

Updated Roadmap:

1*UL2Wd5ZZYWO6ks_s24MxtA.png

Explanation:

Security

Despite the fact that we are excited to bring Offshore Storage into the world; we aren’t going to release a version we are not happy with. At this stage, we have a lot more security testing that we want to be able to carry out. Ideally with source code released to the public.

We have a lot of people trying to take advantage of Haven’s success and also target us for their own enjoyment/benefit. We are looking for outside developers with experience to provide a fresh perspective to help us with testing and ideally improvements with the Offshore Storage code. Finding developers we can trust is a priority for us, although difficult.

XUSD + Exchanges

We are wanting to extend the platforms that Haven for decentralization of data for the price oracle. We also are working through the application process for the addition of our XUSD Stable coin to exchanges which would be ideal to have available at mainnet launch.

Added Roadmap Items:

Before the release of Offshore Storage we want to have incorporated Bulletproofs/Hardware wallet support. Completing this major upgrade to our network is now our focus for the rest of Q4. In addition, because of some active hostilities towards us and our network a Code Review was added to the Roadmap. A crucial addition but very difficult to execute.

Mining Centralization

We have designed the Offshore Storage price oracle to not be influenced by the wider network and thus will reject any attempted blocks with an incorrect price. However, we need to be as vigilant as possible as mining centralization on our network is a point weakness and with Offshore Storage release the potential gains of a network breach could be extremely high and would completely devastate our network.

Miner.Rocks is a solid pool, and the person who runs it has proven to be trustworthy. But they have had 50–90% of the network hash for we don’t know who they are, and their pool may well be hacked.

We don’t want to release our mainnet with the mining centralization issue prevalent. We will consider extreme measures to penalize miners using the centralized pool and incentivize switching.

Please switch your rigs to any of the following:

stat?event=post.clientViewed&referrerSource=full_rss&postId=bbcbd3f1d8ce

View the full article

Snider

Today is the day! Public Testnet release download link and information to follow.

1*S64ZWMy1x5b9ldqKHNFNFg.png

If you participated in any other tests:

Make sure you remove any old test blockchain and wallet files to avoid any local conflicts:

e.g: C:\ProgramData\haventest

and: C:\Users\{username}\Documents\havenoffshore

Download Link:

https://drive.google.com/file/d/1l0nVFpLAGUd0TA5lyoFM-1nT2XztmVDC/view?usp=sharing

Explorer: http://167.99.93.242/

Key features to test:

  • Send XHV
  • Receive XHV
  • Send XUSD
  • Receive XUSD
  • Offshore XHV -> XUSD
  • Onshore XUSD -> XHV
  • Send Offshore XHV -> XUSD (to another address)
  • Send Onshore XUSD -> XHV (to another address)

Mining/Receiving Test funds.

Request test funds from the discord channel #publictestnet or post your hvxtest address in a suitable thread.

You cannot send funds from the live network — this is a completely incompatable network specific for the test.

Solo Mining: Alternatively solo mine using cpu power to get your funds to play with and distribute to others. You must run a Haven Oracle to mine. As usual type: start_mining [address] to start mining.

Bugs & Feedback.

Report bugs in the #publictestnetbugreport channel on Discord.

We have lots of UI plans already this test it to primarily test the Haven Protocol core, not UI. However if you do have a suggestion feel free to leave it in the #publictestnetfeedback channel on Discord.

We are working on implementing UI changes/Multi-currencies such as the design concepts we have shown.

XGOLD is by far the most popular stablecoin request by the @HavenProtocol community. It will be added to the network in Q1 2019.

 — @HavenProtocol

Sneak peak #2 into the future of @HavenProtocol: What feature do you want added to the 2019 roadmap?

 — @HavenProtocol

stat?event=post.clientViewed&referrerSource=full_rss&postId=22f7f56c411

View the full article

Snider

Important announcement for the future of Offshore Storage!

Offshore Storage will be available based in other Currencies:

We have teased and previewed this in tweets of our vision for the future mobile app redesign:

Sneak peak #2 into the future of @HavenProtocol: What feature do you want added to the 2019 roadmap?

 — @HavenProtocol

Concept

The concept for multi-currencies has been in place from very early on in development. Although storage of funds is a major component to Offshore Storage, the use case as a day to day payment platform is very clear. Using Offshore Storage, any user can effectively create cryptographically untraceable fiat to store and transfer worldwide.

In order for Haven Protocol to rival all traditional stable options for a storage or payment platform i.e. onshore and offshore Banks, PayPal, Visa etc on a worldwide scale, support for multiple currencies is imperative.

Release time

At this time we are planning to initially release Offshore Storage with Haven Dollars exclusively. The Multi-currencies implementation will be a future hard fork.

Ticker Change

0*melNw3smPFR0ZX_i.png

The reason for the change is to provide clarity and consistency for all future offshore currencies. Any existing currency ticker can be used simply with adding an ‘X’.

When considering how to identify offshore USD from CAD, AUD, NZD we would have inconsistent formats with our previous ticker format. (XHVD vs XHVCAD) All issues are solved with the addition of a leading ‘X’.

Although from a technical perspective this change isn’t an issue, maintaining consistency from a marketing and discussion perspective is important to avoid confusion.

All other documentation referencing XHVD will be updated to reflect the new XUSD format.

What Currencies are we going to support?

So far we have previewed the following:

1*6DDv0mTJ0gmCgqmooow3gQ.png

More currencies will be announced in the future! If adding a new currency helps bring more users to the Haven Protocol platform, we will work to do so.

This is very exciting from a cryptocurrency adoption perspective for merchants. They will be able to accept Offshore Storage funds and store funds in their respective countries currency. Price stability and privacy are the only hurdles to crypto adoption — and Haven solves both.

stat?event=post.clientViewed&referrerSource=full_rss&postId=3e3f295932f2

View the full article

Snider
1*mXPPmQTs0YIz0qwmoxcvdQ.png

Round 2 of private testing has gone swiftly — Time for the Haven Protocol Public Testnet

Initially our aim was October for the Public Testnet. However the most significant piece of feedback the team have given us is to ensure that a decentralized oracle is to be included in the Public Test. In previous tests we were just focusing on the offshore storage specific code.

The main reason for this is to avoid the perception that the mainnet oracle will function the same way. As the decentralized oracle wasn’t ready, we have had to work on it which wasn’t the initial plan for this test.

We don’t want to have to make everyone wait more than we need to and are going to push out the estimated release time to mid November.

Haven Decentralized Oracle:

What is the Haven Oracle?

For those who don’t know, an oracle is how a blockchain interacts with the wider internet i.e. an API. The Haven Oracle is what is used to determine the current price of Haven so we know the USD value of any Offshore (XHV -> XUSD) and Onshore (XUSD -> XHV) transaction.

Design

Who runs nodes?

Anyone can run their daemon as a validator and run the open source oracle code locally. As new blocks are detected, your daemon references the reported price in the new block and compares it to the prices you have determined independently.

Everyone is encouraged to run a remote node but all exchanges, pools, remote nodes and seed nodes will be required to run an oracle node.

Oracle nodes can be run independently from the Haven daemon. Anyone not running a validator node will accept the chain with the most work as usual.

How is the price determined?

The price is determined based on a weighted average and will be calculated over all exchange values, primarily based on volume, and normalized over previous 20 previous prices. Each oracle reaches out to the exchange APIs and gets the recent market history.

This will disincentivize someone attempting to manipulate mint and burn for profit through pushing up the price/dumping the price. To have any significant impact they would need to maintain the value over all exchanges for over 20 blocks (40 minutes). The cost of doing this would far out weigh any rewards.

FAQ: What would would happen in a 51% attack situation? Couldn’t they force everyone to accept a tampered price?

No. If the price in the block doesn’t match what is expected by your oracle, even if it is the longest chain with the most work, it will be rejected.

Your oracles reported price isn’t determined based on what the majority of oracles report; they don’t reference each other in any way.

There seems to be some misconceptions around how a 51% attack works. You can’t rewrite any consensus rules — otherwise all 51% attacks would involve minting billions of coins. A 51% attack can only force a roll back if their chain is the longest with the most PoW. An attack would work like this: An attacker would start mining with over 50% of the nethash and not expose the chain to the wider network.

The attacker sends all their coins to an exchange. After the deposit has enough confirmations, they sell and withdraw the btc. Once the btc is in their wallet; they expose their chain to the wider network. As that chain has the most work, it will become the “correct” chain and all nodes will roll back and sync with it. On the hacked chain, the attacker never sent their coin the the exchange address and will still have the coins in their wallet. The exchange loses out in this scenario.

If someone was to input a fake prices, all other nodes would reject the transaction as this price wouldn’t match what their trusted oracle data reports. They would have created a chain split and all validator nodes will eventually stop attempting to sync with the incorrect chain and ban them.

Most significantly all exchanges will stay on the original chain and any transactions attempting to send hacked coins to the exchange will be doing so on a completely different chain and never reach them.

stat?event=post.clientViewed&referrerSource=full_rss&postId=8ff8718d7981

View the full article

Snider

Why Haven Protocol’s [XHV] Offshore Storage is the best crypto stable coin storage solution.

1*mXPPmQTs0YIz0qwmoxcvdQ.png

Offshore Storage allows users to preserve the value of their coins, without compromising on security, privacy, and decentralization unlike other stable coins. Offshore Storage allows for anyone to be able to effectively open a USD based bank account without a central bank and transact funds away from the prying eyes of government.

Offshore Storage: (Mint and Burn)

The underlying coin is decentralized and the collateral efficiency is at a maximum (burning $100 worth gives you $100 worth). It’s also secure in a crash as no matter the price, the method of minting and burning works without discrimination. Any issues with liquidity can be circumvented with a USD base trading pair too.

Offshore Storage functions exclusively with a Privacy coin. The ’mint and burn’ lets the money supply fluctuate freely. The velocity of money is cryptographically unfeasible to determine as the blockchain does not reveal the amount transferred nor the wallet addresses they are transferred to. This means the currency is unable to be valued based on total supply.

Offshore Storage Secure to crashes Decentralized Collateral-efficient #xhv #haven #havenprotocol

 — @HavenProtocol

Other Stablecoin types:

The problem with existing solutions is that they tend to fall into a few main problematic categories:

Fiat-collateralized — e.g. Tether.
The fundamental issue with this method is that it is centralized and requires a large amount of trust in the company that is holding the fiat. It is not a long term solution and is counter-intuitive to exactly what crypto is trying to solve.

Crypto-collateralized — Backing a stablecoin with Ethereum/another Crypto. It’s Decentralized but as the backing isn’t stable either, a big enough price drop could exceed the amount of collateral and force you to liquidate. Not immune to crashes

Non-collateralized — Functions like a central bank by controlling the money supply of coins in order to move the price towards $1. This is a step in the right direction but still falls short. If the current price is $1.50, more coins are created and sold into the market to lower the price. If the current price drops to $0.50, coins can’t simply be burned so the central entity has to buy up coins in the market until the price hits $1.

Attempts to circumvent this by selling contracts to users to temporarily fund shortfalls and pay them back once the price goes up… Overall not very decentralized and not immune to a major crash.

Haven Protocol uses Offshore Storage to produce the best Stablecoin from a security of value and decentralized perspective in addition to being completely private.

Common Questions regarding Offshore Storage:

What if XHV’s price drops; resulting in minting more XHV thus causing inflation and further lowing the price. Couldn’t this turn into a massive inflation spiral?

This is a common question, which is understandable. Specifically with this example — there are a few assumptions you’d have to make to infer an inflation spiral. In order to get XHVD in the first place, you’d have to burn XHV, thus lowering supply (deflation).

To a certain point this is balanced out by reminting XHV (inflation). Although, because of offshore storage, the value of the coin isn’t directly derived by the supply, as its unknowable. Also, if you consider the users utilizing Offshore Storage, for the purpose of safe storage, are they going to mint back coins when the price lowers? What would be their reasoning for doing so? Minting and burning will be happening all the time no matter the price and doesn’t have to have any interaction with XHV trading on Exchanges.

What if there isn’t enough liquidity to cover selling your minted coins at the determined valuation price — as selling would lower the price?

A XHVD/USD Base pair would totally solve this. Haven’s long term plan is to have XHVD/USD pairs on exchanges.

Even without, the solution is simple — Smart users wont mint and sell their XHV in a downward trend, users have a large disincentive to do so as they could get more in an upward trend. Users also don’t have to sell all of their Offshore Storage at once. They are free to mint back smaller amounts and sell them for the value they were minted at.

Long term, Haven Protocol’s vision is to have the usability of a standard online bank app or PayPal/Venmo with complete anonymity. With adoption, users won’t have the same requirement to mint back XHV from their XHVD as they can utilize and transfer XHVD just like USD.

Could someone manipulate the price of XHV in order to lower it to burn a lot of XHV coins for more XHVD — then pump up the price and mint back more XHV than they started with?

This would be an extremely expensive exercise. In order to profit, you would need a large amount of funds — to the point where the cost of manipulating Offshore Storage in this way is not significantly different to the cost of manipulating any market.

Fundamentally this sort of manipulation would work like this:

  • Purchase xXHV
  • Offshore bXHV -> mXHVD = bXHV *CurrentPrice
  • Sell sXHV (to lower the price to Original price/f — e.g.1/2 the current price and maintain for 20 blocks)
  • Onshore mXHVD -> oXHV = mXHVD /(CurrentPrice/f)
  • Buy pXHV (in order to raise the price — e.g. back to the Original Price and maintain for 20 blocks)

If p + o > x a profit is realized.

In order to determine if this is profitable, you have to determine or make a lot of assumptions and derive values for f, s and p.

x=b+s+p

You could make the assumption that it costs the same amount of XHV to lower the price as it does to raise it back up. Bear in mind that the cost of this is difficult to determine, as a manipulator would need to maintain the price at the low value for 20 blocks and at the high price again for 20 blocks — a total of 80 minutes over every exchange as the algorithm that determines the XHV/XHVD exchange rate used a weighted average.

The more you sell, the more it costs you, as you would be selling your XHV for up to 1/f of what it is worth.

x = b+2p
p+o > b+2p
o > b +p

We also have discussed this and other game theories at length in the discord channel. MyCryptoNinja has put together a trello board and has included some screenshots of discussions that have taken place: https://trello.com/c/fdCroy1g/4-game-theories

stat?event=post.clientViewed&referrerSource=full_rss&postId=61f118129784

View the full article

Snider
1*kwQFNzzrPRJTMvmxFy4LTA.jpeg

Round 1 of Testing has been completed!

Big thanks to our community testers for assisting us with testing and providing us with a lot of very useful feedback! Some testers were quick to show the wider community what we have been working so hard on:

Taking a test trip offshore. $XHV $XHVD @HavenProtocol

 — @notsofast

XHV Testnet Preview, good job guys, keep it up @HavenProtocol @donjordev @haven_dev $xhv https://t.co/jSMPik0B08

 — @vacs03

Our community was instructed to test the following functionallity:

  • Send XHV
  • Receive XHV
  • Send XHVD
  • Receive XHVD
  • Offshore XHV -> XHVD
  • Onshore XHVD -> XHV
  • Send Offshore XHV -> XHVD (to another address)
  • Send Onshore XHVD -> XHV (to another address)

Also, they gave feedback on the process itself. A very positive result, although can always be improved. Very exciting to be able to see the offshore storage process working.

We did discover some visual bugs during testing which we are working on fixing for testing round 2. We have been heavily working on the actual functions rather than the wallet.

Wallet Design

We are very fortunate to have JuanTwo in the Haven Community. He has been working extremely hard to put together new design for the Haven Protocol wallet:

Haven Protocol | Zeplin Scene

As Donjor and Havendev are both programmers first, having a designers eye is extremely important when creating UIs.

We have had more awesome responses from the community regarding the design which we are incorporating as much as we can into our future wallet.

Testnet Round 2:

We expect to start the 2nd round of testing this month. We are going to open up the testing to slightly more people. At this stage we need to be able to talk with everyone on a individual basis and slowly start to add more functionality.

We are going to have a public block explorer during the next testing phase so the entire community will be able to see the functioning chain at work.

What are we testing:

Similar to Round 1, we are wanting to test the basic sending, receiving and conversion functions and bug test the issues identified in the first round, notably:

  • Confusing fee and returned change values in transaction history.
  • Wallet transaction history visual bug (balances correct).
  • Delay when entering values in offshore fields.
  • No unmixable outputs to sweep error (due to new offshore transactions).

We also want to test out the block explorer and our UI changes. Once again, this will be a closed release with ~ 20 extra community members added.

Round 2 Release date:

Our aim for the release is September. Stay tuned for further updates from the Haven Protocol team!

Haven Protocol Community Alpha:

The Testnet for everyone!

After we are confident with the results of Round 2, we want to release a version for our wider community to interact with as soon as possible. This will be able to be downloaded by everyone!

Our aim for this release is October.

Testnet Future Goals/Tests

  • Simulated exchange prices.
  • Local node users daemon and gpu mining
  • Offshore Storage Game theory testing.
  • Local Haven Oracle node testing.

Glitch in the matrix?

An amusing TradeOrge glitch reported Haven’s price to be 7.6 BTC for a short time before being rectified.

I almost became a billionaire overnight $xhv

 — @PandaTaiwanese

iOS Update

We have an iOS version available, we just need to sort out publishing and closed testing with Apple. Unfortunately this is a bit difficult without being a registered company or exposing personal information. Working on a solution with our legal team!

stat?event=post.clientViewed&referrerSource=full_rss&postId=a7123b6e0e72

View the full article

Sign in to follow this  
  • HashVault Stats

    • Global Hashrate
      3.63 TH
    • Avg Hashrate
      2.50 GH
    • Total Miners
      1452
    • Miners Paid
      42034
    • Total Payments
      1502093
    • Total Hashes
      9.23 EX
    • Blocks Found
      1646259
×
×
  • Create New...