npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2025 – Pkg Stats / Ryan Hefner

@story-protocol/protocol-periphery

v1.3.2

Published

Story Proof-of-Creativity protocol periphery smart contracts

Readme

Story Proof-of-Creativity Periphery

Version Documentation Website Discord Twitter Follow

Welcome to the Story PoC Periphery repository. This repository contains the peripheral smart contracts for the Story Proof-of-Creativity (PoC) Protocol. These contracts simplify developers’ work by allowing them to bundle multiple interactions with the PoC protocol - like registering an IP Asset and attaching License Terms to that IP Asset - into a single transaction.

For access to the core PoC contracts, please visit the protocol-core-v1 repository.

Documentation

📘 Learn more about Story

Story PoC Periphery combines multiple common independent interactions with the Story PoC Protocol into a single transaction. For example, this mintAndRegisterIpAndAttachPILTerms is one of the functions that allows you to mint an NFT, register it as an IP Asset, attach License Terms, and setting Licensing Configuration all in one call.

function mintAndRegisterIpAndAttachPILTerms(
  address spgNftContract,
  address recipient,
  WorkflowStructs.IPMetadata calldata ipMetadata,
  WorkflowStructs.LicenseTermsData[] calldata licenseTermsData,
  bool allowDuplicates
) external onlyCallerWithMinterRole(nftContract) returns (address ipId, uint256 tokenId, uint256 licenseTermsId)

Supported Workflows

For a list of currently supported workflows, check out the Workflows documentation.

Batching Calls

Batch calling functions is supported both natively and through the Multicall3 contract. For more information, check out the Multicall documentation.

Audit Reports

Audit reports are available in the ./audits directory.

Deployed Contracts

Version contracts are deployed on Story. The contract addresses can be found in deployment-1315.json (Story Aeneid Testnet) and deployment-1514.json (Story Homer Mainnet).

Quick Start

Prerequisites

Please install Foundry / Foundryup

Install dependencies

yarn # this installs packages
forge build # this builds

Verify upgrade storage layout (before scripts or tests)

forge clean
forge compile --build-info

Helper script to write an upgradeable contract with ERC7201

  1. Edit script/foundry/utils/upgrades/ERC7201Helper.s.sol
  2. Change string constant CONTRACT_NAME = "<the contract name>";
  3. Run the script to generate boilerplate code for storage handling and the namespace hash:
forge script script/utils/upgrades/ERC7201Helper.s.sol
  1. The log output is the boilerplate code, copy and paste in your contract

Testing

forge test -vvvv

Coverage

forge coverage

Working with a local network

Foundry comes with local network anvil baked in, and allows us to deploy to our local network for quick testing locally.

To start a local network run:

make anvil

This will spin up a local blockchain with a determined private key, so you can use the same private key each time.

Code Style

We employed solhint to check code style. To check code style with solhint run:

make lint

To re-format code with prettier run:

make format

Security

We use slither, a popular security framework from Trail of Bits. To use slither, you'll first need to install python and install slither.

Then, you can run:

make slither

And get your slither output.

Contributing

Please see our contribution guidelines.

Licensing

MIT License, details see: LICENSE.