Split audit tasks inside audit contract #9

New issue

Closed

opened 2025-12-28 18:08:13 +00:00 by sami · 2 comments

sami commented

2025-12-28 18:08:13 +00:00

Owner

Originally created by @alexvanin on GitHub (Dec 21, 2020).

Right now inner ring nodes split all available containers to perform audit autonomously by getting giant container list from container contract (see #29). Later if audit contract will store audit complexity values per container, inner ring node will do more work asking one more contract to split the tasks.

Instead we can offload it to audit contract. Let it iterate through all containers and pick suitable ones for inner ring node. To do so we need:

add endpoint to container contract that returns storage.Context,
calculate position of inner ring node inside inner ring list in audit contract,
go through storage context with storage.Find in audit contract and return suitable containers.

Originally created by @alexvanin on GitHub (Dec 21, 2020). Right now inner ring nodes split all available containers to perform audit autonomously by getting giant container list from container contract (see #29). Later if audit contract will store audit complexity values per container, inner ring node will do more work asking one more contract to split the tasks. Instead we can offload it to audit contract. Let it iterate through all containers and pick suitable ones for inner ring node. To do so we need: - add endpoint to container contract that returns `storage.Context`, - calculate position of inner ring node inside inner ring list in audit contract, - go through storage context with `storage.Find` in audit contract and return suitable containers.

sami

2025-12-28 18:08:13 +00:00

closed this issue
added the
enhancement

container

audit

U4

S2

I3
labels

sami commented

2025-12-28 18:08:13 +00:00

Author

Owner

@alexvanin commented on GitHub (Sep 9, 2021):

It should be useful in multiimplementation environment, where it's hard synchronize new audit selection policy. It will be easier to update contract than update multiple Inner Ring implementations.

@alexvanin commented on GitHub (Sep 9, 2021): It should be useful in multiimplementation environment, where it's hard synchronize new audit selection policy. It will be easier to update contract than update multiple Inner Ring implementations.

sami commented

2025-12-28 18:08:14 +00:00

Author

Owner

@roman-khimov commented on GitHub (Jul 9, 2025):

No audit — no problem. #499

@roman-khimov commented on GitHub (Jul 9, 2025): No audit — no problem. #499