Tracking [Factomize-7] Core and General Development

Chappie

Factomize Bot
Pending
#1
This is your grant tracking thread. Below, you will find information from your original grant.

Grant Proposal
https://factomize.com/forums/threads/factomize-7-core-and-general-development.2285/

ANO / Committee
Group: Factomize
FCT address: FA3nsSjUy5uSkqMEug8t3VcehZn5w2ciSMpgqFEEsMRwMrHoa9k3
FCT: 8747

Total FCT Requested
8747

Start Date
2019-09-01

Completion Date
2019-11-30

Success Criteria
Contribute meaningfully to development of Core and other critical projects and provide at least one blog post per month.

Timelines and Milestones
This grant will cover development work from September 1st to November 30th.

Budget
We seek 8,747 FCT. If our ask was inline with last round, it would be 10,933 but Factomize has decided to internalize 20%.
 

Chappie

Factomize Bot
Secured
#2
@David Chapman @Factomize

Today is your grant start date! We look forward to regular updates from your team.

When you are ready for the final determination poll, first summarize the grant and self score then go to the thread tools dropdown at the top right and select "Create Final Determination Poll".
 
Secured
#3
I can confirm receipt of the FCT and will update the community every two weeks going forward.

Thank you to the community for funding this grant. We greatly appreciate it and will work hard to deliver value.

Each separate update will be added into this one.

Issues, PRs, and Other Work

https://github.com/pegnet/pegnet/pull/278
https://github.com/pegnet/LXRHash/pull/50 (WIP)
https://github.com/pegnet/pegnet/pull/279
https://github.com/Factom-Asset-Tokens/FAT/pull/32
https://github.com/pegnet/pegnet/issues/283
https://github.com/pegnet/pegnet/issues/284
https://github.com/pegnet/pegnet/issues/285
https://github.com/pegnet/pegnet/issues/286
https://github.com/pegnet/pegnet/issues/287
https://github.com/pegnet/pegnet/issues/288 + https://github.com/pegnet/pegnet/pull/289
https://github.com/pegnet/LXRHash/pull/51
https://github.com/Factom-Asset-Tokens/factom/pull/1
https://github.com/AdamSLevy/jsonrpc2/issues/1
https://github.com/Factom-Asset-Tokens/factom/issues/9
https://github.com/Factom-Asset-Tokens/fatd/pull/34
https://github.com/pegnet/pegnet/issues/310
https://github.com/pegnet/pegnet/pull/318
https://github.com/pegnet/pegnet/pull/319
https://github.com/Factom-Asset-Tokens/fatd/pull/40
https://github.com/pegnet/LXRHash/issues/54
https://github.com/pegnet/pegnet/issues/325
https://github.com/FactomProject/factom/pull/118
https://github.com/pegnet/pegnetd/issues/1
https://github.com/pegnet/pegnetd/pull/2 (related: https://github.com/pegnet/pegnetd/issues/3)
https://github.com/pegnet/pegnetd/issues/4
https://github.com/pegnet/pegnetd/issues/7
https://github.com/pegnet/pegnetd/pull/9
https://github.com/pegnet/pegnetd/pull/17
https://github.com/pegnet/pegnetd/pull/18
https://github.com/pegnet/pegnetd/pull/19
https://github.com/pegnet/pegnetd/issues/46
https://github.com/AdamSLevy/jsonrpc2/issues/3
https://github.com/pegnet/pegnetd/issues/47
https://github.com/pegnet/pegnetd/issues/48
https://github.com/pegnet/pegnetd/issues/49 (related https://github.com/Factom-Asset-Tokens/factom/issues/15) https://github.com/pegnet/pegnetd/pull/51
https://github.com/pegnet/pegnetd/issues/52
https://github.com/pegnet/LXRHash/issues/55
https://github.com/pegnet/LXRHash/issues/56
https://github.com/Factom-Asset-Tokens/fatd/pull/40
https://github.com/FactomProject/factom/issues/120
(PR for the above) https://github.com/FactomProject/factom/pull/121
https://github.com/FactomProject/factom/issues/117
https://github.com/FactomProject/factom/issues/119
(PR for the above) https://github.com/FactomProject/factom/pull/122
https://github.com/FactomProject/factomd/issues/893
(PR 1 for the above) https://github.com/FactomProject/factomd/pull/897
(PR 2 for the above) https://github.com/FactomProject/factom/pull/123
https://github.com/FactomProject/factomd/issues/784
(PR for the above) https://github.com/FactomProject/factomd/pull/898
(review of Michael Lam's PR) https://github.com/FactomProject/factomd/pull/901
https://github.com/FactomProject/factomd/pull/904
https://github.com/Factom-Asset-Tokens/factom/issues/16
(continued) https://github.com/pegnet/LXRHash/issues/55
https://github.com/pegnet/pegnetd/pull/66
https://github.com/pegnet/LXRHash/pull/59
https://github.com/FactomProject/factom-walletd/issues/79
https://github.com/pegnet/pegnetd/wiki/API#get-transaction-status
https://github.com/pegnet/pegnetd/wiki/API#get-transactions
https://github.com/pegnet/pegnetd/pull/68
https://github.com/pegnet/pegnetd/pull/69
https://github.com/FactomProject/factom/pull/130
(request only) https://github.com/pegnet/pegnetd/issues/70
https://github.com/pegnet/pegnetd/issues/71
https://github.com/pegnet/pegnet/issues/334
https://github.com/pegnet/pegnetd/pull/72#pullrequestreview-310807197
https://github.com/pegnet/LXRHash/pull/60
https://github.com/pegnet/pegnetd/pull/54
https://github.com/pegnet/pegnetd/pull/54
https://github.com/pegnet/pegnetd/pull/72
https://github.com/pegnet/pegnet/pull/335
https://github.com/pegnet/pegnetd/pull/65
https://github.com/pegnet/pegnetd/pull/73
https://github.com/pegnet/pegnetd/pull/74
https://github.com/pegnet/pegnet/issues/334
https://github.com/WhoSoup/factom-p2p/commits/develop
https://github.com/WhoSoup/factom-test-network/commits/master
https://github.com/WhoSoup/factom-p2p-testapp/commits/master
https://github.com/WhoSoup/factom-p2p-testapp/releases/tag/1.0

Blog Posts

PegNet Part Three: Conversions, Transactions, and more
How To Setup the PegNet Ecosystem for Conversions and Transfers
 
Last edited:
Secured
#8
Who went back to Core at the start of this two week period and had a couple PRs and made P2P2 progress but then it became apparent that PegNet was in vital need of API work for exchanges and wallets. As you'll see, Who has been very productive. The below has been merged into the first post.

Issues and PRs

https://github.com/FactomProject/factom/issues/120
(PR for the above) https://github.com/FactomProject/factom/pull/121
https://github.com/FactomProject/factom/issues/117
https://github.com/FactomProject/factom/issues/119
(PR for the above) https://github.com/FactomProject/factom/pull/122
https://github.com/FactomProject/factomd/issues/893
(PR 1 for the above) https://github.com/FactomProject/factomd/pull/897
(PR 2 for the above) https://github.com/FactomProject/factom/pull/123
https://github.com/FactomProject/factomd/issues/784
(PR for the above) https://github.com/FactomProject/factomd/pull/898
(review of Michael Lam's PR) https://github.com/FactomProject/factomd/pull/901
https://github.com/FactomProject/factomd/pull/904
https://github.com/Factom-Asset-Tokens/factom/issues/16
(continued) https://github.com/pegnet/LXRHash/issues/55
https://github.com/pegnet/pegnetd/pull/66
https://github.com/pegnet/LXRHash/pull/59
https://github.com/FactomProject/factom-walletd/issues/79
https://github.com/pegnet/pegnetd/wiki/API#get-transaction-status
https://github.com/pegnet/pegnetd/wiki/API#get-transactions
https://github.com/pegnet/pegnetd/pull/68
https://github.com/pegnet/pegnetd/pull/69
https://github.com/FactomProject/factom/pull/130
(request only) https://github.com/pegnet/pegnetd/issues/70
https://github.com/pegnet/pegnetd/issues/71
https://github.com/pegnet/pegnet/issues/334
 
Secured
#9
In the last two weeks, Who went back to work on P2P2 (and did other work below as you can see) which culminated in a test of P2P2 (thank you to all the testers!). The test went well and Who identified some areas of P2P2 that can be improved for the next test. I'm excited to say he also identified some behavior with the current P2P implementation (which we will call p2p1) that needs to change. In short, in p2p1, if the node itself or a peer wasn't able to keep up with bandwidth, it would just silently drop older messages without notifying anyone. In P2P2, Who drops newer messages with notifications. The surprise was just how quickly it happened in p2p1, so right now Who is working on a way that the node can detect when the node is struggling to send messages and slow down. This MAY be a TPS bottleneck but the reality is, it's really hard to say as there's no good way to measure what the actual bottleneck is. It's definitely a possibility though since it introduces the effect of a large number of lost packets if nodes can't keep up with the bandwidth.

The below are merged into the first post.

(PR review) https://github.com/pegnet/pegnetd/pull/72#pullrequestreview-310807197
(exploration) https://github.com/pegnet/LXRHash/pull/60
(PR review) https://github.com/pegnet/pegnetd/pull/54

Review and merge for pegnetd release:
https://github.com/pegnet/pegnetd/pull/54
https://github.com/pegnet/pegnetd/pull/72
https://github.com/pegnet/pegnet/pull/335
https://github.com/pegnet/pegnetd/pull/65
https://github.com/pegnet/pegnetd/pull/73
https://github.com/pegnet/pegnetd/pull/74
(update) https://github.com/pegnet/pegnet/issues/334

Work on P2P2 in branch:
Package: https://github.com/WhoSoup/factom-p2p/commits/develop
Simulation Network: https://github.com/WhoSoup/factom-test-network/commits/master
Public Test App: https://github.com/WhoSoup/factom-p2p-testapp/commits/master
Public Test App Release: https://github.com/WhoSoup/factom-p2p-testapp/releases/tag/1.0