Does kubus Node mirror private data?
No. It is scoped to public archive records and does not mirror private user data.
Public & street art
How does kubus Node work?
kubus Node works as an availability node for public archive replication. It mirrors public cultural records, reports liveness and can create pending contribution records for verified availability. It does not mirror private user data, control wallets or create live payouts.
Public archive replication
The node is scoped to public archive records such as artwork metadata, public media references and public AR assets when available. Private user data, drafts, wallet backups and admin records stay outside the replication boundary.
Liveness and checks
An availability node can report liveness, archive coverage and retrieval checks. These signals help show whether public records remain reachable across infrastructure.
Pending contribution records
Verified availability can create pending contribution records. These are not live payouts, investment returns or financial promises. Future settlement would need separate, explicit infrastructure.
Open operator tooling
The runtime is published on GitHub so operators can inspect the tooling. It should be described as cultural infrastructure for public data availability, not as a wallet or trading product.
Frequently asked questions
Are node rewards live payouts?
No. They are pending contribution records until future settlement infrastructure exists.
Does the node control my wallet?
No. kubus Node is not a wallet and does not control settlement funds.
Where is the code?
The kubus Node runtime is published on GitHub at https://github.com/kubus-project/kubus-node.
Editorial and expertise transparency
This page is maintained by the art.kubus editorial team using public-source research, local context, and community-verified map contributions.
Editorial and research team: art.kubus editorial team