profile
viewpoint
If you are wondering where the data of this site comes from, please visit https://api.github.com/users/ZenGround0/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.

ipfs/ipfs-cluster 938

Pinset orchestration for IPFS

drand/drand 348

🎲 A Distributed Randomness Beacon Daemon - Go implementation

filecoin-project/FIPs 88

The Filecoin Improvement Proposal repository

ipfs/go-ipfs-keystore 8

go-ipfs-keystore provides an interface and implementation of key storage for IPFS

therealyingtong/RollupNC 5

non-custodial exchange build with rollup

ZenGround0/ent 4

Herd filecoin state trees for upgrade migrations

shippy/wm4m 1

Watch me for me. Rails/Pebble mental health hack.

push eventprotocol/research

Jonathan Gross

commit sha 8e2c5a1b1d5fd81de9803df9138d35aab5ede96d

Update research-seminar-suggestion.md

view details

push time in an hour

pull request commentfilecoin-project/filecoin-ffi

don't require rustup

If you do this, you should check that rustc --version matches whatever is in https://github.com/filecoin-project/filecoin-ffi/blob/master/rust/rust-toolchain otherwise you will break the assumptions made. Rustup will use the version specified in that file, but if you use a system rust install that will not be the case, and things might start to break suddenly

coryschwartz

comment created time in 5 hours

Pull request review commentfilecoin-project/go-amt-ipld

fix(diff): handle edge case diffing empty against non-empty

 func Diff(ctx context.Context, prevBs, curBs cbor.IpldStore, prev, cur cid.Cid, 		height:   curAmt.height, 	} +	// edge case of diffing an empty AMT against non-empty+	if prevAmt.count == 0 && curAmt.count != 0 {+		return addAll(ctx, curCtx, curAmt.node,0)

unspaced ,, needs a go fmt

frrist

comment created time in 19 hours

pull request commentfilecoin-project/go-amt-ipld

fix(diff): handle edge case diffing empty against non-empty

Codecov Report

Merging #56 (f2b3529) into master (506754a) will increase coverage by 0.26%. The diff coverage is 100.00%.

Impacted file tree graph

@@            Coverage Diff             @@
##           master      #56      +/-   ##
==========================================
+ Coverage   65.75%   66.02%   +0.26%     
==========================================
  Files           6        6              
  Lines         514      518       +4     
==========================================
+ Hits          338      342       +4     
  Misses         93       93              
  Partials       83       83              
Impacted Files Coverage Δ
diff.go 66.84% <100.00%> (+0.71%) :arrow_up:

Continue to review full report at Codecov.

Legend - Click here to learn more Δ = absolute <relative> (impact), ø = not affected, ? = missing data Powered by Codecov. Last update 506754a...f2b3529. Read the comment docs.

frrist

comment created time in 19 hours

create barnchfilecoin-project/go-amt-ipld

branch : frrist/fix-empty-diff

created branch time in 19 hours

issue commentfilecoin-project/specs-actors

Actors v5 Plan

Items in this issue that didn't get completed are likely candidates for v6: https://github.com/filecoin-project/specs-actors/issues/1458

ZenGround0

comment created time in 21 hours

push eventfilecoin-project/FIPs

nemo

commit sha 16f00fb16068252ff723fbd8372dd16de14361a2

fix: add comm_rs to the aggregate/verify method signatures

view details

Jennifer

commit sha dc1a6248bab6e4b297775c93d680b0d91cc83f88

Merge pull request #115 from cryptonemo/fip13-api-update-2 fix: add comm_rs to the aggregate/verify method signatures

view details

push time in a day

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/specs-actors

Reconsider inline cids

We should definitely test this, but I'm a bit skeptical that this will help with sector infos, at least. Those are already inlined into the AMT and have no sub-fields that can be inlined.

However, we could probably save a bit of space by reducing the overhead of the AMT. But not much space, in this case.

ZenGround0

comment created time in a day

pull request commentfilecoin-project/specs-actors

Inline small blocks into CIDs.

@ZenGround0 a separate part of this discussion is blake2 => sha256, saving 2 bytes per cid. Not sure if worth another ticket, or too small of a saving.

Stebalien

comment created time in a day

pull request commentfilecoin-project/specs-actors

Inline small blocks into CIDs.

@ZenGround0 @anorth @Stebalien @arajasek in light of the chain scalability conversations - should this be reconsidered?

The change is disruptive, yes, but is also extremely easy technically and rather low-risk: we now have a very long history of successful chain format changes.

Stebalien

comment created time in a day

push eventfilecoin-project/network-info

Jennifer Wang

commit sha 56e2cc6b3780a15306239084a4acef2568f672ca

add filscout calib explorer

view details

push time in 4 days

push eventfilecoin-project/network-info

Jennifer Wang

commit sha 6b4db99ec3c8b0c427af94cb4da3c062d837471f

update the tag for calib

view details

push time in 4 days

push eventfilecoin-project/network-info

Jennifer Wang

commit sha 9fbe12620e874cb8df3393c463dd316d73d4a82a

Point the calib net base to the v1.10.0 release branch for now until the tag is available

view details

push time in 4 days

push eventfilecoin-project/network-info

Jennifer Wang

commit sha 8cf06fe406793b96b45977118500930ff56ccd6b

Update calib net

view details

push time in 4 days

created tagfilecoin-project/filecoin-ffi

tagd60fc680aa8abeaf

C and CGO bindings for Filecoin's Rust libraries

created time in 4 days

created tagfilecoin-project/filecoin-ffi

tag62b99ca01bce1787

C and CGO bindings for Filecoin's Rust libraries

created time in 4 days

PR merged filecoin-project/filecoin-ffi

Bump version

https://github.com/filecoin-project/lotus/pull/6524#issuecomment-863994056

+1 -1

0 comment

1 changed file

magik6k

pr closed time in 4 days

push eventfilecoin-project/filecoin-ffi

Łukasz Magiera

commit sha 62b99ca01bce1787f4934e41ec93b5dfc81f75a5

Bump version

view details

Łukasz Magiera

commit sha d60fc680aa8abeafba698f738fed5b94c9bda33d

Merge pull request #188 from filecoin-project/misc/proofs8.0.2-vers Bump version

view details

push time in 4 days

PR opened filecoin-project/filecoin-ffi

Bump version

https://github.com/filecoin-project/lotus/pull/6524#issuecomment-863994056

+1 -1

0 comment

1 changed file

pr created time in 4 days

create barnchfilecoin-project/filecoin-ffi

branch : misc/proofs8.0.2-vers

created branch time in 4 days

delete branch filecoin-project/filecoin-ffi

delete branch : agg-update

delete time in 4 days

created tagfilecoin-project/filecoin-ffi

tag6f11cdffd4f6c7ae

C and CGO bindings for Filecoin's Rust libraries

created time in 4 days

push eventfilecoin-project/filecoin-ffi

nemo

commit sha 70d1cc483f2aed4cba862c6fcc665830693b6747

fix: update proofs to latest for proper agg serialization format

view details

Łukasz Magiera

commit sha 6f11cdffd4f6c7ae1b05d0e47f578d4c9b21415f

Merge pull request #187 from filecoin-project/agg-update fix: update proofs to latest for proper agg serialization format

view details

push 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

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.

Also can be a great question for next weeks deep dive AMA!

anorth

comment created time in 5 days