Mkt Cap $0 Volume $980K
|$3.92฿ 0.00061400||$0||$980K XTZ 250K||-9.43%|
Trying to find out how the beta net will work and got this from AB. My 35 year old basic programming class from high school didn't cover this.
[–]murbardfounder 1 point 51 minutes ago There's been some good documentation for the CLI for a while: http://doc.tzalpha.net/api/cli-commands.html#tezos-client-commands permalinkembedsaveparentreportgive goldreply
If you think about timing of tezos launch, huge investors in ICO its getting not impossible to have tezos on coinbase. What you think?
Ubuntu 18.04 LTS is ready on a dedicated machine.
Once betanet is released I'd like to install a tezos solo-bake node according to this guideline:
And put only the xtz for bonds/endorsements to the node. The rest I'd like to delegate according to this guide: https://www.reddit.com/r/tezos/comments/8sr8qt/practical_instructions_to_keep_most_of_your/
When my solo-bake node is up and running I'd like to transfer all tezos-related stuff to another Ubuntu installation that runs in a VM. (reason: when I have to shutdown my main solo-bake node for maintenanc purpuse I can start the VM on my notebook in between)
(remark: I know I mustn't run the VM-ware node at the same time when my main node is up and running. Only one node is allowed to work)
Thanks for your suggestions!
I was just browsing the interwebs, and I cam across this theorem https://en.wikipedia.org/wiki/CAP_theorem .
It says there are 3 guarantees that any distributed system can offer, and it is impossible for any distributed system to offer all three.
The 3 guarantees are :
Does anyone know which 2 Tezos has chosen, and why?
Starting to look through the KYC process in preparation to do this myself (Yes, this is the first time I am looking at it). The entire “Terms and Conditions” document is something that is new. You need to check this box to do KYC and therefore agree to these terms and enter into a contract. This is NOT KYC but a separate contract which nobody has mentioned so far.
Information is a good thing! People that are going to downvote something like this – you only show your ignorance. This is not my communication this is from TF. If you think that their terms and conditions are FUD then hassle TF and not me.
Here are some key aspects of the agreement we are accepting:
This appears to be fairly focused attempt to restrict any legal action against TF and the founders or if there is a way to come after them it makes it painful to do so – needing to do it in Zug and individually instead of as a group. It also makes me think that KYC is solely for the purposes of legal jockeying in relation to the current class action suits although it seems to me that a court would sweep this aside.. Perhaps it also has the added benefit of protecting the liquidity of TF because the courts may now reject an American request to freeze funds... I am not enough of a legal expert to interpret how this may impact the class action suits. Am I reading this correctly?
(This is not legal advice and I am not a lawyer – this is only for purposes of a Reddit discussion)
For you thoughtful people I would love to hear opinions on this.
For you Ignorant
What is this about?
for solo bakers all the tezzies can be stored in one account. However the secret key of the account has to be made available on the Tezos node, which practically means that it is either present all the time or the baker has to manually copy the key after the node has been selected for baking/endorsement so that the a deposit can be made(note on ledger*). It is assumed that the node is not accessible remotely (security first) but still the situation is potentially risky.
To make baking safer, one possibility is to create a delegate account that will store only the tezzies for the deposits and a delegated account with the rest of the tezzies. These tezzies contribute to the rolls while they remain safe with the secret key stored offline.
To find out how, follow this link
Feel free to experiment on the zeronet (it should also work on the betanet with minor or no modifications). The only requirement is to have access to a Tezos node (any OS, with/without docker). Feedback is not only welcome but almost necessary (I do make mistakes! a lot). I decided to post this note before completing few more tests (updates posted on the page linked above) to help more solo-bakers practicing before the imminent launch of the betanet.
If there are better or simpler ways, please let me know. In fact, if there is enough traction from other solo-bakers, the above link could be moved from the tezos-RPI3 wiki home where it is based now, to a dedicated wiki page where all kind of methods to setup a safe and secure home baking node could be gathered in one place.
(note on ledger*) Based on my very limited knowledge, with a ledger there is no need to manually copy the key into the file "secret_keys" since any requested operation is signed automatically and it can be done from any machine remotely. It is unclear to me whether the ledger can be used to issue a bond. If that is the case then it has to be plugged in from time to time to make the deposit payment from a [baker_account] (for the definition of [baker_account] follow the link). In addition the ledger can be also used to delegate, assuming that the owner has a [secondary_account] (follow the link) and wants to delegate to his/her own [baking_account] or a third party [baking_account]
Since we are closer to lunch then ever before I am quite concerned with delegating my tezies right from the day 1.
I didn’t want to solo bake, as it requires a lot of security measures and 24/7 hardware stability. However, all of the delegation services I found on the internet are not answering my e-mails, moreover, many of them look abandoned.
The question is. Is solo baking the only option to start baking from day 1, or will there be any actual running delegates?