NFT Registry - A meta transactional Non Fungible Token Registry

Description

The project is to implement a registry using an ERC1155 or ERC721 template from OpenZeppelin.

The registry should allow for the following:

• Allow user to register IPFS hash of some underlying document or folder as a new NFT.
• Allow user to register a “service” that has a name and points to a collection of NFTs and a single address of an EOA.
• Has an execute function similar to the one in ERC725X plus an additional argument which is the “service” name. This function checks that the tx it receives is signed by the EOA which is registered for the service and then makes the contract to contract call specified.

Configuration

Install Truffle cli

Skip if you have already installed.

npm install -g truffle

Install Dependencies

npm install

Test!💥

Run Tests

Launch Ganache then run:

npm run test

or test in truffle console

truffle(develop)> test
Using network 'develop'.


Compiling your contracts...
===========================
> Everything is up to date, there is nothing to compile.



  Contract: Registry
    Metadata
      √ should get name (172ms)
      √ should get symbol (136ms)
    Meta-transaction
      √ should verify signature (405ms)
      √ should revert when an invalid signer provided (681ms)
    Service
      register
        √ should register a service (378ms)
        √ should revert if the service exists already (841ms)
      unregister
        √ should unregister a service (762ms)
        √ should revert if the service doesn't exist (483ms)
        √ should revert when the signer has no permission (817ms)
    Token
      register
        √ should register a token (571ms)
        √ should register a token and add to a service (1136ms)
        √ should revert if the given service doesn't exist (406ms)
      unregister
        √ should unregister a token (1001ms)
        √ should revert if the token doesn't exist (564ms)
        √ should revert when the signer has no permission (735ms)
    Token-Service Relationship
      √ should use a token for a service (1326ms)
      √ should revert if the service doesn't exist (807ms)
      √ should unuse a token for a service (1809ms)
      √ should revert if the token doesn't exist (1040ms)
    execute
      √ should revert if the signer has no permission (1009ms)
      √ should revert if the unsupported operation requested (954ms)
      √ should external call (1067ms)


  22 passing (31s)