i think some exchange in china will list XEL after the project release.  |
|
|
|
|
any timeline for the step one you mentioned earlier, and how do people participate into the test Phase of this amazing project?
thank you!
|
|
|
|
Is there a simple doc or wiki on this? And one more question - it looks like Elastic editor is not just an editor, but is an IDE which has a debugger too..? Is that correct? If thats a case, that would be amazing!   I will make a small "Elastic PL" book and put in online. It will cover all functions, example code snippets, and some background information on the Elastic Network ;-) RIght now the IDE is an editor, a compiler and a memory debugger. In the long term it would be cool if it supported also publishing work to the Elastic Network and controling live work packages. All from one single place ;-) that's great news, this project is far more better than that ethereum based golem project...they delivery nothing, i think... cheers XEL！thank you EK, you are making the project become true. |
|
|
|
Step 1: The Mainnet is locked and offline. In order to launch it, 25% of all tokens must be redeemed. This essentially means that the users (to recall, I code this for you guys) decide thenselves when to launch or not to launch. If the whales think the code sucks, they just delay! when step one start?  |
|
|
|
|
when will step one start?
|
|
|
|
|
Maybe do the signature for every TX again ?
Since only signature can prove you have the private key.
|
|
|
|
Yes, signed message cannot be abused easily.
This part below is mostly IMHO Frankly speaking, I believe having only signature way of linking the Bitcoin address would be just enough. This microtracsaction method only messes things up. If user does not know how to sign, he could learn. If his wallet does not have signing capability, he can move his Bitcoins to a wallet which has that capability. This could be a good reason for someone to educate himself, and prove he really wants to have Byteball! Kind of a PoW - "proof of work", "proof of willingness", "proof of worthiness" This is good point and I agree with that. This will largely simplify the process and prove clearly that you must have the private key of the wallet, avoiding people to send micropayments from some common wallets and take the chance. also vote for signature proof only. Micro payment has a lot tricky, and not that good enough. almost every main btc wallet support signature. |
|
|
|
|
So right now we are at the open test phase?
who will do the code review?
|
|
|
|
Thanks, it works and it took about 6h to sync. The wallet is good looking. Exploring the settings I saved the seed and created a spending password as I would do on the real network. I'm confused by the backup part, the instructions say that the seed isn't enough to recreate the account but you need other settings too but it doesn't say which ones or how to save them (I don't remember the exact phrase because it was deleted along the seed after I saved it).
I agree with this assessment - I think clearer instructions on how to backup the wallet are necessary. You need to back up the entire data folder (~/.config/Byteball test on linux). This folder includes private payments (blackbytes) which are not restorable from the seed. A better way to prepare for the device loss or failure, is by setting up a multi-sig wallet with redundancy, then you'll automatically have several copies of private payments on multiple devices. how do i backup wallet on Windows? thank you I downloaded the light wallet. To back up my wallet, what else should I do besides writing down my wallet seed?
It seems I don't need the wallet seed to log into my wallet/account. Is it right?
The seed is almost never needed. If you are on Windows, backup the folder C:\Users\YOURUSERNAME\Local\AppData\byteball. where is key file? seems Appdata/bateball is a empty file for me. my byteball install under C/program files (x86)/byteball and it's a big big folder, seems it's about more than 300MB |
|
|
|
|
when i linked my BTC address, i only have 1 BTC in my address, can i send another 2 BTC 10 days later?
will it counter as 1BTC as my balance or 3BTC as my balance? thank you very much.
|
|
|
|
Thanks, it works and it took about 6h to sync. The wallet is good looking. Exploring the settings I saved the seed and created a spending password as I would do on the real network. I'm confused by the backup part, the instructions say that the seed isn't enough to recreate the account but you need other settings too but it doesn't say which ones or how to save them (I don't remember the exact phrase because it was deleted along the seed after I saved it).
I agree with this assessment - I think clearer instructions on how to backup the wallet are necessary. You need to back up the entire data folder (~/.config/Byteball test on linux). This folder includes private payments (blackbytes) which are not restorable from the seed. A better way to prepare for the device loss or failure, is by setting up a multi-sig wallet with redundancy, then you'll automatically have several copies of private payments on multiple devices. how do i backup wallet on Windows? thank you |
|
|
|
|
how to backup the byteball wallet ?
back seed is not enough?
thank you very much!
|
|
|
|
@EK as a part of a bug bounty please post at public passphrase (aka private key) to XEL-9HQ9-BXCV-TARZ-BRDNA account. We want to test if we can spend/forge/do anything with this account. As all of you know this account is used for redeem XEL to original donators. This address also need to be secured for a lot of attack factors. I know that this address could (and will change) when mainnet will be live but we need to be sure that this address is bulletproof before mainnet (and logic/code is in place before then).
Thanks! I'll test this address as soon as you post passphrase for this account.
Password is exactly the way it is written nice password. Should be longer. |
|
|
|
|
also after link, when can we get the first real byteball? and what's the timeline to distribute the left byte all?
|
|
|
|
|
what's the basket mechanism ...?
thank you
|
|
|
|
A few small bugs in the miner are being solved right now,
and the new retargeting method is being tested locally right now ... I guess we can put it into the testnet in a few hours.
Now it's time for some contests where people can get some BTC if they crash the software or manage to steal funds. Getting rid of any potential bugs is the main part that is left.
Everything else works perfectly.
Tu sum up: We just need to get the GPU miner ready, and stress test for the last remaining bugs and that's it i guess.
Except BTC bounty, I think community can commit some XEL as bounty. |
|
|
|
|
yes we can vote for the donations.
that's will make the governance of XEL more easier.
|
|
|
|
hi where is the Transition Bot？ had it been deleted from the official website? thank you very much. Finally, you can experience the pre-distribution linking of Byteball and Bitcoin addresses. We are launching a new testnet, and you'll be able to get a portion of its distribution in proportion to your balance in Bitcoin testnet. 0. Get your Bitcoin testnet wallet ready and funded. 1. Download and install the wallet for the new Byteball testnet: https://github.com/byteball/byteball/releasesYou will have two Byteball wallets - one for the old testnet that you already have, the other for the upcoming new testnet. 2. Visit https://byteball.org and click the link to chat with the Transition Bot. The link will open the new wallet and start a chat. Follow the instructions of the Transition Bot to prove your Bitcoin balance.  You have two options to prove your Bitcoin balance: a. By making a micropayment. The bot will see your address the payment came from, will know that it is your address, and will instruct you to move your Bitcoins to this address. By making several micropayments, you can link several Bitcoin addresses to the same Byteball address. b. By signing a message (if your Bitcoin wallet supports this function). You tell the bot your Bitcoin address and sign your Byteball address with the Bitcoin address. After you prove one address (a typical Bitcoin wallet has dozens of them), you can either move all your coins to this single proven address or prove all other addresses in the same way -- by signing a message. Update: to clarify, if you try to link the same Bitcoin address to multiple Byteball addresses, only the last linking counts. If you prove by micropayment, remember to check that the Bitcoin address that the bot received the micropayment from, is indeed your address. An attacker might see your payment on the blockchain and repeat the same micropayment from his address trying to trick you to move your funds to him. 3. After linking, there is no use of the new wallet before the distribution, just keep it installed (backup if necessary). It will receive the bytes on the distribution day. If you make any Bitcoin payment, your coins will most likely be moved to a new change address. Chat with the bot again, see the balance on your linked address(es) and move the coins back to the linked address(es) if necessary. The linking phase will end in late November, after which we'll do the distribution for the new testnet. Those who linked their Byteball and Bitcoin addresses will receive new test bytes in proportion to their Bitcoin testnet balances on the distribution day. If all goes well, we'll do exactly same linking, but with real Bitcoin addresses, from early December to December 25 before the upcoming livenet launch and distribution. Please retweet https://twitter.com/ByteballOrg/status/796810412935282688 |
|
|
|
|
how about EK post a donation address for XEL？
So when XEL release i would like to donate 5% of my share to support XEL long term development.
It's a not easy project,but EK did a great job and never disappoint us.
Also for more donation, we can reward HMC some XEL for his talent work too.
|
|
|
|
Well, unfortunately it ends tomorrow 07:51:39 PM forum time.
Am I correct in that this means that there is just under 20 hours remaining? That should be plenty of time... welcome back HMC. |
|
|
|
|
Show Posts
