OpenViSTAI · Agents · Blockchain · Crypto
Submit a project
Menu
Smart Contracts

Decentralized Star Notary

Decentralized Star Notary is a Solidity ERC-721 learning project that represents stars as digital assets. It includes a smart contract, unit tests, and a basic UI intended to register stars and retrieve them by token ID, alongside examples of token ownership, transfers, sales, purchases, and exchanges.

Explore the practical guide ↓

Independent OpenViST project profile, based on linked sources.

Decentralized Star Notary — OpenViST project profile in Smart Contracts.
OpenViST project illustration. See the linked sources for product details.
Understand the project

Practical overview

When it fits

Use it as a learning reference for an ERC-721 star registry or as a starting point for adapting a collectible demo, while accounting for its documented permissive functions and dependency mismatch.

Who it is for

  • Developers learning Solidity and ERC-721 contract patterns.
  • Readers studying token ownership, approvals, transfers, or test coverage.
  • Builders exploring a simple tokenized-collectible registry as a code starting point.

Documented uses

  • Register a star asset and retrieve it using its token ID through the basic UI.
  • Study contract functions for token creation, existence, ownership, sale, purchase, transfer, and exchange.
  • Review unit tests for minting, approvals, ownership, transfers, and buying and selling.
Before you choose

Requirements & limits

The source is a public GitHub repository identified as MIT-licensed; it is not described as a hosted application.

  • The project separates the Solidity contract from a basic UI for registering and retrieving assets by token ID.
  • The README describes unit tests for token metadata, registration, ownership, approvals, transfers, and sale-and-purchase behavior.
  • Minting is unrestricted and any address can call exchangeStars, according to the README; the project identifies these as learning-demo simplifications.
  • The README says the pinned compiler and resolved OpenZeppelin versions are incompatible, so the project will not compile as committed; it proposes alternative version pairings.
  • The README's suggested local workflow uses Truffle and Ganache CLI.

Check current requirements in the official documentation. Source-based guidance does not mean OpenViST has run or independently tested this project.

Source-based practical guide

Set up the local project dependencies

Install the project dependencies from the repository before attempting local development.

Before you start

  • A checkout of the repository
  • npm

Steps

  1. Change into the repository directory, then into smart_contracts.

  2. Run npm install to install the project dependencies; Electron is also downloaded and installed.

Expected outcome

Project dependencies are installed for local development.

Guide limitations

  • The README documents a compiler and OpenZeppelin version mismatch; the project will not compile as committed. Dependency installation alone does not resolve that mismatch.
Documentation 1 ↗
Evidence and transparency

Sources & review

Official repository ↗
Source record details
Source availability
Active
Sources checked
9 October 2026
Original website title
alpersonalwebsite/erc721-smart-contract · Official homepage title · retained in its source language
How we review sourcesSuggest a correction