profile
viewpoint
If you are wondering where the data of this site comes from, please visit https://api.github.com/users/jennijuju/events. GitMemory does not store any data, but only uses NGINX to cache data for a period of time. The idea behind GitMemory is simply to give users a better reading experience.

filecoin-project/rust-fil-proofs 330

Proofs for Filecoin in Rust

filecoin-project/community-china 184

Resources and forum for the Chinese community, maintained and moderated by CoinSummer & PL.

filecoin-project/community 171

Filecoin community and ecosystem channels, discussion forums, and more

filecoin-project/FIPs 88

The Filecoin Improvement Proposal repository

filecoin-project/venus-docs 31

Content for go-filecoin tutorial

filecoin-project/benchmarks 27

A place for community-submitted Filecoin benchmarks

ethers-io/ethers-aion 6

An Aion-flavored version of ethers.js.

filecoin-project/tpm 3

Technical Project Management: Meeting notes and agenda items

release bloxbean/intelliada

v0.1.0

released time in 5 hours

pull request commentfilecoin-project/FIPs

fix: add comm_rs to the aggregate/verify method signatures

This PR is required to update the API signatures after the finalized SnarkPack audit. The comm r's are now required in the aggregation calls, and they were previously missing.

cryptonemo

comment created time in a day

issue commentfilecoin-project/community

A well-known open source project is missing FIL

Tagging @momack2 @arajasek to evaluate and triage.

forjdk

comment created time in 4 days

issue closedfilecoin-project/community

create and bridge IRC channels to matrix/slack

IRC channels will help us get in touch with a significant portion of our community that really prefers to use IRC over Matrix and Slack. We currently have several chat channels created in Matrix. We chose Matrix because it uses a decentralized, p2p protocol, and channels can be encrypted end-to-end. Matrix also makes it easy to integrate with other chat services.

Currently, we have bridged our Matrix channels to Slack. We want our core channels (listed below) to be bridged to IRC as well.

This issue requires two main steps:

  1. Create IRC channels for:
  • fil-dev
  • fil-proofs
  • fil-chat
  • fil-mining
  • fil-devex-docs
  1. Then, bridge these IRC channels to our Matrix channels (which the Slack channels are also bridged to).

closed time in 4 days

pooja

issue commentfilecoin-project/community

create and bridge IRC channels to matrix/slack

Closing this issue. If there is community interest, please comment on this issue and we will re-open.

pooja

comment created time in 4 days

issue closedfilecoin-project/community

Watch discuss.filecoin.io or drive people away from it.

The official discussion forum about Filecoin, which is featured in the Readme of this very repo, is ghosted by the Filecoin team.

There re several different occurrences of people complaining having no answer after a long time, and a lot of unanswered posts even though there are not many posts (maybe for that very reason).

I think the Filecoin team should at least publish a post explaining that most of the fun happens on Matrix, Slack, etc. The link to the forum should be removed from the Readme, or the team should watch it carefully.

The forum as it is makes it look to new comers like Filecoin is a dead project (which it is everything but, of course).

Just a thought.

closed time in 4 days

bertrandfalguiere

issue commentfilecoin-project/community

Watch discuss.filecoin.io or drive people away from it.

@bertrandfalguiere We've finally migrated the Filecoin discussion forum to https://github.com/filecoin-project/community/discussions, and redirected the old URL. Your nudge was much appreciated - thank you.

bertrandfalguiere

comment created time in 4 days

PR opened filecoin-project/community

Add deep links to Showcase instructions

Add more detailed links & instructions to add your project to community showcase.

+2 -7

0 comment

1 changed file

pr created time in 4 days

create barnchfilecoin-project/community

branch : mishmosh-patch-1

created branch time in 4 days

issue commentfilecoin-project/FIPs

Add the EVM and other VMs to Filecoin

+1, but I want to ask, if smart contracts are added, does it mean that it has the same functions as Ethereum? Is there a bit too much opponent? After all, there are too many public chains competing with Ethereum, such as Polkadot, near, Binance, Huobi, etc. Can they catch up? And if smart contracts are added, will the economic model of fil tokens also change?

jbenet

comment created time in 4 days

issue commentfilecoin-project/FIPs

Add a batched PreCommitSectors method

@stuberman this is an implementation concern so your question will be best addressed by filing an issue with the implementation you are using (sounds like https://github.com/filecoin-project/lotus is the right place)

anorth

comment created time in 5 days

issue commentfilecoin-project/FIPs

Add a batched PreCommitSectors method

It is not clear to me whether the pre commit batch affects sealing. While precommit commit messages are waiting for release (expiration of "PreCommitBatchWait") are those sectors held from further processing/sealing? As an example is PreCommitBatchWait = 8 hours will PC2 sectors queue up on sealing disks until the timer expires? If so, miners will need to be advised to set the wait timer low enough to not run out of disk capacity and cause worker to idle waiting for timer to expire.

anorth

comment created time in 5 days

issue openedfilecoin-project/tpm

Filecoin Core Devs Meeting 21 Agenda

Filecoin Core Devs Meeting 21 Agenda

Agenda

created time in 5 days

issue closedfilecoin-project/tpm

Filecoin Core Devs Meeting 20 Agenda

Filecoin Core Devs Meeting 20 Agenda

Agenda

closed time in 5 days

arajasek

issue openedfilecoin-project/tpm

Meeting notes for 0020

Filecoin Core Devs Meeting #20 - 2021-06-17

  • Meeting Date/Time: Thursday June 17 2021, 16:00 UTC
  • Meeting Recording:
  • Attendance: Forest (Chainsafe), Fuhon (Soramitsu), Lotus (PL), Venus (IPFSForce), Filecoin Foundation and Community representatives

Lotus:

  • We did some fixes on the bugs we found, which were solved.
  • Calibration net is now used for testing, we found 1 proofs issues which was fixed
  • RC5 is our the latest release, seems pretty stable for us.
  • Miners are adopting and testing the codebase, everything seems good so far.
  • Generated test vectors, we have auto-generated test vectors to run against codebase - https://github.com/filecoin-project/specs-actors/tree/master/test-vectors#readme

Forest:

  • Fixing on bugs we found in the audit, that was the. biggest priority for us in the past week
  • Working on Proofs libraries + FIP updates for the V5 Actors version
  • Working on dashboard to get more insight - Grafana updates are there
  • We are working on user documentation for our first release

Fuhon:

  • We have great news - we were able to solve memory leak issues, everything seems normal in testing phase for us.
  • We are running test and will let it run for the next week, to make sure everything is right
  • Next up is the security audit for us, we will contact someone from the foundation to help out
  • We have refactored our API, which was linked with our memory leak issue. All good on this front.

Venus:

  • In the last two weeks, we have successfully integrated Actors V5. Calibration also works for us.
  • We completed our initial version of our first component - Gateway which will allow users to access in an easier way.
  • We are working on improvements to our Github repo, including our FAQ section. We will use this to explain to small miners how to connect to our service. Repo Link: https://venus.filecoin.io/Overview.html
  • In the next 2 weeks we will on the new network version upgrade, to make sure it’s successful + work on items which are found in our audit report, to have a final version.

Filecoin Foundation:

Community:

  • We need to talk about how we include community in planning for next releases
  • Developer portal - we are trying to build will need review from this group in order to improve it and get the best potential UX for users

V5 Actors and V13 Network upgrade -updates and simulation findings

  • Hyperdrive simulations are run in the last 2 weeks: We created a simulated blockchain where we did window posts and other operations in order to try to predict what will happen after we launch.
  • State tree grows 1.7GB per day, which is really a lot and more than we expected. From this, we can project how big the snapshots will be. We are looking at the massive growth in size after 6 months, looking at the end of this year.
  • We have ideas on how we can tackle this and will discuss ideas in the weeks to come. For now, we are just moving ahead with releases, knowing that we will need to deal with this in the future.

For now, we stay on the path to deliver hyperdrive v13 for faster network growth, like we originally planned.

created time in 5 days

PR opened filecoin-project/tpm

Create Meeting 0020
+60 -0

0 comment

2 changed files

pr created time in 5 days

issue openedfilecoin-project/FIPs

FIP Proposal: Upgrade regular deal to verified deal

Simple Summary

Allow miner to send an upgraded verified deal after the piece data has been sealed and sector has been landed on chain.

Abstract

Today if client/miner wants to take advantage of Filecoin Plus program, the process is client send DataCap request to notary, with supplemental in formations provided, notary approve the request and assign DataCap to the client, then client start the deal process by sending proposal(s) with VerifiedDeal field marked "true", and miner go through the rest of deal process steps, while being part of Filecoin Plus, miners enjoy the higher quality adjusted power and clients enjoy lower storage price, a de factor binding has been imposed between filecoin plus onboarding process and deal-seal process by making successful onboarding process as the pre-condition before deal-seal

This proposal is aiming to break this de factor dependency without changing or compromising the Filecoin Plus Client Onboarding process, but just wants to introduce an additional deal upgrade message to be allowed to submit to the chain to either 1, make the previous regular deal to be an "verified deal" or 2, To supplement deal information related to a CC sector which sealed piece data with meaningful content

Change Motivation

1, Given the benefit of Filecoin Plus to both clients and miners, clients might tend to apply for DataCap before store their data in the chain, and DataCap approval process normally take days even weeks, and it's possible that eventually only partial or even no DataCap is granted, therefore it could be a barrier or a delay factor for clients to land their data in the network. Decouple Filecoin Plus and propose deal will encourage client to store their data in Filecoin first and apply DataCap in parallel or later.

2, Although the network storage power is over 6EiB, majority of it is Committed Capacity with zero data in it. Miners are not intended to use existing "CC upgrade" to make it a sector with deals because of no extra economic motivation, given the "post verification" mechanism in place, expect deals might be increasing sharply and it could be economic efficient to leverage existing committed capacity with zero piece by CC upgrade, therefore the overall piece data size parentage could be increased w.r.t overall network storage power. (For reference, in date of Jun 4, In the total 768062 precommit message, only 2 were "ReplaceCapcity" )

3, For CC sectors with non zero data piece (assume to implement in FIP "Pack arbitrary data in CC sectors and be able to upgrade them to verified data later"), no re-seal will be needed to upgrade the CC sector to a "deal sector"

Design Rationale

Two scenario will need to be considered in design: 1, New "Upgrade deal" proposal needs to be defined with verified field to be true, and new "UpggadeStorageDeal" needs to be added to the Market Actor, to link the existing original deal to the sector already committed to the network, and update the quality adjusted power. 2, With another FIP "Pack arbitrary data in CC sectors and be able to upgrade them to verified data later" implemented, a complemented proposal need to be defined to the CC sector, and a "ComplemntStorageDeal" needs to be added to the Market Actor to link the complement deal to the existed CC sector.

Backwards Compatibility

There will be no impact to the existing sectors/deals committed to the chain

Security Considerations

Seal process will keep as it is, there will be no chance to bring sectors to the network in faster manner by this proposal. The DataCap approval process will not be no change (or even be strengthen for notary to retrieve the piece data before grant the DataCap), therefore there will be no shortcut for clients/miners to bring more quality adjusted power nonauthentic way.

Incentive Considerations

1, Encourage client to bring more business data to the network without waiting for DataCap proving process 2, Encourage miner to leverage CC upgrade more often 3, For "CC sectors with data piece", no re-seal needed for CC upgrade.

created time in 7 days

push eventfilecoin-project/tpm

Aayush Rajasekaran

commit sha d0b183842474e8a3cbf3c5c12e16a153e6cd3ba4

Create Meeting 0019

view details

push time in 7 days

PR merged filecoin-project/tpm

Create Meeting 0019

Absorbs the notes from #44

+60 -0

0 comment

2 changed files

arajasek

pr closed time in 7 days

issue commentfilecoin-project/FIPs

FIP Proposal: Client can make an off-chain deal and miner can use CC sectors to storage data without resealing

Another cool side of the proposal - is that the described unsealed/off-chain data can be regular IPLD formatted data and thus retrievable from IPFS. This could be an additional solution for Filecoin/IPFS interoperability issue and even implement remote pinning API for miners. For a variety of cases, off-chain deals would give enough guarantees about data being stored.

Also, it looks similar to optimistic rollup schema, but in this case, this can be called an 'optimistic storage deal'. That is, the deal is optimistically stored off-chain as IPLD data in the CC sector, which can be (1) upgraded to an on-chain deal and (2) disputed in the case it's not stored anymore(verification procedure?).

andrewzhao87

comment created time in 11 days

pull request commentfilecoin-project/FIPs

fix: add comm_rs to the aggregate/verify method signatures

Related to https://github.com/filecoin-project/rust-fil-proofs/pull/1470

cryptonemo

comment created time in 12 days

issue commentfilecoin-project/FIPs

FIP Proposal: Client can make an off-chain deal and miner can use CC sectors to storage data without resealing

Exciting, so great to read this idea!

(@lucanizzardo and I were about to post a proposal to try to solve the same problem).

andrewzhao87

comment created time in 13 days

issue commentfilecoin-project/FIPs

FIP proposal: A more secure signature method of worker&post account

I think I'm getting your point now. The short version is: you want special "limited" accounts that can only:

  1. Pay for gas (cannot pay send funds).
  2. Ideally only sends specific kinds of messages to specific addresses.

This is doable in theory but would require adding some potentially complex logic to the filecoin message validation step. This can't be implemented as a simple smart contract.

This would reduce the incentive for stealing these keys. But do note that:

  1. A key used for window posts can still be used to cost the miner funds by submitting invalid window posts (which can later be disputed).
  2. A key used for pre-commits can be used to make known-bad pre-commits, costing the pre-commit deposit.
  3. A malicious miner could pay themselves a high premium using these keys.
  4. An attacker could simply burn all the gas in these keys.
arsadmin

comment created time in 13 days

PR opened filecoin-project/network-info

update to 1.9.0

updated the commit and the release tag for the latest stable v12 lotus release tag

if i missed something - please let me know

+2 -2

0 comment

1 changed file

pr created time in 13 days

issue commentfilecoin-project/FIPs

Add the EVM and other VMs to Filecoin

+1. Would love to see full smart contract capabilities in Filecoin.

jbenet

comment created time in 13 days

issue openedfilecoin-project/FIPs

FIP Proposal: Client can make an off-chain deal and miner can use CC sectors to storage data without resealing

Simple Summary

Client can make an off-chain deal to miner. The miner will use existing or new CC sector to storage client's real data. If client want its off-chain data on chain, miner should upgrade the CC sectors to Regular Sectors with resealing.

Problem

Right now, the total network power is more than 6EiB,but the real storage is just only 15PB(https://storage.filecoin.io/). There are a lot of CC sectors with the zero deal. The miner should have an easy way to use the existing CC sectors to store the real data from the clients, no more resealing. So that it can solve the problem about the idle hardware equipment.

The currently method is that the pledged sector can be replaced with a new sector containing deals.(https://docs.filecoin.io/mine/lotus/sector-pledging/#upgrading-pledged-sectors). However, it requires the deal to publish and new sector to seal. It will take up more resources of the miners and also occupy more resources of the network. Client storage costs will also increase because of it.

Proposed Solution

The client can choose whether to publish its own data and deal on chain or not.

  • If the client make the on chain deal, the miner can store it in a new sector or upgrade the CC sector by 'mark-for-upgrade'.
  • If the client make the off chain deal, there are not publishStorageDeals message, sealing and dealID etc. The client's data will be stored in the CC sector of the miner. At the same time, miners need to save DealCid and PieceCID. SectorPreCommitInfo also needs to be changed or add some data fields. (we also see some similar proposals at #57 #89)

Storing the off-chain data will save the gas fee, which is so expensive when the base fee is high especially. Like Verified data, the miners can provide the client another lower storage price than on-chain mode. The clients also can download files from the miner by the file CID.

If the client needs, it can change its off-chain deal on chain. The miner will migrate the data into the regular sector.

Especially, when the client finds that the miner do not provide services any more, it can create an arbitration or appeal. If the miner lost the data, the miner needs to pay the customer compensation for the loss of data. Meanwhile, the power and pledge will also be slashed. (Perhaps we can discuss another FIP in detail)

created time in 13 days

issue commentfilecoin-project/FIPs

FIP proposal: A more secure signature method of worker&post account

@Stebalien Thank you for your reply. As you mentioned I update that what I really want to say is the control key that can be more secure.

In our practical mining, usually we have two control keys. One is used to provide the gas fee when Sealing the sectors (messages linke PreCommitSector and ProveCommitSector), we usually call it gas address. The other one is used to provide the gas fee when doing the PoSt (messages like SubWindowedPoSt), we usually call it PoSt address.

So these two control keys need to have enough FILs to provide the gas fee. Once the miner was attacked by hackers and the control keys were stolen, The miner will suffer great loss of asserts.

So as mentioned above, when the control account send FILs during PreCommitSecotor\ProveCommitSector\SubWindowedPoSt and so on, just Single signature like now, it's OK. we call these working transfer.

But if the control account want to send FILs directly to someone else with no working messages(like PreCommit\ProveCommitSector\SubWindowedPoSt). These kind of transferring need to use Multi signature.

So even the control keys were stolen, they can't get the FILs in the account.

if there is any doubt, please feel free to let me know.

arsadmin

comment created time in 13 days

issue commentfilecoin-project/FIPs

Add the EVM and other VMs to Filecoin

There are many folks looking at this, and I hear many people want to build this before the end of 2021. I would love to see this happen, and would be very supportive of such a FIP.

jbenet

comment created time in 14 days