Iamtutut
|
|
October 10, 2019, 03:54:54 PM |
|
They don't control the old haven accounts, including here.
You have updates on twitter.
|
|
|
|
big_daddy
|
|
October 10, 2019, 05:46:10 PM |
|
They don't control the old haven accounts, including here.
You have updates on twitter.
Than will be good to open a new XHV official thread, controlled by the current team
|
If you don't believe it or don't get it, I don't have the time to try to convince you, sorry.
|
|
|
goshiz
Jr. Member
Offline
Activity: 34
Merit: 3
|
|
November 02, 2019, 03:29:46 PM |
|
Hey guys, the "new" team is going to recreate a topic with all the informations updated.
|
|
|
|
big_daddy
|
|
November 04, 2019, 09:06:18 AM |
|
Hey guys, the "new" team is going to recreate a topic with all the informations updated.
where you got that info?
|
If you don't believe it or don't get it, I don't have the time to try to convince you, sorry.
|
|
|
goshiz
Jr. Member
Offline
Activity: 34
Merit: 3
|
|
November 16, 2019, 09:11:58 AM |
|
Hey guys, the "new" team is going to recreate a topic with all the informations updated.
where you got that info? I asked the project leader on discord if he intend to post a new subject, he reply that he will try to do so, but I guess he did not have the time after all. The team already add offshore function to cli-wallet and rpc-wallet, now the add all functions on the desktop wallet (using RPC-Wallet) so they don't had the time yet to post a new topic. to prevent any misinterpretation, I help the Haven Team on DevOps operations, I appear as "developer" on their discord, but I'm not a blockchain developer, I'm not a developer at all and I'm not part of the core team.
|
|
|
|
big_daddy
|
|
November 16, 2019, 09:19:54 AM |
|
That sounds promising The team is doing well, the price and trading volume is gaining more and more lately
A quick one: do we have to use some new wallets or the versions from the OP are still operational?
|
If you don't believe it or don't get it, I don't have the time to try to convince you, sorry.
|
|
|
goshiz
Jr. Member
Offline
Activity: 34
Merit: 3
|
|
November 16, 2019, 10:17:58 AM Last edit: November 16, 2019, 03:05:46 PM by goshiz |
|
Like everything else, the old team did not turn-over the control of website, github account, twitter account, bitcointalk user, discord, telegram... Everything posted by OP must considered outdated, included old @HavenProtocol twitter, old website (havenprotocol dot com) and old github account (havenprotocol on github). Website : https://havenprotocol.org/Github : https://github.com/haven-protocol-orgTwitter : https://twitter.com/HavenXHVDiscord : https://discordapp.com/invite/CCtNxfGTelegram : https://web.telegram.org/#/im?p=s1273047334_13986713956461503950Medium : https://medium.com/@havencurrencyReddit : https://www.reddit.com/r/havenprotocol/Current desktop-wallets are available on the new website https://havenprotocol.org/ you also can use the brand new web-wallet by login with the button on top-right of the website. You have to enter your seed (the seed never leave your computer, only view-key are sent to parse the blockchain and show the balance).
|
|
|
|
pinpins
|
|
December 27, 2019, 11:36:55 AM |
|
You can mine Haven at autoexchange mining pool Zergpool.com at 0.5% fee. Please use following commands for different mining options Option 1 Auto coin switch by profitability within algorithm with autoexchange to specified coin wallet(BTC in example below) -a cn-heavy/xhv -o stratum+tcp://cryptonight_haven.mine.zergpool.com:4452 -u <YOURBTCWALLET> -p c=BTC Option 2 Direct coin mining with payout to coin wallet -a cn-heavy/xhv -o stratum+tcp://cryptonight_haven.mine.zergpool.com:4452 -u <YOURXHVWALLET> -p c=XHV,mc=XHV Option 3 Direct coin mining with autoexchange to specified coin wallet(BTC in example below) -a cn-heavy/xhv -o stratum+tcp://cryptonight_haven.mine.zergpool.com:4452 -u <YOURBTCWALLET> -p c=BTC,mc=XHV Please note mc stands for mining coin symbol, c stand for payout coin symbol Autoexchange to BTC, LTC, DASH, BCH, DOGE or any other currency we mine Happy mining, cheers pinpin
|
|
|
|
goshiz
Jr. Member
Offline
Activity: 34
Merit: 3
|
|
January 09, 2020, 05:43:19 PM |
|
|
|
|
|
|
|
goshiz
Jr. Member
Offline
Activity: 34
Merit: 3
|
|
May 17, 2020, 08:07:47 AM |
|
Hi guys, here is the new Medium article from Haven: https://medium.com/@havencurrency/haven-deep-dive-cracking-the-xusd-code-8b5c7bd5f42Neac (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.
|
|
|
|
goshiz
Jr. Member
Offline
Activity: 34
Merit: 3
|
|
June 17, 2020, 03:46:48 PM |
|
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: 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. 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. 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. 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. 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. 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.
|
|
|
|
Iamtutut
|
|
June 17, 2020, 04:13:30 PM |
|
Confirmed on Haven team twitter account.
|
|
|
|
Atomjuice
Member
Offline
Activity: 103
Merit: 10
|
|
June 18, 2020, 01:04:59 PM |
|
..your f*cking wallet does not work..started mining on herominers..coins mined never went to your scumbag rippoff scamcoin wallet..thats it for me..just another shitcoin scamcoin!! PEOPLE: BEWARE Your 'wallet'..doesn't sync in time..fucking hangs all the time..took me 2 days to download the chain..and wasted that along with the time my rig was on your shitcoin..
|
|
|
|
pikomule
Newbie
Offline
Activity: 32
Merit: 0
|
|
June 18, 2020, 01:07:08 PM |
|
..your f*cking wallet does not work..started mining on herominers..coins mined never went to your scumbag rippoff scamcoin wallet..thats it for me..just another shitcoin scamcoin!! PEOPLE: BEWARE Your 'wallet'..doesn't sync in time..fucking hangs all the time..took me 2 days to download the chain..and wasted that along with the time my rig was on your shitcoin..
I have also had many problems with wallets, including the web wallet. Finally I could send with the CLI verion of 40xhv every time, more xhv gives error
|
|
|
|
Iamtutut
|
|
June 19, 2020, 08:14:03 AM |
|
..your f*cking wallet does not work..started mining on herominers..coins mined never went to your scumbag rippoff scamcoin wallet..thats it for me..just another shitcoin scamcoin!! PEOPLE: BEWARE Your 'wallet'..doesn't sync in time..fucking hangs all the time..took me 2 days to download the chain..and wasted that along with the time my rig was on your shitcoin..
Use the web wallet with your seed, it works perfectly.
|
|
|
|
pikomule
Newbie
Offline
Activity: 32
Merit: 0
|
|
June 19, 2020, 08:15:14 AM |
|
..your f*cking wallet does not work..started mining on herominers..coins mined never went to your scumbag rippoff scamcoin wallet..thats it for me..just another shitcoin scamcoin!! PEOPLE: BEWARE Your 'wallet'..doesn't sync in time..fucking hangs all the time..took me 2 days to download the chain..and wasted that along with the time my rig was on your shitcoin..
Use the web wallet with your seed, it works perfectly. not work perfectly. much error to send
|
|
|
|
Iamtutut
|
|
June 19, 2020, 08:58:42 AM |
|
I don't have issues.
|
|
|
|
pikomule
Newbie
Offline
Activity: 32
Merit: 0
|
|
June 19, 2020, 09:00:37 AM |
|
I don't have issues.
I could not send xhv to tradeogre, always error. I did it with CLI
|
|
|
|
|