Skip to content

Collection Registry Filtering / Patch #216

Description

@NickJ202

Collection Registry ID: TFWDmf8a3_nw43GCm_CuYlYoylHAjCcFGbgHfDaGcsg

Before adding patch to the collection registry process, we should add in a mechanism which removes collections that are inactive. One good method to use to identify active collections is to check the amount of stamps that they have, as well as the amount of activity on the collection assets themselves.

Inside the registry process, there should be a new handler added which when called, identifies collections in the process which should be removed. Ideally we can utilize cron to run this task at a specific interval.

The handler should pass the collection IDs to the stamp process (LaC2VtxqGekpRPuJh-TkI_ByAqCS2_KB3YuhMJ5yBtc) and then remove any collections which have none. An additional metric to use could be to determine how much activity (orders) have taken place in the collection as an additional weight for determining which collections should remain in the process.

Note: A staging process for testing should first be created with a snapshot of the production registry.

Once this feature is released in the registry, there should be patch messages added to each handler which updates state in the process, as well as an initial patch message sent on the initial load of the process.

Metadata

Metadata

Assignees

Labels

Type

No type

Fields

No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions