Pkg
Stats

npm package discovery and stats viewer.

Discover Tips

General search
[free text search, go nuts!]
Package details
pkg:[package-name]
User packages
@[username]

Sponsor

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.

Twitter
@PkgStats
GitHub
pkgstats
Twitter
@ryanhefner
GitHub
ryanhefner
Site
ryanhefner.com

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 🙏

Framework
react / react-dom
Server
next / express / next-routes
Data Store
redux / react-redux / next-redux-wrapper / redux-thunk / redux-logger
Caching
lru-cache
CSS / Styling
next-page-transitions / styled-components
Typeface
@ibm/plex
Avatars
gravatar
Data Viz
chart.js / react-sparklines
Date formatting
dayjs
Infinite scrolling
react-scroll-trigger
Markdown rendering
react-markdown
Repository url parsing
hosted-git-info
User data
npm-user
Compiling
babel-plugin-module-resolver / babel-plugin-styled-components
Types
prop-types
Odds & Ends
es6-promise / isomorphic-fetch

© 2024 – Pkg Stats / Ryan Hefner

@tokene/core-contracts

v1.8.0

Published

4 months ago

The TokenE operating system on top of EVM by Distributed Lab

Downloads

36

0High
0Medium
0Low

solidity ethereum smart-contracts tokene distributedlab

The TokenE operating system on top of EVM by Distributed Lab

This repository represents the core smart contracts part of the operating system.

What

The TokenE core consists of 5 main smart contracts:

MasterContractsRegistry
MasterAccessManagement
ReviewableRequests
ConstantRegistry
Multicall

Each of these contracts serves an important role for the system:

The MasterContractsRegistry is an ERC-6224 compliant contract that is used throughout the core and its modules.
The MasterAccessManagement is used to handle permissions and access, leveraging solarity RBAC smart contract.
The ReviewableRequests is a primary integration tool that is used to "speak" with admins. One can issue tokens or pass KYC requests via that contract.
The ConstantRegistry that stores the system-wide parameters.
The Multicall is used as a utility to execute batches of transactions.

Installation

The core contracts are available as an npm package:

$ npm install @tokene/core-contracts

Or if you want to use the low-level solarity:

$ npm install @solarity/solidity-lib

Integration

Once you have installed the packages, feel free to play around with them.

In order to integrate with TokenE core, please check that you are aware of these things:

Your module has to be dockerized. The smart contract, scripts, and deployments must be included in the docker image.
TokenE is a role based system, the external access control must integrated with MasterAccessManagement contract.
Double check that the RBAC resource does not collide with the any existing one.
Your smart contract must be discoverable by the system. It means that you will have to add them to the MasterContractsRegistry in the deployment scripts.
You must never create reviewable requests directly, always use the appropriate module for that. If you are writing such module, make sure it is able to handle both "accept" and "reject" request cases.

Documentation

You can find an extensive documentation of the protocol here.

License

The TokenE core is released under the custom License. Please take a look to understand the limitations.