refactor(examples): secp256k1 transfer example

[IronLu233]

Description

The origin secp256k1 transfer example is too hard to understand. because it builds up the transaction mannually. In current lumos version, we have commons.common.transfer method, which can manipulate the raw transaction's inputs/outputs. Thus, it's a time for reactoring it. And I add a new feature, which allows developer can transfer CKB to mulitple addresses

Type of change

[x] other

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Updated
lumos-website	✅ Ready (Inspect)	Visit Preview	Sep 16, 2022 at 3:43AM (UTC)

[codecov]

Codecov Report

Merging #388 (579677f) into develop (f244d81) will increase coverage by 0.18%.
The diff coverage is n/a.

@@             Coverage Diff             @@
##           develop     #388      +/-   ##
===========================================
+ Coverage    81.94%   82.13%   +0.18%     
===========================================
  Files           93       94       +1     
  Lines        19003    19269     +266     
  Branches      1785     1820      +35     
===========================================
+ Hits         15572    15826     +254     
- Misses        3390     3401      +11     
- Partials        41       42       +1     

Impacted Files	Coverage Δ
packages/ckb-indexer/src/services.ts	47.47% <0.00%> (-1.49%)	⬇️
packages/codec/src/high-order/nested.ts	99.17% <0.00%> (-0.83%)	⬇️
packages/ckb-indexer/src/type.ts	100.00% <0.00%> (ø)
packages/ckb-indexer/src/index.ts	100.00% <0.00%> (ø)
packages/ckb-indexer/src/paramsFormatter.ts	92.30% <0.00%> (ø)
packages/codec/src/error.ts	94.64% <0.00%> (ø)
packages/ckb-indexer/src/resultFormatter.ts	95.83% <0.00%> (+0.08%)	⬆️
packages/codec/src/number/uint.ts	99.23% <0.00%> (+0.10%)	⬆️
packages/codec/src/molecule/layout.ts	99.74% <0.00%> (+0.65%)	⬆️
packages/helpers/src/index.ts	86.63% <0.00%> (+0.91%)	⬆️
... and 3 more

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update f244d81...579677f. Read the comment docs.

[homura]

can you please upgrade the example to [email protected]? checkout the migration guide

[homura]

IMO, as an example, it should be linear, procedural. Modular for engineering but not for viewing, especially for a web app like GitHub, which would require more memory if I had to jump between multiple methods.

Can you please refactor transfer into a method

function transfer(options: {
  recipients: Array<{address: Address, capacity: BIish}>,
  senderPrivkey: BytesLike
}): Promise<Hash> {
  // step 1 - convert a privkey to an lock(address)

  // step 2 - caculate the total capacity to be transferred

  // step 3 - call common.transfer to generate a txSkeleton

  // step 4 - pay tx fee

  // step 5 - prepare signing entries

  // step 6 - seal the transaction

  // step 7 - broadcast the transfer tx
}

[IronLu233]

However, we need show the transaction fee. So we have to split the whole transfer into differient part.