Skip to content

Instantly share code, notes, and snippets.

View gist:149e46c136dd1d6f374699f650cbfe48
### Keybase proof
I hereby claim:
* I am j01tz on github.
* I am joltz (https://keybase.io/joltz) on keybase.
* I have a public key ASCxnw-8k9yh2KDGJdG-k7xKjzZk_N4T1TfT5PoMwQvKGgo
To claim this, I am signing this object:
View gist:a221e50ea301dd866701c1cd84be2b51
20190926 14:21:47.959 DEBUG grin_servers::common::hooks - Received block header 0000035c00a8 at 364606 from 68.183.14.16:3414, going to process.
20190926 14:21:47.960 DEBUG grin_chain::txhashset::txhashset - Rewind header extension to 000012d20521 at 364605 from 000012d20521 at 364605
20190926 14:21:47.966 DEBUG grin_servers::common::hooks - Received block header 0000035c00a8 at 364606 from 70.50.33.130:3414, going to process.
20190926 14:21:47.971 DEBUG grin_chain::pipe - header_head updated to 0000035c00a8 at 364606
20190926 14:21:47.974 DEBUG grin_p2p::peer - Requesting compact block 0000035c00a8 from 68.183.14.16:3414
20190926 14:21:47.974 DEBUG grin_p2p::peer - Requesting compact block 0000035c00a8 from 70.50.33.130:3414
20190926 14:21:48.069 DEBUG grin_servers::common::hooks - Received block header 0000035c00a8 at 364606 from 85.187.253.59:49316, going to process.
20190926 14:21:48.070 DEBUG grin_p2p::peer - Requesting compact block 0000035c00a8 from 85.187.253.59:49316
20190926 14:21:48.092 DEBUG grin_
View grin_tui_freeze.log
20190926 10:25:21.253 INFO grin_servers::grin::sync::syncer - sync: total_difficulty 1108226330053722, peer_difficulty 1108242348055466, threshold 13220556610 (last 5 blocks), enabling sync
20190926 10:25:21.253 DEBUG grin_servers::grin::sync::header_sync - sync: initial transition to HeaderSync. sync_head: 0000089c6854 at 364246, resetting to: 000000330936 at 364371
20190926 10:25:21.267 DEBUG grin_chain::txhashset::txhashset - Rewind header extension to 0000089c6854 at 364246 from 000000330936 at 364371
20190926 10:25:21.295 DEBUG grin_chain::types - sync_state: sync_status: NoSync -> HeaderSync { current_height: 364371, highest_height: 364377 }
20190926 10:25:22.495 DEBUG grin_servers::grin::sync::header_sync - sync: locator : [(364371, 000000330936), (364369, 000000f6fb46), (364365, 00000259057f), (364357, 0000225f70d3), (364341, 00000128fd46), (364309, 00000143efe4), (364245, 0000234c9a17), (364117, 000002a29810), (363861, 00000e9bea8d), (363349, 000001483656), (362325, 00000056728a), (360277, 00001af95f
View grin-rfc-process-0000.md
  • Feature Name: rfc_process
  • Start Date: TBD
  • RFC PR: TBD
  • Grin-PM Issue: TBD

Summary

The "RFC" (request for comments) process is intended to provide a consistent and controlled path for new features to enter the Grin codebase and governance structure, so that all stakeholders can be confident about the direction the project is evolving in.

View grin-rfc-readme.md

Grin RFCs - Active RFC List

This process attempts to emulate the success of the Rust programming language and as such has almost mirrored the RFC process the Rust developers use, which is tried and tested and appears to work very well. This document is currently a work in progress. It will be adjusted as needed before sharing with the wider community. If you are reading this please leave your feedback!

View grin-rfc-template.md

Summary

One paragraph explanation of the feature.