Seems that libp2p is closing the connection too early. needs fix coming with https://github.com/filecoin-project/go-fil-markets/issues/361
An issue has been raised that the message produced by lotus-miner actor set-addrs isn't being mined into blocks. This may cause issues as I believe it will halt any other message going through from the address. If anyone has been successful in using the command it would be good to know.
Currently I'm just seeing messages stack up in the mpool.
lotus mpool pending | jq -c '. | select(.Message.Method == 18 )' | wc -l
If you look at lotus-miner sectors status --log [sectorid] and see something like locked funds insufficient to cover initial pledges (... < NUMBER), then:
lotus send --method 14 --params-json '"NUMBER"' t0MinerID 0
Should fix that (edited)
junyao 15 days ago
Hi @Magik6k could you briefly explain what's going on with the lotus send command?
- what does the trailing '0' represent in the message
- How to make sure the miner has enough 'locked funds' ahead of time (instead of taking actions after we notice the error) (edited)
Magik6k 15 days ago
It invokes the AddLockedFunds method on the miner actor - https://github.com/filecoin-project/specs-actors/blob/master/actors/builtin/miner/miner_actor.go#L65
We need to fix things to do it automatically when you recover sectors
Describe the bug
I originally saw (in lotus code) and I read "period: 25", assuming that drand round is 25s.
Given our analysis there must be at least one drand entry per block (for the slow catchup mode to fully work). Having less than 1 drand per block allows miners to rush during catch-up on some epochs (e.g. if drand is 30 and lotus is 25, they can catch up every 5 blocks).
We do not have analysis that show that the impact of a single rush every few epochs is insecure nor that it insecure, however, we do know that one drand per round is secure.
Proposal 1: Change Filecoin blocktime: Set Filecoin block time to ≥30s
Proposal 2: Change Filecoin blocktime: Set Drand round time to ≤25s
Every SAFT purchaser will get his/her own individual actor (a.k.a. smart contract) that vests over the appropriate period. You can do two things with that actor:
Withdraw tokens that have vested
Change ownership of the actor using the SwapSigner method – this doesn’t let you withdraw more tokens, but it does let you transfer ownership of the actor to a new custodian or wallet.
If you choose to use a professional custodian (which we recommend for most people) rather than self-custody, CoinList will facilitate that for most purchasers. The custodian that CoinList will be working with by default will support SwapSigner , as will the self-custody wallet with Ledger support. Others may or may not – you should ask, and be aware that you might be stuck with the custodian if they don’t implement it.
There will be more instructions for SAFT purchasers via emails from Coinlist in the next few weeks!
每个SAFT购买者都将获得他/她自己的个人演员（也称为智能合约），在适当的时间内进行投资。你可以对那个演员做两件事： 收回已授予的代币 使用SwapSigner方法更改参与者的所有权-这不会让您提取更多的代币，但可以将参与者的所有权转移到新的保管人或钱包中。 如果您选择使用专业的保管人（我们建议大多数人使用）而不是自行保管，CoinList将为大多数购买者提供便利。CoinList将默认与之合作的托管人将支持SwapSigner，以及支持分类账的自助保管钱包。如果你不知道，他们可能会问你。 在接下来的几周里，Coinlist会给SAFT买家更多的指示！
We have other constructions in development, NSE and other options. They will be proposed as network upgrades through a FIP (Filecoin Improvement Proposal) after Mainnet launch. We hope to have at least one of these faster and cheaper constructions online within 6-12mo, but the development timeline depends on a lot of different constraints after mainnet launch. Note that new proofs will coexist with SDR, so a new cheaper proof will be optional to miners.
About NSE: NSE is one of the best candidates for a proof upgrade, and teams are working on implementation. But there are other candidates too, which are promising as well. It may be that another algorithm ends up better than NSE -- we don’t know yet. Proof upgrades will arrive after mainnet launch and will coexist.