🎙️

Jacky Wang

Jacky Wang developed DxChain Network’s public blockchain focusing on storage service. He built mainnet deployment, light client implementation, watchdog monitoring, DPOS consensus, and storage contract. Jacky holds a Physics bachelor’s from Fudan University and an Electrical and Computer Engineering master’s from University of Arizona.

Jacky enjoys writing beautiful and clean code. In leisure time, he spends time singing Chinese pop karaoke, hiking Lake Chabot twice a week, and watching drama movies like “Three Billboards”.

Upcoming Plans

  • Monthly Deliverables: 2021 Oct
    • Keep testing stream sync protocol. Fix bugs and problems and (hopefully) deploy to testnet for further test.
    • Code design, review and local test of liquidity staking in core protocol.
    • White paper, pitch deck, and demo for NFT^2 project.
  • Quarterly Milestones: 2021 Q4
    • Have stream sync protocol tested and deployed to Mainnet.
    • Product full design and implementation for Harmony liquidity staking.
    • Product testnet launch for Harmony liquidity staking.
  • Yearly Planning: 2022 Q1 - Q3
    • Product launch for NFT^2 project
    • Product launch for Harmony liquidity staking
    • Resharding

Achievements in 2021 Q2-Q3

  • Optimize and fix for spamming attacks from p2p network
  • Optimize and migrate explorer db performance
  • RPC performance optimization and fix

2021/1/17

  1. 20 hours spent on mainnet stuck issue
    1. RPC rate limiter:
    2. Proposing, testing Rate limiter
  2. 8 hours on stream sync
  3. 2 hours on migrating rate limiter parameter to harmony config.

2021/1/10

  1. 25 hours used for node-status issue.
    1. , , , , ,
    2. The issue is introduced by , and expose the data race issue at caching the sync results.
    3. Another issue exposed is the result returned when no DNS server return any result is wrong (true instead of false)
  2. State Sync
    1. 4 hours for deploying the downloader code to stressnet. https://watchdog.hmny.io/report-stn
    2. 8 hours for debugging, code changes
    3. One bug discovered from deploying is that there is no “memory” in discover. Thus if there are no valid streams, client node will keep discovering without and cooldown. So a cooldown mechanism is required in discover. Keep implementing.

2021/12/13~2021/12/19

2021/12/13

  1. 3 hours for devops maintenance
    1. Write report
    2. Extending storages
    3. Stuck nodes
    4. Error analysis (sync loop stuck)
  2. 3 hours for prometheus issue for rpc2.
    1. Legacy problem from
    2. rpc2 prometheus metrics not counted correctly

2021/12/14

  1. 1 hour for downloader CPU increasing issue.
    1. Restarted testing instances (probe node)
    2. Code analysis
    3. Updates on code, and redeploy
    4. Still large number of connection setup / broke. Problem is not resolved by last fix.
  2. 5 hours for prometheus rpc2 ()
    1. Added timeout mechanism at rpc at util layer.
    2. Added the timeout to harmony config with config layer
    3. Added prometheus metrics to web socket traffics.
    4. Trying to fix rpc2 metrics not showing issue. Failed with another implementation. Keep seeking.

2021/12/15

  1. 2 hours for downloader CPU issue.
    1. Observe no difference.
    2. Changed discover mechanism to see difference.

2021/12/16

  1. 1 hour for downloader CPU issue.
    1. Discover does not have large relation with CPU usage.
    2. CPU still fine (45% ) wait for one day more to check again.
  2. 2 hour to research prometheus issue
  3. 3 hour to implement the rate limiter for stream sync
    1. Implementation on-going

2021/12/17

  1. 1 hour for downloader CPU issue
    1. CPU bursted.
    2. Comment out code and retry
  2. 2.5 hours for Implementing test cases for rate limiter
  3. 1 hour to research into prometheus issue. (no findings)
  4. 3.5 hours for mainnet sync stuck issue
    1. Pulled logs.
    2. Analyzed code.
    3. Looks like consensus cache race issue. Multiple threads calling UpdateBlockAndStatus function.

2021/12/18

  1. 1 hour for prometheus issue.

2021/10/26

  1. Continue debugging for stream sync.
    1. The previous found suspect do impact CPU (very occasionally), but it is still not the root cause. The nodes dies after 3 days' running...
    2. The next suspect is... still the discovery protocol... Keep researching
  2. Research for design for liquidity staking
    1. Looked into the implementation of Lido, StaFi, and bLuna.
    2. Lido and StaFi almost use the same implementation. The final derivative token is a token with increasing intrinsic value (in unit of deposit token), which is not the perfect candidate for DeFi products because of Impermanent loss
    3. Starting to talk to Lido / StaFi team.
  3. Core protocol change for liquidity staking
    1. Discuss, track, and help with core protocol change for staking precompiles.
    2. Code review for https://github.com/harmony-one/harmony/pull/3906 (Finished two rounds, third round in progress)

2021/10/19

  1. Continue working on stream sync. Found a suspect for CPU explosion
    1. The problem lies in two peers sending out the INIT package in two end's streaming protocol because of the immediate discovery after stream number is lower than lower threshold. And this will fail the stream setup and result in a large number of discovery and stream setup operations (which is heavy)
    2. Have reproduced the issue in two nodes in different regions resulting in high CPU cost (which is a hipe, not a slow growth).
    3. Starting with the fix - Adding a cooldown mechanism in discovery and stream manager.
  2. Proceed with liquidity staking
    1. Code review and discussion with xiaopeng
    2. Discussed over signature of the precompiles, as well as the gas issue.

2021/10/08

  1. Working on stream sync. First looking at the potential memory / CPU leak. Running two machines running customized code on mainnet with stream sync turned on. The customized code include:
    1. Frequent discovery call (10s/discovery).
    2. Unstable stream sync protocol (injected error in stream sync, occasionally fail)
    3. The result remains to be observed.

  2. Finished code revisit and RPC fix concerning stream sync.
  3. Next step is to
    1. Investigate the CPU / memory leak
    2. Spin up stressnet for reproducing the stucking short range sync.