nspcc-dev / nspcc-dev/neofs-node
Smart `IR` -> `SN` GAS transfers
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 38
- Forks
- 51
- Avg merge
- 1d 20h
- Merged PRs (30d)
- 38
Description
After #873 there is rude notary deposit logic: SN checks its notary and GAS balances and tries to keep 1:3 GAS to Notary balance proportion with GAS/2 OR 1 deposits.
But it could not be always good, e.g. for tests, it is common practice to set epoch to 20 blocks in dev-env, but IR sends GAS to SN only once in 300 blocks(it does not depends on epoch duration), so SN runs out of GAS(not notary balance) with the time.
Questions
- How often/much should
IRsend GAS toSN? - Should it depend on
netmapsize/SN's balances? - Should
SNchange its deposit logic?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading issue #873 and tracing the IR-to-SN GAS transfer and SN deposit logic described here. Compare the behavior with short development epochs and the stated balance ratio. Done requires a decided transfer cadence or amount, any netmap or balance dependency, and a decision on whether SN's deposit policy changes, supported by tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- blockchain, distributed-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100