Tezos News

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

Hodl'ing Proof of stake coin like Tezos: 5-10% reward

Hodl'ing proof of work coin: ........nope.

Anyone have an estimate on the percentage of tokens which will go unclaimed due to lost PDFs, passwords, etc?

Also, what will happen to said tokens?

If you think about timing of tezos launch, huge investors in ICO its getting not impossible to have tezos on coinbase. What you think?
https://twitter.com/GDAX/status/1008768547668070400

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:

https://github.com/tezoscommunity/FAQ/wiki/Build-a-zeronet-node-on-Debian-9

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)

• How can I do this? How do I get my xtz for endorsements duplicated to the VM? How do I get my delegated XTZ for the roll(s) duplicated?
• Another question: when I was offline for a certain time due to the swich from the main node to the backup node do I have to execute some special commands on the other node to get everything up and running or do I just have to start up the backup node?

(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!

Hey everyone,

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 :

• Consistency: Every read receives the most recent write or an error
• Availability: Every request receives a (non-error) response – without guarantee that it contains the most recent write
• Partition tolerance: The system continues to operate despite an arbitrary number of messages being dropped (or delayed) by the network between nodes

Does anyone know which 2 Tezos has chosen, and why?

Thanks.

Even though US people are getting activation codes, I'm not sure I will feel comfortable until people confirm they received tokens. Anyone else?

If tezos can top bitcoin marketcap if they can some good tech partnership ....they tech nology looks solid ...

So, I sent my email verification to Tezos but have not received a link to the KYC verification. Is there a way to email them?

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:

• First Paragraph: “The following terms and conditions (“Terms”) govern your acceptance and use of the Tezos Foundation’s recommended allocation of XTZ in its proposed genesis block (including in connection with the Tezos Network).” Notes – This seems to make it clear, if you want the tokens you will need to agree to the following. Interesting that it only covers the “genesis block”. Does this mean that this does not cover tokens from post genesis block or from people who buy on exchanges?
• Your Assumption of Risk Regarding XTZ: This seems to be pretty basic stuff that most of us already assumed when we signed up. If our tokens are lost, for whatever reason, we agree not to blame TF. While we all accept the risk of tokens this also adds the idea that if TF screws up and loses our tokens we cannot come after TF.
• The Tezos Network: This portion is where you agree not to harm the network. While everyone here has a vested interest in the network and would not harm it – it seems a little odd. Kind of like the passing of a law that makes it illegal for criminals to become criminals. In any case, this is added liability on your part. If you were to buy tokens post launch from an exchange you would not be liable in the same way as the original founding members of the network.
• Your Responsibility to Keep the Information Available to you Confidential: This is an odd paragraph. It apparently says that we agree that we are responsible to maintain our confidentiality, TF is NOT liable, and we consent to allow TF do anything they want with the data. Notes – this seems about as one sided as it gets...
  
• Disclaimers: TF makes no representation, blah blah blah, use tokens AS IS, blah blah blah, no warranty, blah blah blah.
• Limitation of Liability: You agree that you cannot take any legal action against TF for any reason, at all, ever. If you live in a jurisdiction that does not allow this in a contract – your use of XTZ tokens is unauthorized.
• Dispute resolution: All disputes shall take place in the courts based in Zug, Switzerland. In addition, you are not allowed to be a part of a Class Action Suit. You must take legal action individually.
• User Disputes: If you get into a dispute with another user you will need to settle it yourselves – you agree that you will not come after TF.
• General: Governed by the laws of Switzerland, this agreement supersedes anything that was said previously by TF and the rest of the crew. The rest seems like standard legalese in all contracts.

My conclusion

• The people this protects is TF, the founders, and developers
• It seems narrowly focused on the people who donated and are a part of the genesis block.
• TF can do anything it deems necessary with your private data and you agree not to come after them.
• Once you accept tokens you cannot be a part of a class action suit
• You agree to accept all liability in regards to tokens and agree to not come after TF or anyone associated with the creation of TF.
• This agreement is valid in Switzerland however if you live in a country where this contract is not valid your tokens are hereby unauthorized. (this does not give me warm fuzzies on the inside as I don't live in Switzerland)

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
https://github.com/maxtez-raspbaker/tezos-rpi3/wiki/%5B0%5D-Simple-instructions-to-bake-and-keep-(most-of)-your-tezzies-offline

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]

I think the foundation mentioned last week they will be sending the codes couple of days before the launch...now that they are out do you think launch is happening next week?

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?

Can someone please help me with this activation code? It appears a lot have people have received theirs already, have they all been sent out at the same time and should I be panicking?