Skip to main content
100%

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.

✓ Published0🌍 Public
Aandrewxhill
Last edited May 4, 2023
Created on May 4, 2023

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.

AI-generated description

Similar vizzes

Loading thumbnail…

Gist 24b18538d178e96bd03dca68ffa3edc2

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`.

Aadamjanes
60% match
Loading thumbnail…

Tableland game workshop

Tableland game workshop demonstrates a live blockchain game state managed through Tableland tables, displaying player positions and interactions on a dynamic map. The React app uses the Tableland SDK to query and update rows in real time, with smart contracts deployed on Arbitrum Goerli handling game logic. It integrates w3link for decentralized content storage and references an NFT minting dapp starter, while the visualization renders through React components styled with CSS, pulling data directly from on-chain table reads via ethers.js.

Aandrewxhill
55% match
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
53% 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
53% match
Loading thumbnail…

Create a table to store changes from any of your tables in a log table.

This example demonstrates a SQL-based version-control system for geospatial data in a CartoDB database. It shows how to create a log table that stores changes from any tracked table, capturing insertions, updates, and deletions with full row data as JSON. The code uses PostgreSQL PL/pgSQL triggers and functions, along with the `row_to_json` and `json_populate_record` functions to serialize and reconstruct records. A trigger on a user-specified table invokes the logging function, storing the geometry, operation type, source ID, and table name in the `version_control` table.

Aandrewxhill
51% 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
51% match
Loading thumbnail…

Uses midpointapi.com to return a single cell value from any table or sql request on Tableland

This example demonstrates how a Solidity smart contract can use the Midpoint API to retrieve a single cell value from any Tableland table or SQL query. The contract wraps the user’s SQL query into a `SELECT ... LIMIT 1` statement and sends it to the Midpoint contract via `callMidpoint`, then handles the asynchronous string response through a callback interface. It uses OpenZeppelin’s `Strings` and `EnumerableMap` libraries to manage request IDs and callback addresses, emitting events for each request and received response. The code shows both a basic query without a callback and a version that routes the response to a user-specified contract implementing `IStringCallback`.

Aandrewxhill
50% match
Loading thumbnail…

Gist 089185f271fafa370b0d50975f91c3b5

This example demonstrates how to deploy two smart contracts, `Migrations` and `HelloEthSalon`, onto an Ethereum blockchain using the Truffle framework. The code defines a migration script that exports a function receiving a `deployer` object, then calls `deployer.deploy()` sequentially for each contract artifact loaded via `artifacts.require`. It shows the standard deployment workflow for initializing migration tracking and a custom contract in a single step. The data source is the contract artifacts and the rendering approach is the command-line deployment process itself.

Aamazingandyyy
49% match