Spore Meeting Agenda @ 2024-01-22

[ashuralyk]

Goal

[previous]

1. mainnet launch, see checklist Focus on Nervos DAO migration of CKB mainnet publish proposal from Nervos talk #6 (comment)
2. help Philosopher Stone successfully run for a couple of days
3. fix bugs in spore-demo (low priority)

talks:

• I plan to use the normal deployment method to upload Spore contracts which is not a ZERO lock and can be consumed potentially, is that ok for now? @Flouse @RongxinZhang

Previous Work

1. co-build integration within spore-contract and spore-sdk has been finished, see CI workflow here feat: add co-build integration in code base spore-contract#28

2. progress on spore-contract

   • fix a compatibility bug bug: fix compatibility within v1 and v2 spore-contract#50
   • complete test cases feat: complete test cases of cluster, proxy and agent contracts spore-contract#44
   • manage docs chore: update docs spore-contract#48
   • release tags v0.1.0 and v0.2.0

3. progress on spore-sdk

   • integrate co-build feat(sdk): cobuild basic support spore-sdk#68
   • remove minPayment argument from transfer ClusterProxy feat(sdk|docs): remove minPayment prop from transferClusterProxy spore-sdk#69
   • dump version to 0.2.0-beta.1 bump(sdk): 0.2.0 beta.1 spore-sdk#74

4. fix bugs in spore-graphql after the breaking change of spore-sdk

   • fix: remove direct dependencies on Spore config spore-graphql#3
   • fix: fixed getTopClusters was not return zero spore clusters spore-graphql#2

5. update dependencies in spore-demo and give some manual tests

   • collect issues from testing Issues related to the v2 version of spore-demo spore-demo#54 (comment)
   • fix bugs

Next Plan

1. carry out a more proper version management on spore-contract to eliminate further chaos
2. deploy spore-contract on mainnet
3. help Philosopher Stone complete its test

---

cc @RongxinZhang @Flouse @Dawn-githup @ShookLyngs

[ShookLyngs]

Done:

• spore-sdk
  • feat(sdk|docs): remove minPayment prop from transferClusterProxy spore-sdk#69
  • bump(sdk): 0.2.0-beta.0 spore-sdk#71
  • ref(sdk)!: replace v2 preview contracts and bump deps spore-sdk#73
  • bump(sdk): 0.2.0 beta.1 spore-sdk#74
  • chore(ci): add contents write permission to the release workflow spore-sdk#75
  • ref(sdk)!: replace v2 contracts with v1-compatible version spore-sdk#76
• spore-demo
  • refactor: use in-app config spore-demo#57
  • refactor: upgrade spore-sdk to 0.2.0-beta.1 spore-demo#59
  • fix: reported issues spore-demo#61
  • bump: upgrade omnilock's dep info in lumos config spore-demo#63
• spore-graphql
  • refactor: move spore-sdk as a peer dependency spore-graphql#4

Next:

• Test spore-sdk#76 and publish a new version
• Review spore-graphql code, if nothing more, publish a new version

[Flouse]

• I plan to use the normal deployment method to upload Spore contracts which is not a ZERO lock and can be consumed potentially, is that ok for now? @Flouse @RongxinZhang

The capsule build --release cmd of spore-contract is a reproducible build solution.
So, technically, anyone can deploy a special version of code with the same code_hash on CKB chain.

This also means you can make a deployment with ZERO lock at any time when you think it's the right time.

Related Suggestions

1. Clearer disclosure of deployment information

   Update the deployment info in spore-contract repo's README or RFC, including:

   • network (CKB testnet or mainnet)
   • spore-contract's version tag or commit
   • contract_name
   • code_hash
   • hash_type
   • tx_hash
   • index
   • dep_type

2. add docs in README: explain that reproducible build is supported to verify the deploy scripts/contracts

References

• https://github.com/nervosnetwork/rfcs/blob/master/rfcs/0025-simple-udt/0025-simple-udt.md#notes

[ashuralyk]

Update the deployment info in spore-contract repo's README or RFC

after things go well, I'll update these information in README.md and docs/VERSIONS.md

[Dawn-githup]

Done:

1. Conduct usability testing on spore-demo based on the latest spore-contract.Write e2e test for spore-demo #8 (comment)
2. Add spore_v1 contract feat:Add spore_v1 contract spore-devenv#4
3. spore demo/spore graphql problem repair verification fix: reported issues spore-demo#61 (comment)

Next:

1. spore-demo problem fix verification https://github.com/sporeprotocol/spore-demo/issues/created_by/Dawn-githup
2. Verification based on new version of spore-graphql Issues related to the v2 version of spore-demo spore-demo#54 (comment)

[anipenguin]

Done:

• Linked to X@sporeprotocol on the official website spore.pro. Add X(twitter) on website spore-site#24

Next:

• Update the tutorial to reflect the changes with the SDK.
• Prepare relevant tweets and announcements for when the launch date is confirmed.

[ashuralyk]

Update the tutorial to reflect the changes with the SDK

how do you know these changes in SDK?

[anipenguin]

it would be based on the updates to https://github.com/sporeprotocol/spore-blog-tutorial with help from the engineer

[ashuralyk]

Progress of Scrum

1. mainnet deployment complete
2. spore-sdk adapted mainnet deployment
3. Philosopher Stone is about to switch to mainnet network
4. team breaking changed