Announcements regarding our community
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!
A place to talk about whatever you want
Seems that libp2p is closing the connection too early. needs fix coming with https://github.com/filecoin-project/go-fil-markets/issues/361
Comments & Feedback（讨论反馈）
Got a question? Ask away!
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
Blog posts from individual members
Both the Proof of Replication and Proof of Spacetime processes in Filecoin use zk-SNARKs for compression.
zk-SNARKs stands for "Zero-Knowledge Succinct Non-Interactive Arguments of Knowledge." You can think of them as hashes of computations. They let us prove that a proof has been done correctly without having to reveal the details of the proof itself or the underlying data on which it's based.
The process of creating Filecoin's zk-SNARKs is computationally expensive (slow), but the resulting end product is small and the verification process is very fast. Compared to the original proofs, zk-SNARKs are tiny, making them efficient to store in a blockchain. For example, a proof that would have taken up hundreds of kilobytes on the Filecoin chain can be compressed to just 192 bytes using a zk-SNARK.
As mentioned previously, everyone running a Filecoin node maintains an up-to-date version of the chain for verification purposes. Keeping each proof small with the assistance of zk-SNARKs minimizes the storage demands placed on each node in the Filecoin network, as well as the length of time it takes to verify a transaction.