You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/pos/how-to/delegate.md
+2-7Lines changed: 2 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -422,14 +422,9 @@ The Polygon Wallet Suite is a web application.
422
422
423
423
First, you must withdraw your funds from Binance or any other exchange to your Ethereum address on Metamask. If you don't know how to use Metamask, google it a bit. There are plenty of videos and blogs to get started with it.
424
424
425
-
### When can I become a validator and how many tokens do I for that?
425
+
### When can I become a validator and how many tokens do I need for that?
426
426
427
-
A user can earn a validator spot only by if the below conditions come into play:
428
-
429
-
1. When a validator decides to unstake from the network, or
430
-
2. Wait for the auction mechanism and replace the inactive validator.
431
-
432
-
The minimum stake depends on the auction process where one user outbids another.
427
+
To become a validator in the PoS network, you'll need to hold and stake a minimum of 10,000 POL tokens, and go through an admissions process to ensure network security."
433
428
434
429
### If I have earned rewards while delegating, and if I add additional funds to the same validator node, what happens?
Copy file name to clipboardExpand all lines: docs/pos/reference/contracts/stakingmanager.md
+1-29Lines changed: 1 addition & 29 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -56,7 +56,7 @@ function stakeFor(
56
56
```
57
57
58
58
- Allows anyone with amount (in MATIC tokens) greater than `minDeposit`, if `currentValidatorSetSize` is less then `validatorThreshold`.
59
-
- Must transfer `amount+heimdallFee`, puts validator into auction period for an `auctionInterval` (more in Auction section).
59
+
- Must transfer `amount+heimdallFee`.
60
60
-`updateTimeLine` updates special timeline data structure, which keeps track of active validators and active stake for given epoch / checkpoint count.
61
61
- One unique `NFT` is minted on each new `stake` or `stakeFor` call, which can be transferred to anyone but can be owned 1:1 Ethereum address.
62
62
-`acceptDelegation` set to true if validators want to accept delegation, `ValidatorShare` contract is deployed for the validator.
@@ -127,34 +127,6 @@ Note that `accountStateRoot` is re-written to prevent exits on multiple checkpoi
127
127
128
128
Standard ERC721 contract with few restrictions like one token per user and minted in sequential manner.
129
129
130
-
### `startAuction`
131
-
132
-
```solidity
133
-
function startAuction(
134
-
uint256 validatorId, /** auction for validator */
135
-
uint256 amount /** amount greater then old validator's stake */
136
-
) external;
137
-
```
138
-
139
-
In order to start a bid or bid higher on already running auction, this function is used. Auction period runs in cycles like `(auctionPeriod--dynasty)--(auctionPeriod--dynasty)--(auctionPeriod--dynasty)` so it *must check for correct auction period*.
140
-
141
-
`perceivedStakeFactor` is used to calculate exact $factor*old stake$ (note currently it is by default 1 WIP for picking the function). *Must check for auction from last auction period if any still going on* (one can choose to not call `confirmAuction` in order to get their capital out in the next auction). Normally continuous english auction is going on in a `auctionPeriod`.
142
-
143
-
### `confirmAuctionBid`
144
-
145
-
```solidity
146
-
function confirmAuctionBid(
147
-
uint256 validatorId,
148
-
uint256 heimdallFee, /** for new validator */
149
-
bool acceptDelegation,
150
-
bytes calldata signerPubkey
151
-
) external
152
-
```
153
-
154
-
-*Must check that this is not an auctionPeriod.*
155
-
- If last bidder is owner of `validatorId`, behavior should be similar to restake.
156
-
- In second case unstake `validatorId` and add new user as validator from next checkpoint, for the new user behavior should be similar to stake/stakeFor.
0 commit comments