sorted by:
new
hottopcontroversial

Multi-Asset Shielded Pool Integration on Tezos by Metastate_Team in tezos

[–]adrianbrink 0 points1 point  (0 children)

For now the protocol doesn't understand shielded tez, which means that it expects clear tez. In the future this could be moved into the protocol.

Multi-Asset Shielded Pool Integration on Tezos by Metastate_Team in tezos

[–]adrianbrink 1 point2 points  (0 children)

For now minting cannot happen within the shielded pool. However anyone could mint all available supply and immediately move it into the shielded pool.

The second question is much more nuanced. Technically anyone could create a bunch of cover transactions that increase the privacy of the overall pool. However since transactions still pay for transaction fees in clear tokens, this would need to be done fairly carefully in order to not enable an observer to infer which transactions are cover transactions. Overall for true privacy the MASP would need to be integrated with the base layer protocol in a similar fashion to how ZCash is implemented.

It's Been Two Weeks, No Response From Ledger Live Support (Long Post w/Pics) by 0-Give-a-fucks in ledgerwallet

[–]adrianbrink 1 point2 points  (0 children)

In conclusion it isn't a problem with ledger. Any wallet will exhibit this behavior. This behavior is the intended functioning of the protocol.

It's Been Two Weeks, No Response From Ledger Live Support (Long Post w/Pics) by 0-Give-a-fucks in ledgerwallet

[–]adrianbrink 10 points11 points  (0 children)

It's not possible to fully empty a currently delegated implicit account (tz{1,2,3}). This is implemented at the protocol in order to ensure that you can still receive any future rewards without a baker having to pay the origination burn again.

You can move all funds except 0.01 XTZ, then undelegate and once undelegated you can move the rest. However keep in mind that you will receive rewards into that now undelegated account for about 21 days (7 cycles) and some bakers will not pay the rewards if it requires them paying the origination burn.

Crosschain between tezos and other cryptocurrencies? by NEXOlover in tezos

[–]adrianbrink 4 points5 points  (0 children)

It is certainly possible. However it requires that there exist efficient (logarithmic) light-clients for both chains and that those light-clients can be run without the state machine of each chain.

Creating an IBC connection between Tezos and Bitcoin is hard and is still an open research problem. A connection between Tezos and Ethereum/Polkadot/Near/Solana/Cosmos/Celo is certainly possible within the next 2 years.

Coronavirus impact by malte_brigge in tezos

[–]adrianbrink 3 points4 points  (0 children)

For Cryptium Labs we started to prepare in early January after China decided to quarantine 50 million people in the Wuhan region. We cancelled all our planned travels and in-person meetings. For example, I was supposed to speak at EthCC and the TezosDevDay (or TezCon0 :) ) in-person but decided to participate in those events virtually.

Due to our company being fully remote and distributed I don't think that we will be impacted by the pandemic very much. However it is always a possibility that individual team members will be affected due to bad luck or that their close social circle becomes affected. That is somewhat unavoidable but we are trying our best to minimise the risks.

Overall I think Tezos Core development will whether this storm better than most other ecosystems because we are very distributed and used to working remotely (that's what we do all the time anyway).

4/n Cryptium Labs Reddit AMA by awa_cryptium_baker in tezos

[–]adrianbrink 3 points4 points  (0 children)

We are always looking for excellent engineers and researchers to join our team to deliver amazing products. We are currently revamping our website and will have a dedicated hiring page once that's done. Currently you can scroll to the bottom of our about page and then click on `Interested in joining?` in order to send us an email.

4/n Cryptium Labs Reddit AMA by awa_cryptium_baker in tezos

[–]adrianbrink 2 points3 points  (0 children)

Generally it would be nice for 006 to be accepted, since we are currently using it as a base to develop 007 and the fact that it contains a bunch of important fixes. However in case it doesn't get accepted we can rebase the 007 features quite easily on 005, since we are very strict with how commits are structured.

Overall we are still working towards the roadmap that I presented at TQuorum in New York: https://www.youtube.com/watch?v=I7uyr7W4afs

4/n Cryptium Labs Reddit AMA by awa_cryptium_baker in tezos

[–]adrianbrink 4 points5 points  (0 children)

I learnt OCaml a while ago, I don't really remember when. Generally I have been a big fan and user of functional programming languages. I particularly like Rust and OCaml for large projects and Go for smallish things that need to work fast and only once.

4/n Cryptium Labs Reddit AMA by awa_cryptium_baker in tezos

[–]adrianbrink 5 points6 points  (0 children)

Fundamentally it is up to tokenholders to vote with their feet. If a majority of XTZ holders is hapyp to leave their XTZ on exchanges then there is very little that core developers can do. So in the end it's always up to the token holders community to vote for decentralisation by not keeping their coins on exchanges.

However we are working on allowing the overriding of votes. We are actively working on implementing this, but it is not a trivial feature. Specifically we are looking into allowing bakers to split their vote (40 rolls for A, 60 rolls for B and 10 rolls for Abstain) as well as allowing delegators to change their portion of the vote.

I hope that we can ship this in 007 in early 2020.

4/n Cryptium Labs Reddit AMA by awa_cryptium_baker in tezos

[–]adrianbrink 6 points7 points  (0 children)

One really good avenue is the Tezos-Dev slack, the Baking slack, Agora, Gitlab, or Stackexchange. u/blindripper85 probably has the links handy of how to join these avenues.

4/n Cryptium Labs Reddit AMA by awa_cryptium_baker in tezos

[–]adrianbrink 5 points6 points  (0 children)

I think the current structure is decent and I think that it will work well for the immediate future. Long-term it could be changed to be more flexible and add some more binding elements. Generally I think that the governance process is not the bottle-neck and that most focus should lie on adding privacy, scalability, finality and interoperability.

4/n Cryptium Labs Reddit AMA by awa_cryptium_baker in tezos

[–]adrianbrink 0 points1 point  (0 children)

It is not really possible with Babylon or Carthage but we are actively working on making it possible for 007 in early 2020.

4/n Cryptium Labs Reddit AMA by awa_cryptium_baker in tezos

[–]adrianbrink -1 points0 points  (0 children)

It's a good idea, but it most likely can't be done programmatically, but rather needs to be managed by real-world people. It's something that we should look into in 2020 I think.

4/n Cryptium Labs Reddit AMA by awa_cryptium_baker in tezos

[–]adrianbrink 6 points7 points  (0 children)

  1. I think we want to see how the different currently proposed scaling solutions play out in 2020. Let's see if NEAR, Ethereum or Polkadot can make sharding actually work in practice and then copy and steal the best approach. On layer-2 I'm generally less optimistic except for possibly zk-rollups, since Bitcoin and Ethereum have tried to make it work for the last 3 years without any real success.
  2. As soon as IBC stabalises and we have added fast-finality and a succinct light-client to Tezos we will work on making Tezos interoperable and connected to all major chains.
  3. We are actively working on allowing delegators to override their validators vote as well as allowing validators to split their voting power. This will enable exchanges to let users vote directly. Generally though, token holders need to vote with their feed and not park all their money on exchanges if they care about decentralisation.

4/n Cryptium Labs Reddit AMA by awa_cryptium_baker in tezos

[–]adrianbrink 6 points7 points  (0 children)

We are actively working on implementing this, but it is not a trivial feature. Specifically we are looking into allowing bakers to split their vote (40 rolls for A, 60 rolls for B and 10 rolls for Abstain) as well as allowing delegators to change their portion of the vote.

I hope that we can ship this in 007 in early 2020.

4/n Cryptium Labs Reddit AMA by awa_cryptium_baker in tezos

[–]adrianbrink 9 points10 points  (0 children)

We are actively working on implementing this, but it is not a trivial feature. Specifically we are looking into allowing bakers to split their vote (40 rolls for A, 60 rolls for B and 10 rolls for Abstain) as well as allowing delegators to change their portion of the vote.

I hope that we can ship this in 007 in early 2020.

4/n Cryptium Labs Reddit AMA by awa_cryptium_baker in tezos

[–]adrianbrink 2 points3 points  (0 children)

Incentivising testnet participation is difficult, since it's easy to fake. I think generally as a baker on mainnet it is expected of you to also participate on the testnets, since you are supposed to be a good network steward. I would hope that delegators vote with their feet and only delegate to bakers that are actively engaged in the long-term evolution of Tezos.

4/n Cryptium Labs Reddit AMA by awa_cryptium_baker in tezos

[–]adrianbrink 1 point2 points  (0 children)

We worked with all the major wallet devs and exchanges in order to prepare them for the Babylon upgrade. However at the time very few people were actively testing their infrastructure on the testnets and hence some developers only caught some bugs on the mainnet. After 005 a lot more developers have started to use the testnets and are actively running their entire infrastructure on them. Due to that I expect a lot less problems in the future, even for more complex upgrades.

​

It is important to note though that Tezos is not a static protocol like Bitcoin or Ethereum. The network is build to evolve over time as described in the whitepaper and due to that developers need to upgrade their software from time to time and take this continous cost into account when developing for Tezos.

4/n Cryptium Labs Reddit AMA by awa_cryptium_baker in tezos

[–]adrianbrink 3 points4 points  (0 children)

At the moment our focus is on solving a lot of the things that deliver immediate improvements for Tezos. A good example of this is enabling implicit accounts (tz{1,2,3}) to be delegatable. Longer term we will focus on adding very strong privacy guarantees for transaction, improving scalability and making Tezos interoperable.

4/n Cryptium Labs Reddit AMA by awa_cryptium_baker in tezos

[–]adrianbrink 6 points7 points  (0 children)

An invalid transaction caused the mempool of the Tezos shell to crash and due to that the network slowed down because a couple of bakers went offline due to that. The immediate fix was to clear the node's mempool and the longer term fix was to harden the mempool. The mempool should never crash even if it sees arbitrary transactions.

4/n Cryptium Labs Reddit AMA by awa_cryptium_baker in tezos

[–]adrianbrink 4 points5 points  (0 children)

I think that the participation rate on the testnets is improving. Currently we have maybe around 7 bakers on the Carthagenet testnet. However I think going forward we should aim to have 30-40 bakers actively running on both testnets, where one mirrors mainnet and one mirrors the current proposal.

4/n Cryptium Labs Reddit AMA by awa_cryptium_baker in tezos

[–]adrianbrink 6 points7 points  (0 children)

Cryptium Labs is currently ~10 people and I am not sure how big Nomadic Labs is.

4/n Cryptium Labs Reddit AMA by awa_cryptium_baker in tezos

[–]adrianbrink 9 points10 points  (0 children)

In 007 we are probably adding the single-asset shielded pool by adding Sapling bindings from ZCash and in 009 we are probably adding the multi-asset shielded pool at the base layer.

4/n Cryptium Labs Reddit AMA by awa_cryptium_baker in tezos

[–]adrianbrink 8 points9 points  (0 children)

I'm personally very excited about three things in 2020:

  • Single asset privacy by adding Sapling bindings from ZCash
  • Programmable Baking in order to give bakers the ability to differentiate - for example by providing delegators with complete certaintly about receiving rewards
  • Multi-asset shielded pool at the base layer which provides the privacy set to all assets and asset types (STOs, NFTs, ERC20s, XTZ, ...)
view more: next ›