Jump to content

Adrian Dobrita

Elrond Team
  • Content Count

  • Joined

  • Last visited

  • Days Won


Adrian Dobrita last won the day on January 21

Adrian Dobrita had the most liked content!

Community Reputation

12 Good

About Adrian Dobrita

  • Rank
    Elrond Core

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. It is not possible to delegate less than 10 eGLD. This is because more fragmented delegations would incur larger gas costs for other operations, like swapping active delegation with staking queue delegation, or increased storage access due to larger SC state. This is also a sort of sybil attack prevention. The difference between staking and delegation is that for staking you need to "lock" 2500 egld in order to run a validator and you need to take care of the machine running the validator software, keep it online, make sure it has good network connection, etc, while for delegation yo
  2. 1. The queue/waiting list will no longer be incentivized, but at the same time more "seats" will be available for staking and the delegation manager will be available for staking providers. At this point we might see some migration from active delegation and/or waiting list delegation to active delegation for staking providers. The nodes for the community nodes delegation will not be supplemented, so active delegation will only become available on the community delegation smart contract if someone with active delegation withdraws. 2. The option for staking providers to choose differe
  3. The deposit will accrue rewards for the SP only if it becomes part of a node stake. If for example the delegation amount + SP deposit <2500 eGLD then it would not receive rewards, as there will be no eligible node to earn rewards. As soon as there is at least one eligible validator with stake from the delegation SC, then the original deposit will also accrue rewards just as you mentioned.
  4. Hi Kevin and welcome! At least for the next few months there is no plan to change the minimum stake per validator node. There is a "soft-auction" in development which we refer to as Phase 4 Staking Proposal, where the price per node can be dynamically adjusted, but not sure though if it will cause the price to go lower as currently there seems to be significant demand. There will also be a minimum price per node as well there, but not all parameters have been decided so I can't say for now what that will be. Before that though, we have prepared the Phase 3 Staking Proposal which
  5. the argument there: 0x0002540be400 represents the supply = 10 000 000 000 in hex.
  6. For 1 there is also the option for you to not go through the provided delegation manager contract and create your own delegation Smart Contract, where you can set your own rules, no minimum delegated amount from staking provider, etc., but here all the coding/gas optimization/validation/testing/auditing efforts will be on your side, which is really important as the risk for loss of funds in case of bugs is high. We have already spent a lot of time for the coding/testing/auditing etc of the delegation manager system SC and more will follow on the testnet, so for the people that do not have
  7. Hi Milan, 1. If you run a staking service (accept delegations) there is a delegation manager contract that allows you to create your own delegation contract with your preferred configuration (service fee, delegation cap, etc). For this you need to come with 1250 eGLD yourself, which will be the first delegated amount (your own delegation) and is required in order to keep your delegation contract active. Everything else can come from other delegators. 2. Yes the node will be deactivated by the protocol while the staked amount is below the minimum required. If in the meantime there is
  8. Most probably sometime in February (I estimate end of February - early March). The date is not fixed as we have been focusing mostly on testing the features required for Maiar launch which comes first. The implementation for phase 3 is already done and some testing has been performed but we still need/planned more testing and it also depends on what kind of issues we still find.
  9. Every separate delegation creates a new entry at the end of the existing queue.
  10. Actually there is one change, where we plan to remove the maximum number of nodes limit, this is for when we introduce phase 4 staking which was briefly touched in the proposal, but the effect would be that we can have no limit for registering nodes, but in every epoch you would also only have 1600 nodes eligible, out of all registered ones, with a maximum of 20% swap ratio for shuffling, the nodes shuffled into eligible list being the best qualified nodes (considering stake value and possibly rating)
  11. As long as we don't change the number of shards, this should stay. Increasing the number of shards will only be triggered when we reach a high enough block fill ratio and implicitly TPS (one block has a capacity of 1.5 *10^9 gas). I would not expect to have the change before we reach ~40% average fill ratio of the block capacity, which would mean 10k-12k regular transactions/block (~6k TPS for the current network setting) It would be amazing to reach this in the next one year, but very difficult. Also unregistering elrond foundation nodes will not affect the maximum number
  12. also until you reach step 11, please do not close the bridge page, use different tabs for the wallet, etc.
  13. Hi Marian, The bridge should still be functional I just tried swapping some leftover ERD ERC20 tokens following the steps provided in the links above and seems to be ok, but you need to follow the steps exactly, otherwise best case it will not work and report an error just like it did for you, or worst case you will send the tokens somewhere else. The exact steps I did: 1. go to https://bridge.elrond.com/ 2. choose in first field ERD ERC20 (Ethereum) 3. go to https://wallet.elrond.com/ and follow the steps to create a eGLD wallet on mainnet (or access existing one if y
  14. Hi Marius, The removal of Elrond foundation nodes is not yet in discussion for the phase 3 release, this will be further down the line and will be announced beforehand. But just for the sake of discussion, the mechanism should be fairly simple, one option (which in my opinion would also be elegant) would be to keep the extra stake from the removed keys(nodes) as TopUp stake on the remaining nodes. This will indeed cause the return per staked token to decrease on average a bit, since the topUp stake APR is always below the base stake APR, but will also allow SaaS providers to become a
  15. Currently only the owner (SP wallet) can add or remove nodes. If there really is a need for this, we can improve and add some options in future iterations, but to keep things simple and the edge cases manageable I would keep it like this for the first release.
  • Create New...