Skip to main content
100%

Gist 24b18538d178e96bd03dca68ffa3edc2

✓ Published0🌍 Public
Aadamjanes
Last edited Oct 11, 2022
Created on Oct 11, 2022

This example shows a Solidity smart contract for minting and managing VerityNFT tokens, an ERC721-compliant NFT collection. The contract uses OpenZeppelin’s ERC721 and Ownable libraries to handle token ownership and administrative functions. It automatically mints three tokens to the deployer upon construction, tracks a global counter for token IDs, and stores file URIs associated with each token in a mapping. Users can add file references to tokens via `addFileToToken` and retrieve them with `getTokenFiles`, while the base URI for token metadata is set by the owner through `setBaseURI`.

AI-generated description

Similar vizzes

Loading thumbnail…

Gist 565d71987d2e83d17e094c9611c50bbf

This example shows the BearNBearToken smart contract, an ERC-721 non-fungible token implementation that manages a collection of 17,153 digital artworks. The Solidity code defines core NFT functionality including token ownership tracking, metadata storage for names and descriptions, and a tiered pricing system for minting, burning, and modifying token attributes. It uses OpenZeppelin’s SafeMath, Address, EnumerableSet, and EnumerableMap libraries to handle arithmetic operations and efficient owner-token lookups. The contract also incorporates a reward pool mechanism that distributes burn rewards across token holders, with provenance recorded via an IPFS hash.

Aamazingandyyy
71% match
Loading thumbnail…

Created using remix-ide: Realtime Ethereum Contract Compiler and Runtime. Load this file by pasting this gists URL or ID at https://remix.ethereum.org/#version=soljson-v0.4.24+commit.e67f0147.js&optimize=true&gist=

This visualization demonstrates the deployment and interaction of an ERC-20 token contract through the Remix IDE. It shows how the Solidity compiler and runtime environment handle real-time contract creation, allowing users to deploy and test token transfers, approvals, and balance queries. The code implements the EIP20Interface standard using Solidity’s pragma directive, with functions like `transfer`, `transferFrom`, and `approve` mapped to the Ethereum blockchain. The example relies on Remix’s web-based interface to compile the contract, highlighting the token’s initial supply, name, decimals, and symbol set in its constructor.

Aalex-milanov
61% match
Loading thumbnail…

Created using remix-ide: Realtime Ethereum Contract Compiler and Runtime. Load this file by pasting this gists URL or ID at https://remix.ethereum.org/#version=soljson-v0.4.24+commit.e67f0147.js&optimize=true&gist=

This example demonstrates a complete ERC-20 token contract, EIP20Interface, and its implementation, TheBestToken, in Solidity. It shows the standard token interface including functions for transferring tokens, checking balances, approving spending, and querying allowances, along with the Transfer and Approval events. The contract is compiled and deployed directly through Remix IDE, the browser-based Solidity compiler, using version 0.4.24 with optimization enabled. The code includes a constructor that initializes the total supply, token name, decimals, and symbol, and relies on Solidity’s built-in mapping and require statements for state management and validation.

Aalex-milanov
60% match
Loading thumbnail…

Generate queryable ownership records and transfer logs in any ERC721. This example is extending OpenZepplin functions. You can see the contract here https://mumbai.polygonscan.com/address/0xB837771546756D58d2EB79CDb0281Bc5F84bC704 and the owner logs here https://testnets.opensea.io/assets/mumbai/0x4b48841d4b32c4650e4abc117a03fe8b51f38f68/5969 and transfer logs here https://testnets.opensea.io/assets/mumbai/0x4b48841d4b32c4650e4abc117a03fe8b51f38f68/5970.

This example extends OpenZeppelin’s ERC721 contract to automatically generate queryable ownership records and transfer logs for any NFT. It uses the Tableland EVM SDK’s `ITablelandTables` and `TablelandDeployments` to create and update two SQL tables: one storing the current owner per token ID, and another recording each transfer’s timestamp, block, from, and to addresses. Every mint and transfer operation triggers a `runSQL` insert or upsert, making the full history visible on PolygonScan and OpenSea’s testnet interfaces.

Aandrewxhill
60% match
Loading thumbnail…

Gist 66a9908ada6981db682304b6f9bc6257

This example demonstrates a simple token transfer system on the Ethereum blockchain, showing how balances are updated between sender and receiver addresses. The Solidity contract defines a `MyCoins` token with an initial balance of 1,000,000 coins assigned to an owner, and the `tranferCoins` function checks that the sender has sufficient funds before deducting and adding amounts. The code uses a `mapping(address => uint)` data structure to store balances, with no external libraries or visualization APIs—it is purely a smart contract logic demonstration.

Aackuser
58% match
Loading thumbnail…

Gist 3478a3e5a0c6a4f52d4f41a3756647ed

This example renders a minimal Solidity smart contract named `HelloEthSalon` that stores a string message and exposes a `GetMessage()` function to return it. The contract uses the pragma directive `solidity ^0.4.4` and defines a constructor, though the visualization primarily displays the source code itself. No external visualization libraries or rendering APIs appear in the provided file; the focus is on the contract’s structure and syntax rather than graphical output. The data source is the embedded Solidity code, presented as a static text example.

Aamazingandyyy
55% match
Loading thumbnail…

Gist a3dd5d0e98ee18894491144540592304

This example displays a simple Ethereum smart contract written in Solidity 0.4.4. The contract, named `HelloEthSalon`, stores a hardcoded string message and exposes a `GetMessage()` function that returns it. The code demonstrates the basic structure of a Solidity contract, including a constructor and a public getter method. It does not use any visualization libraries or data sources, focusing solely on the contract's logic and syntax.

Aamazingandyyy
55% match
Loading thumbnail…

Gist 4b02d1558eb34ecad764c3ccf5289600

This example demonstrates a web interface for managing decentralized file storage on Filecoin, showing how users interact with a bridge API to store, deposit, release, and check the status of files. The code uses React hooks like `useState` and calls to a custom `api` object with methods such as `.store()`, `.addDeposit()`, `.releaseDeposit()`, and `.status()`, which handle file uploads, bridge deposits, fund releases, and deal status queries. Uploads are tracked in a state array, and responses include IPFS CIDs, while alerts and console warnings report errors or confirm actions. The visualization relies on the API's JSON responses rather than a rendering library.

Aandrewxhill
54% match