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 🙏

© 2024 – Pkg Stats / Ryan Hefner

@windingtree/videre-contracts

v2.1.0

Published

🔧 Videre Engine Smart Contracts

Downloads

82

Readme


author: mfw78 [email protected]

Videre Engine Smart Contract

Overview

Videre is a collection of contracts that allows for implementation of real-world service marketplaces. Components of the contracts include:

  • Registries
  • Escrow
  • Industry-specific logic

For more information, please see the docs.

Usage

First configure a .env file. You can copy .env.template to .env and change the defaults. You MUST specify a MNEMONIC.

To compile and run a hardhat test node with the contract deployment:

yarn #installs packages
yarn hardhat node

Tests

Test contracts are located in contracts/test, with unit tests being written in Typescript. The unit tests are found within test and make extensive use of fixtures from hardhat-deploy.

Deployment

The deployment in videre-contracts is handled by hardhat-deploy which handles deployment in the following scenarios:

  1. Local unit testing - deploy to hardhat local chain.
  2. Staging - deploys to live testnet (ie. sokol, goerli, ropsten, etc).
  3. Production (forking) - deploy to hardhat local chain forked from production archive node.
  4. Production - deploy to live environment.

CI/CD

All PR are linted and subjected to local unit tests. Once a PR is pushed to the main branch, upon successful completion of linting and local unit tests, the contracts are pushed automatically to the nominated staging testnet (eg. sokol).

All staging releases are deployed using transparent proxy contracts, allowing for in-place upgrading in the development cycle.

WARNING: When a smart contract is modified such that it's storage layout changes, this is grounds for nominating a breaking change in the commit message, at which time the entire staging environment should be redeployed with new addresses published to the in the release notes.

Sokol (staging)

  • TimestampRegistry - 0x24E2208ca60DFF063DA854Edcd2Ed5B0C2Cb6933
  • ServiceProviderRegistry - 0xC1A95DD6184C6A37A9Dd7b4b5E7DfBd5065C8Dd5
  • LineRegistry - 0xE7de8c7F3F9B24F9b8b519035eC53887BE3f5443
  • Vat - 0x47a6ac78e7A2C27A85903b172D32a78F88aac0c9
  • MockERC20 - 0x344514f61ae62dB6ce7261D0eeb1CbA5a03bCc61
  • GemJoin - 0x0190aC9B981Aa9AB7eD645C96D4a403a1c484988
  • Giver - 0xb2BF9a28A7f92153686F94C71883f360D546a27C

All contracts have source code verified via sourcify, with this being accessible via blockscout.

Developers: In order to get whitelisted / receive test tokens, please kindly ask for help in our discord.

How to use

Unit testing:

yarn test

Coverage analysis:

yarn hardhat coverage

Run deploy scripts and deploy to sokol:

yarn hardhat deploy --network sokol

Now verify the contracts on Sourcify:

yarn hardhat sourcify --network sokol

NOTE: Substitute gnosis above for the applicable target network.