profile
viewpoint
If you are wondering where the data of this site comes from, please visit https://api.github.com/users/johnchandlerburnham/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.
John Chandler Burnham johnchandlerburnham Yatima Inc Boston, MA agathic.com

johnchandlerburnham/hpfp 27

Exercises and Projects for Haskell Programming from First Principles by Allen & Moronuki

johnchandlerburnham/agnus 2

ecce agnus da

johnchandlerburnham/ctfp 1

Exercises for Category Theory for Programmers by Bartosz Milewski

johnchandlerburnham/dotfiles 1

NixOS, XMonad, termite, zsh, neovim, taffybar

johnchandlerburnham/AdventOfCode2019.fm 0

Advent of Code 2019 written in the Formality language https://github.com/moonad/formality

issue commentyatima-inc/bytecursor

remove sp-std dependency

I agree, and I think we can do this for much of, maybe all of, our sp-* library ecosystem

dignifiedquire

comment created time in 4 days

pull request commentyatima-inc/sp-multihash

add support for unsized multihashes

Sure, very comfortable with unsafe Rust. Are you thinking of casting/transmuting the newtypes?

Stebalien

comment created time in 4 days

pull request commentyatima-inc/sp-multihash

fix: correctly encode multihashes with serde

I'm pretty sure it should be encoded as a multihash, as per https://github.com/multiformats/multihash/issues/133

Stebalien

comment created time in 4 days

pull request commentyatima-inc/sp-multihash

fix: correctly encode multihashes with serde

Looking at the upstream issue, this makes sense to me, and resolves some of the confusion I had around truncation. Not 100% sure it's completely right either, but it seems more right than what exists currently, so in the interest of moving fast I've merged it.

Do the other multihash implementations do truncation correctly? Would be useful to compare if so

Stebalien

comment created time in 4 days

push eventyatima-inc/sp-multihash

Steven Allen

commit sha 2077805384eb8f19aa96fcbd4a2beaa9f806845e

fix: correctly encode multihashes with serde The number of digest bytes written needs to match the size. See the upstream issue here: https://github.com/multiformats/rust-multihash/pull/140 All credit goes to @koushiro. My one change is to not allocate.

view details

John Chandler Burnham

commit sha ca3f4766b9aa654b3adf5abe9ccfa0bd6a296a90

Merge pull request #7 from Stebalien/feat/enc-dec fix: correctly encode multihashes with serde

view details

push time in 4 days

PR merged yatima-inc/sp-multihash

fix: correctly encode multihashes with serde

The number of digest bytes written needs to match the size.

See the upstream issue here: https://github.com/multiformats/rust-multihash/pull/140

The one change is to not allocate.

+30 -10

2 comments

1 changed file

Stebalien

pr closed time in 4 days

issue commentmultiformats/rust-multihash

Merging work from yatima-inc/sp-multihash

Okay, it's sounding like we should focus on sending PRs for ByteCursor and Nix, and waiting on const-generics. We'll get to work on PRs for those two.

Given that sp-std is basically just a core/std switch, I see no reason not to depend on it.

To clarify the double negative, you mean we should depend on sp-std or we should not, and use core, alloc, etc directly instead?

Would it be possible to make ByteCursor implement the standard traits iff the "std" feature is enabled?

Doing the std::io traits in bytecursor itself is a good idea, I'll look into that.

johnchandlerburnham

comment created time in 5 days

issue openedyatima-inc/sp-multihash

`cargo test` requires --all-features

We should figure out what's not configuring correctly so that cargo test by itself will just work

~/sp-multihash main
❄ λ cargo test
   Compiling sp-multihash v0.2.0 (/home/john/sp-multihash)
error[E0432]: unresolved imports `sp_multihash::Sha1`, `sp_multihash::Sha1Digest`, `sp_multihash::Strobe256`, `sp_multihash::Strobe512`, `sp_multihash::StrobeDigest`
  --> tests/lib.rs:26:3
   |
26 |   Sha1,
   |   ^^^^ no `Sha1` in the root
27 |   Sha1Digest,
   |   ^^^^^^^^^^
   |   |
   |   no `Sha1Digest` in the root
   |   help: a similar name exists in the module: `Sha2Digest`
...
37 |   Strobe256,
   |   ^^^^^^^^^ no `Strobe256` in the root
38 |   Strobe512,
   |   ^^^^^^^^^ no `Strobe512` in the root
39 |   StrobeDigest,
   |   ^^^^^^^^^^^^ no `StrobeDigest` in the root

error[E0433]: failed to resolve: use of undeclared crate or module `rand`
 --> src/arb.rs:5:5
  |
5 | use rand::{
  |     ^^^^ use of undeclared crate or module `rand`

error[E0432]: unresolved import `quickcheck`
 --> src/arb.rs:1:5
  |
1 | use quickcheck::{
  |     ^^^^^^^^^^ use of undeclared crate or module `quickcheck`

error[E0432]: unresolved import `rand`
 --> src/arb.rs:5:5
  |
5 | use rand::{
  |     ^^^^ use of undeclared crate or module `rand`

error[E0433]: failed to resolve: use of undeclared type `WeightedIndex`
  --> src/arb.rs:21:16
   |
21 |     let dist = WeightedIndex::new(weights.iter()).unwrap();
   |                ^^^^^^^^^^^^^ use of undeclared type `WeightedIndex`

error: aborting due to 4 previous errors

Some errors have detailed explanations: E0432, E0433.
For more information about an error, try `rustc --explain E0432`.
error: could not compile `sp-multihash`

To learn more, run the command again with --verbose.
warning: build failed, waiting for other jobs to finish...
error[E0599]: no method named `write_all` found for struct `IdentityHasher` in the current scope
   --> tests/lib.rs:203:24
    |
203 |                   hasher.write_all(b"helloworld").unwrap();
    |                          ^^^^^^^^^ method not found in `IdentityHasher<32_usize>`
...
217 | /   assert_roundtrip!(
218 | |       Code::Identity, Identity256;
219 | |       Code::Sha1, Sha1;
220 | |       Code::Sha2_256, Sha2_256;
...   |
232 | |       Code::Blake3_256, Blake3_256;
233 | |   );
    | |____- in this macro invocation
    |
    = note: this error originates in the macro `assert_roundtrip` (in Nightly builds, run with -Z macro-backtrace for more info)

error[E0599]: no method named `write_all` found for struct `sp_multihash::Sha2_256` in the current scope
   --> tests/lib.rs:203:24
    |
203 |                   hasher.write_all(b"helloworld").unwrap();
    |                          ^^^^^^^^^ method not found in `sp_multihash::Sha2_256`
...
217 | /   assert_roundtrip!(
218 | |       Code::Identity, Identity256;
219 | |       Code::Sha1, Sha1;
220 | |       Code::Sha2_256, Sha2_256;
...   |
232 | |       Code::Blake3_256, Blake3_256;
233 | |   );
    | |____- in this macro invocation
    |
    = note: this error originates in the macro `assert_roundtrip` (in Nightly builds, run with -Z macro-backtrace for more info)

error[E0599]: no method named `write_all` found for struct `sp_multihash::Sha2_512` in the current scope
   --> tests/lib.rs:203:24
    |
203 |                   hasher.write_all(b"helloworld").unwrap();
    |                          ^^^^^^^^^ method not found in `sp_multihash::Sha2_512`
...
217 | /   assert_roundtrip!(
218 | |       Code::Identity, Identity256;
219 | |       Code::Sha1, Sha1;
220 | |       Code::Sha2_256, Sha2_256;
...   |
232 | |       Code::Blake3_256, Blake3_256;
233 | |   );
    | |____- in this macro invocation
    |
    = note: this error originates in the macro `assert_roundtrip` (in Nightly builds, run with -Z macro-backtrace for more info)

error[E0599]: no method named `write_all` found for struct `sp_multihash::Sha3_224` in the current scope
   --> tests/lib.rs:203:24
    |
203 |                   hasher.write_all(b"helloworld").unwrap();
    |                          ^^^^^^^^^ method not found in `sp_multihash::Sha3_224`
...
217 | /   assert_roundtrip!(
218 | |       Code::Identity, Identity256;
219 | |       Code::Sha1, Sha1;
220 | |       Code::Sha2_256, Sha2_256;
...   |
232 | |       Code::Blake3_256, Blake3_256;
233 | |   );
    | |____- in this macro invocation
    |
    = note: this error originates in the macro `assert_roundtrip` (in Nightly builds, run with -Z macro-backtrace for more info)

error[E0599]: no method named `write_all` found for struct `sp_multihash::Sha3_256` in the current scope
   --> tests/lib.rs:203:24
    |
203 |                   hasher.write_all(b"helloworld").unwrap();
    |                          ^^^^^^^^^ method not found in `sp_multihash::Sha3_256`
...
217 | /   assert_roundtrip!(
218 | |       Code::Identity, Identity256;
219 | |       Code::Sha1, Sha1;
220 | |       Code::Sha2_256, Sha2_256;
...   |
232 | |       Code::Blake3_256, Blake3_256;
233 | |   );
    | |____- in this macro invocation
    |
    = note: this error originates in the macro `assert_roundtrip` (in Nightly builds, run with -Z macro-backtrace for more info)

error[E0599]: no method named `write_all` found for struct `sp_multihash::Sha3_384` in the current scope
   --> tests/lib.rs:203:24
    |
203 |                   hasher.write_all(b"helloworld").unwrap();
    |                          ^^^^^^^^^ method not found in `sp_multihash::Sha3_384`
...
217 | /   assert_roundtrip!(
218 | |       Code::Identity, Identity256;
219 | |       Code::Sha1, Sha1;
220 | |       Code::Sha2_256, Sha2_256;
...   |
232 | |       Code::Blake3_256, Blake3_256;
233 | |   );
    | |____- in this macro invocation
    |
    = note: this error originates in the macro `assert_roundtrip` (in Nightly builds, run with -Z macro-backtrace for more info)

error[E0599]: no method named `write_all` found for struct `sp_multihash::Sha3_512` in the current scope
   --> tests/lib.rs:203:24
    |
203 |                   hasher.write_all(b"helloworld").unwrap();
    |                          ^^^^^^^^^ method not found in `sp_multihash::Sha3_512`
...
217 | /   assert_roundtrip!(
218 | |       Code::Identity, Identity256;
219 | |       Code::Sha1, Sha1;
220 | |       Code::Sha2_256, Sha2_256;
...   |
232 | |       Code::Blake3_256, Blake3_256;
233 | |   );
    | |____- in this macro invocation
    |
    = note: this error originates in the macro `assert_roundtrip` (in Nightly builds, run with -Z macro-backtrace for more info)

error[E0599]: no method named `write_all` found for struct `sp_multihash::Keccak224` in the current scope
   --> tests/lib.rs:203:24
    |
203 |                   hasher.write_all(b"helloworld").unwrap();
    |                          ^^^^^^^^^ method not found in `sp_multihash::Keccak224`
...
217 | /   assert_roundtrip!(
218 | |       Code::Identity, Identity256;
219 | |       Code::Sha1, Sha1;
220 | |       Code::Sha2_256, Sha2_256;
...   |
232 | |       Code::Blake3_256, Blake3_256;
233 | |   );
    | |____- in this macro invocation
    |
    = note: this error originates in the macro `assert_roundtrip` (in Nightly builds, run with -Z macro-backtrace for more info)

error[E0599]: no method named `write_all` found for struct `sp_multihash::Keccak256` in the current scope
   --> tests/lib.rs:203:24
    |
203 |                   hasher.write_all(b"helloworld").unwrap();
    |                          ^^^^^^^^^ method not found in `sp_multihash::Keccak256`
...
217 | /   assert_roundtrip!(
218 | |       Code::Identity, Identity256;
219 | |       Code::Sha1, Sha1;
220 | |       Code::Sha2_256, Sha2_256;
...   |
232 | |       Code::Blake3_256, Blake3_256;
233 | |   );
    | |____- in this macro invocation
    |
    = note: this error originates in the macro `assert_roundtrip` (in Nightly builds, run with -Z macro-backtrace for more info)

error[E0599]: no method named `write_all` found for struct `sp_multihash::Keccak384` in the current scope
   --> tests/lib.rs:203:24
    |
203 |                   hasher.write_all(b"helloworld").unwrap();
    |                          ^^^^^^^^^ method not found in `sp_multihash::Keccak384`
...
217 | /   assert_roundtrip!(
218 | |       Code::Identity, Identity256;
219 | |       Code::Sha1, Sha1;
220 | |       Code::Sha2_256, Sha2_256;
...   |
232 | |       Code::Blake3_256, Blake3_256;
233 | |   );
    | |____- in this macro invocation
    |
    = note: this error originates in the macro `assert_roundtrip` (in Nightly builds, run with -Z macro-backtrace for more info)

error[E0599]: no method named `write_all` found for struct `sp_multihash::Keccak512` in the current scope
   --> tests/lib.rs:203:24
    |
203 |                   hasher.write_all(b"helloworld").unwrap();
    |                          ^^^^^^^^^ method not found in `sp_multihash::Keccak512`
...
217 | /   assert_roundtrip!(
218 | |       Code::Identity, Identity256;
219 | |       Code::Sha1, Sha1;
220 | |       Code::Sha2_256, Sha2_256;
...   |
232 | |       Code::Blake3_256, Blake3_256;
233 | |   );
    | |____- in this macro invocation
    |
    = note: this error originates in the macro `assert_roundtrip` (in Nightly builds, run with -Z macro-backtrace for more info)

error[E0599]: no method named `write_all` found for struct `Blake2bHasher` in the current scope
   --> tests/lib.rs:203:24
    |
203 |                   hasher.write_all(b"helloworld").unwrap();
    |                          ^^^^^^^^^ method not found in `Blake2bHasher<64_usize>`
...
217 | /   assert_roundtrip!(
218 | |       Code::Identity, Identity256;
219 | |       Code::Sha1, Sha1;
220 | |       Code::Sha2_256, Sha2_256;
...   |
232 | |       Code::Blake3_256, Blake3_256;
233 | |   );
    | |____- in this macro invocation
    |
    = note: this error originates in the macro `assert_roundtrip` (in Nightly builds, run with -Z macro-backtrace for more info)

error[E0599]: no method named `write_all` found for struct `Blake2sHasher` in the current scope
   --> tests/lib.rs:203:24
    |
203 |                   hasher.write_all(b"helloworld").unwrap();
    |                          ^^^^^^^^^ method not found in `Blake2sHasher<32_usize>`
...
217 | /   assert_roundtrip!(
218 | |       Code::Identity, Identity256;
219 | |       Code::Sha1, Sha1;
220 | |       Code::Sha2_256, Sha2_256;
...   |
232 | |       Code::Blake3_256, Blake3_256;
233 | |   );
    | |____- in this macro invocation
    |
    = note: this error originates in the macro `assert_roundtrip` (in Nightly builds, run with -Z macro-backtrace for more info)

error[E0599]: no method named `write_all` found for struct `Blake3Hasher` in the current scope
   --> tests/lib.rs:203:24
    |
203 |                   hasher.write_all(b"helloworld").unwrap();
    |                          ^^^^^^^^^ method not found in `Blake3Hasher<32_usize>`
...
217 | /   assert_roundtrip!(
218 | |       Code::Identity, Identity256;
219 | |       Code::Sha1, Sha1;
220 | |       Code::Sha2_256, Sha2_256;
...   |
232 | |       Code::Blake3_256, Blake3_256;
233 | |   );
    | |____- in this macro invocation
    |
    = note: this error originates in the macro `assert_roundtrip` (in Nightly builds, run with -Z macro-backtrace for more info)

warning: unused import: `std::io::Write`
 --> tests/lib.rs:2:5
  |
2 | use std::io::Write;
  |     ^^^^^^^^^^^^^^
  |
  = note: `#[warn(unused_imports)]` on by default

error: aborting due to 15 previous errors; 1 warning emitted

Some errors have detailed explanations: E0432, E0599.
For more information about an error, try `rustc --explain E0432`.
error: build failed

created time in 5 days

issue commentyatima-inc/sp-cid

Unsized Cids

Oh, just realized what you meant by "variable-sized multihash", you mean like a variable-digest hash where the digest size isn't divisible by 8, right? E.g. a 100 bit Blake3 won't be distinguishable from a 104 bit Blake3 without the size field

Stebalien

comment created time in 5 days

issue commentyatima-inc/sp-cid

Unsized Cids

It's redundant when unsized, but I think we still need it when sized. Otherwise, it's difficult to construct variable-sized multihashes/cids.

Could you give me an example of a variable-sized multihash/cid where the size is actually used? Trying to see in what edge-cases where the digest length and the size would be different.

test issues

You need to do cargo test --all-features to turn on std in test. I'll see if I can fix this, and will add it to the README otherwise

#[derive(Copy)] seems to work. Am I missing something?

No, I just assumed the derive wouldn't work. Tried it now and it does though, which is nice.

names

I like DynCyn/DynMultihash, but I think

MultihashArrayBuf<S> fixed-sized.
MultihashBuf sized but allocated (like PathBuf).
Multihash unsized (like Path).T: ?Sized>

is worth a second look, since

 pub struct MultihashBuf {
    code: u64,
    size: u8,
    digest: Vec<u8>,
}

Seems like it might have some uses in some contexts.

rustfmt

This one?

Stebalien

comment created time in 5 days

issue openedmultiformats/rust-multihash

Merging work from yatima-inc/sp-multihash

Hi, I talked briefly to @Stebalien about merging some of the work from our https://github.com/yatima-inc/sp-multihash no_std fork. Happy to send PRs, but wanted to ask a few questions first:

  1. Const-Generics:sp-multihash is on rust 1.54-nightly, so we were able to adapt @mriise's excellent #116. It looks like you guys are waiting on https://github.com/rust-lang/rust/issues/44265 hitting stable Rust first before merging #116. To me, the usability regression reported in this comment seems acceptable compared to the usability gains from not having to drag typenums around everywhere. Plus, const-generics also opens up some really exciting refactoring possiblities, like @Stebalien's neat idea for using DSTs to erase the size-info here: https://github.com/yatima-inc/sp-cid/issues/5. Since waiting some weeks/months for stable GATs seems not ideal, I'm wondering if we can figure out some way around this:
  • Is the stable requirement an absolute for this lib? Or maybe we could make a "nightly" rust-multihash branch/release so that development here isn't impacted by rustc as much?
  • Alternatively, is there a way to make the above usability regression acceptable to you, using only stable const-generics?
  1. ByteCursor: Our no_std work removes std::io functions for reading/writing in favor of our bytecursor library. This can be added independently of Const-Generics.
  • Is the bytecursor dependency acceptable here? What about sp-std?
  • Do you want to keep the std::io, functions gated behind the std feature via pragmas? If so, should std still be default?
  1. Nix: We've added a Nix build to sp-multihash, and can PR (independently of the above) to add one here (preview: https://github.com/yatima-inc/rust-multihash/pull/1/files), if that's of interest.

created time in 5 days

issue commentyatima-inc/sp-cid

Unsized Cids

This looks like a an elegant way to have compile-time sizes and to erase that info when we don't want it.

It looks like we can even do:

#[derive(Debug, Clone, PartialEq, Eq, PartialOrd, Ord, Hash)]
#[doc(hidden)]
pub struct MultihashBase<T: ?Sized> {
  code: u64,
  size: u8,
  digest: T,
}

#[derive(Debug, Clone, PartialEq, Eq, PartialOrd, Ord, Hash)]
#[doc(hidden)]
pub struct CidBase<T: ?Sized> {
  version: Version,
  codec: Codec,
  hash: MultihashBase<T>,
}

impl<const S: usize> Copy for MultihashBase<[u8; S]> {}
impl<const S: usize> Copy for CidBase<[u8; S]> {}

And get Copy when we have known static sizes, which is pretty cool.

I wonder if as part of this we can also get rid of the size: u8 field on MultihashBase, since digest.len() should return the number of bytes in the digest.

So yes, definitely open to PRs on this!

Stebalien

comment created time in 5 days

pull request commentw3f/Grant-Milestone-Delivery

Yatima Milestone 3: sp-yatima

@mmagician We've just added an automated version of the integration test with docker here: https://github.com/yatima-inc/substrate-node-template/commit/41c504f56c83178c388f4515c07548c2e17f881b

johnchandlerburnham

comment created time in 10 days

startedyatima-inc/lean-blake3

started time in 11 days

pull request commentw3f/Grant-Milestone-Delivery

Yatima Milestone 3: sp-yatima

@mmagician Thanks for the fast feedback! We've fixed the formatting on the tutorial, and have rewritten it:

  1. While debugging the error you reported, we ran into some build issues from the recent changes to the substrate-developer-hub/substrate-node-template and substrate-developer-hub/substrate-front-end-template repositories. We now have simpler instructions to build from yatima-inc/substrate-node-template and yatima-inc/substrate-developer-hub/substrate-front-end-template directly.
  2. The previously linked bool.ya file was incorrect. We now link to a working sp-bool.yafile, as well as an sp-vector.ya to show proofs, and a bool-parse-error.ya and bool-type-error.ya to show errors. The issue was caused by a limitation on the on-chain parser that causes it to have to parse a slightly different file from the off-chain cli. Currently in order to be Substrate compatible we can only parse single file modules without dependencies, since the imports in the package preamble can trigger IO. This is a temporary measure since Yatima packages/modules are content-addressed and in future can be imported on-chain via an IPFS link, but this requires greater backend integration between Substrate and IPFS, such as via offchain::ipfs. (Another option is to create a package manifest file (analogous to a Cargo.toml) and upload that along with each package file, but this is logically equivalent to a single module, just with a different UI)

Let me know if this resolves the error you ran into, and if this is what you had in mind for an integration test. Happy to add more detail if needed.

johnchandlerburnham

comment created time in 12 days

push eventyatima-inc/yatima

Samuel Burnham

commit sha 4a2073554184a6527d10f1ec6d7669e5f7cc5ea9

Update substrate-tutorial.md (#133) * Update substrate-tutorial.md * Update substrate-tutorial.md

view details

push time in 12 days

push eventyatima-inc/substrate-node-template

John C. Burnham

commit sha 5427f6c6b09a6fbd5cfbf3bf65dca8139675fc8f

Update README

view details

push time in 12 days

push eventyatima-inc/substrate-node-template

John C. Burnham

commit sha 9cf1417b907d5c9fcc01816e8458dbc00b408071

tmp

view details

push time in 12 days

push eventyatima-inc/substrate-node-template

Shawn Tabrizi

commit sha 80c6e20723fc70ded7d33486d005ef8689adec13

Initial commit

view details

Shawn Tabrizi

commit sha 22fc4951909c9e612f0079fe992586aba981e5f1

Initial node-template

view details

Shawn Tabrizi

commit sha b6bfc95d7161eb0660d29497071eb8fffd18487b

Move node-template up a folder

view details

Ricardo Rius

commit sha 3abe9654b566c7ec89830a05354e3c8ee7340229

Add execute permission to rename script (#1)

view details

Shawn Tabrizi

commit sha cd271e0972b9b86ff0e6e6e0c21c3454485d4951

Update Node Template: 7d7e74fb7

view details

Shawn Tabrizi

commit sha 5cd3d42aeddb203f4f18aa6f64195df90e5edb07

Delete substrate-node-rename.sh

view details

Shawn Tabrizi

commit sha 09d2defac58e9b5bf3a6b5e0140605479b6ab6da

Revert "Update Node Template: 7d7e74fb7" This reverts commit cd271e0972b9b86ff0e6e6e0c21c3454485d4951.

view details

Shawn Tabrizi

commit sha 4e1734cccda339210372f08d7c6b02330025475f

Revert "Delete substrate-node-rename.sh" This reverts commit 5cd3d42aeddb203f4f18aa6f64195df90e5edb07.

view details

Shawn Tabrizi

commit sha ef3a59b007ad2589743628c3ed2abaf983b256c1

Delete substrate-node-rename.sh

view details

Shawn Tabrizi

commit sha 1434d54e29aaccca3b7b290cdacceddb80951ecd

Update to `3dedd246c62255ba6f9b777ecba318dfc2078d85`

view details

Shawn Tabrizi

commit sha 676186d7d80c1cd7c0a2599e52d457fc0aa6b6c7

Delete substrate-node-template.tar.gz In order to allow people to clone this template, GitHub requires all files be less than 10 mb.

view details

Shawn Tabrizi

commit sha 60675465c294255e77f264e8200d607305cf7c4c

Update to `d1cd01c74`

view details

Shawn Tabrizi

commit sha 20d08c295b0da01c0251c728963220ae27512449

Update README.md

view details

Shawn Tabrizi

commit sha 43ee95347b6626580b1d9d554c3c8b77dc85bc01

Merge pull request #6 from substrate-developer-hub/shawntabrizi-update-node-template Update to `d1cd01c74`

view details

Joshy Orndorff

commit sha 25c494b81d8392a3c140383f76e83016ff3985b2

Update to `d1cd01c7`

view details

Joshy Orndorff

commit sha 8fea1dc6dd0c5547117d022fd0d1bf49868ee548

Merge pull request #14 from substrate-developer-hub/joshy-update-d1c Update to `40a16ef`

view details

Ricardo Rius

commit sha 9e02251a9c5d4b40c5b2df05f057437c534a7a18

Update to 3e65111 (#18)

view details

Jimmy Chu

commit sha 1d6e830474290d3a1893a475aca305c1c65b5f03

readme update on generating your own node-template (#16) Added readme for generating your own substrate node template

view details

Jimmy Chu

commit sha 8b6fe6666d589486dd541663a32ffd98f2e21d74

Update README.md

view details

Joshy Orndorff

commit sha 7db81f928b53974978d22da2350b4826d95ccffc

Update node template to alpha.3

view details

push time in 12 days

push eventyatima-inc/yatima

John Chandler Burnham

commit sha 64d76a15fdc5caec5f85c5535d351c0ebe21a9c6

fix tutorial formatting (#132)

view details

push time in 12 days

PR merged yatima-inc/yatima

fix tutorial formatting
+4 -4

0 comment

1 changed file

johnchandlerburnham

pr closed time in 12 days

PR opened yatima-inc/yatima

fix tutorial formatting
+4 -4

0 comment

1 changed file

pr created time in 12 days

push eventyatima-inc/yatima

John C. Burnham

commit sha 5cba863e56147193e9bfd288d6abd9b81612999f

fix tutorial formatting

view details

push time in 12 days

create barnchyatima-inc/yatima

branch : jcb/doc-fix

created branch time in 12 days

push eventyatima-inc/Grant-Milestone-Delivery

John C. Burnham

commit sha 214e3bcb90dc721f761fb45290df4d92d93169a6

Yatima Milestone 3

view details

push time in 13 days

PR opened w3f/Grant-Milestone-Delivery

Yatima Milestone 3: sp-yatima

Milestone Delivery Checklist

Link to the application pull request: https://github.com/w3f/Grants-Program/pull/463

+23 -0

0 comment

1 changed file

pr created time in 13 days

push eventyatima-inc/Grant-Milestone-Delivery

Noc2

commit sha 60a43d83fc1dee0a210631139e4d5276f05690d0

udpate subscrypt 2

view details

Noc2

commit sha 655f3ddb9d975953fb279373db8cb3b727b483a0

Merge branch 'master' of https://github.com/w3f/Grant-Milestone-Delivery

view details

Noc2

commit sha ff654ce89d68598b2f755b622bc1b8651c09ce53

Subscrypt milestone 3

view details

Sebastian Müller

commit sha 55e627cfc437513ffd454eaec5d0af61a5f959cf

hs-web3 M4 accepted

view details

Aleksandr Krupenkin

commit sha 0c649b57b488176b008c21294745f6c185f89416

Added hs-web3 milestone 4 (#251)

view details

Aleixo Sánchez

commit sha f2725360c3b903191fdde830d83f1515dd59ea59

Update google_sheet_update.yml Fix matching pattern to parse application file URL in sheet action

view details

David Hawig

commit sha 437f244748f9f53701488419601b378d0296409d

Update subscrypt_3_Noc2.md

view details

Sebastian Müller

commit sha 656ee4c2d017ae3f8a0ad501bfc5f05f7e435178

NewOmega M4 in progress

view details

Sebastian Müller

commit sha 3f163095096f8793a39f50168a27298146e7c3a1

NewOmega M4 accepted

view details

celrisen

commit sha 3631d0442016a8b447e8f6d804a024507bc7221f

NewOmega M4 (#260) Co-authored-by: ¨Celrisen¨ <¨celrisen@gmail.com¨>

view details

Sebastian Müller

commit sha b579f563caf268dc58aa366bcd864852b182ad11

Canyon Network II M1 accepted

view details

Liu-Cheng Xu

commit sha 7e7de16947b9777aa2ebec814cd3bae05aa95bf1

Add canyon network phrase 2 (#258)

view details

Sebastian Müller

commit sha 81326e305d992cfc3ec49dd6cd56185e2c187d17

Polk-Auction M1 accepted

view details

Sebastian Müller

commit sha 4c4fc0cea012b0d307eaa2a4c52ec102b990151a

Merge branch 'master' of https://github.com/w3f/Grant-Milestone-Delivery

view details

Cyril Carlier

commit sha 77cf1138c324958f8c5c7504cc83725412775777

PolkAuction - milestone 1 (#259)

view details

Marcin

commit sha 3e973b253c6b4a9936b6992b1128d6fe45e87d0b

Evaluation of Yatima M2 (#268)

view details

Marcin Górny

commit sha 5913022572935af1f48fdf4277696fc7687dc811

Change Yatima M2 status to accepted

view details

John Chandler Burnham

commit sha 946c0514e0849d1ec5eefc650ccb48b01a369c3d

Yatima Milestone 2 (#256)

view details

S E R A Y A

commit sha 357e6c1fcb45bd235f23dadaeaae389efaf1e1c4

Openbrush milestone 2 Evaluation (#267) * added evaluation for openbrush * updated openbrush evaluation after unit tests were fixed * updated unit test section since they pass now * accepted openbrush milestone 2 Co-authored-by: Sebastian Müller <sebastian@web3.foundation> Co-authored-by: Seraya Takahashi <seraya.takahashi@swisscom.com> Co-authored-by: Sebastian Müller <sebastian@web3.foundation>

view details

Markian | Supercolony

commit sha 7f9b65bbc0bce3e5cee586f4fe325a3b5221f4aa

Openbrush milestone 2 delivery (#261) * Added delivery report for the first milestone * Added delivery report for the second milestone Co-authored-by: xgreenx <xgreenx9999@gmail.com>

view details

push time in 13 days

push eventyatima-inc/Grant-Milestone-Delivery

John C. Burnham

commit sha 85e7c39687cac3c289b2af95c166c07bf2163a5b

Yatima Milestone 3

view details

push time in 13 days

push eventyatima-inc/radiya

John C. Burnham

commit sha e4952c89015427db4958b4c2ee894c06cf0c60f6

unsigned varint, multihash, multibase encoding in Lean

view details

push time in 14 days