Home
Platform Principles

Three pillars that keep Fractinow honest

Not a marketing promise — these are the technical mechanisms you can verify yourself on every page of the application.

01

On-chain Transparency

Every dollar tracked, every unit verified.

Fractinow treats every contribution, unit transfer, and distribution as a public, auditable record. Funding flows, project status, and transaction history are displayed in a real-time activity timeline — not PDF reports generated on demand.

Contributions are created as pending records, then confirmed by an admin after payment is verified. No figures change silently: every increase in a project total and every unit transfer leaves a permanent trail in the Activity Feed.

The end goal is accountability without intermediaries: the community can independently verify where their money went and who holds which units.

  • Real-time activity timeline
  • Auditable contribution status
  • Permanent unit transfer trail

02

Collective Ownership

Assets once reserved for the few, now owned together.

Fractional ownership allows many people to hold ownership units in a single asset — from lakeside villas and productive land to community infrastructure. Each unit carries usage rights and the potential for revenue distributions as configured by the project.

Ownership is calculated from net holdings: contributions adjusted for secondary-market transfers. The Portfolio Dashboard accurately displays asset value, unit count, and distributions received.

The secondary market provides liquidity: unit holders can list units for sale, and new buyers can enter without waiting for a new project to open.

  • Fractional units & usage rights
  • Automatic net holdings
  • Secondary market liquidity

03

Security & RLS

Your data is yours alone — enforced at the database level.

Row-Level Security (RLS) ensures every user can only view and modify their own data. Contributions, portfolio, watchlist, and private notifications cannot be accessed by other users — not through a UI check, but enforced directly by the database engine.

Sensitive financial operations (payment confirmation, distributions, unit transfers) run through backend functions with service-role access and server-side validation. No financial figures are trusted from client input.

Admins have a separate role for moderation: approving projects, verifying KYC, and confirming payments. These access rights are also controlled via RLS, not merely hidden from the UI.

  • Per-entity RLS policies
  • Server-side financial validation
  • Separate admin role

See these principles in action

Browse active projects, check the activity timeline, or explore the secondary market.