created_at2024-01-21 13:46:02.846701
updated_at2024-06-03 12:43:30.10963
descriptionpendzl library for smart contract development on ink!.




Pendzl is a library for smart contract development on ink!.

Why use this library?

  • To make contracts interoperable to do safe cross-contract calls (by having the same function's signature among every contract)
  • To ensure the usage of Polkadot Standards Proposals
  • To ensure the usage of the latest & most secure implementation
  • Useful contracts that provide custom logic to be implemented in contracts
  • To save time by not writing boilerplate code
  • Useful features that can simplify development
  • All contracts are upgradeable by default

Which Standard tokens & useful contracts does it provide?

  • PSP22 - Fungible Token (ERC20 equivalent) with some extensions including Vault - a modified ERC-4626 contract!
  • PSP34 - Non-Fungible Token (ERC721 equivalent) with some extensions
  • (not yet supported) PSP37 - ERC1155 equivalent with extensions
  • Ownable Restrict access to action for non-owners
  • Access Control Define a set of roles and restrict access to action by roles
  • Pausable Pause/Unpause the contract to disable/enable some operations
  • (not yet supported) Timelock Controller Execute transactions with some delay
  • (not yet supported) Governor Govern
  • General Vester Allows for the creation of a vests

This library was created based on ideas of implementation macro, Storage trait, and storage_item macro that came from openbrush-contracts.

How does it work?

Library allows for reusing implementations of the supported traits for any ink! smart-contract. It's goal is to be modular and extensible without unnecessary complexity overhead.

Deriving implementations of provided traits is easy. For example, in case of a PSP22:

add a field of of type PSP22Storage and annotate it with #[storage_field] add StorageFieldGetter to storage struct's derive macro (with the above allows for access to the storage item via .data()) make your contract reuse the PSP22 implementation via #[pendzl::implementation(PSP22)] annotation on top of your contract! The first two steps are to satisfy required boundaries by default implementations - contract's storage must implement StorageFieldGetter with appropariate generic T (in this case it's PSP22Storage).

pub mod my_psp22 {
    pub struct Contract {
        psp22: PSP22Data,

The #[pendzl::implementation(PSP22)] macro implements the PSP22 by including the following code after the macro is expanded:

impl  pendzl::contracts::psp22::PSP22Internal for Contract {
            fn _total_supply(&self) -> Balance {

impl pendzl::contracts::psp22::PSP22 for Contract {
        fn total_supply(&self) -> Balance {

One can override the default_impl of functions from PSP22 and/or PSP22Internal as follows:

    const HATED_ACCOUNT: AccountId = <some_account>

    fn _update(
        &mut self,vault::PSP22VaultInternalDefaultImpl,
        /// one can use default_impl as in this example or provide completely new implementation.
        pendzl::contracts::psp22::implementation::PSP22InternalDefaultImpl::_update_default_impl(self, from, to, amount)

    fn approve(
        &mut self,
        spender: AccountId,
        value: Balance,
    ) -> Result<(), PSP22Error> {
        if spender == HATED_ACCOUNT {
            return Err(PSP22Error::Custom(String::from("Hated account can not have allowance to spend tokens")));
        /// one can use default_impl as in this example or provide completly new implementation.
        pendzl::contracts::psp22::implementation::PSP22DefaultImpl::approve(self, spender, value)

the above overrider functions (marked with #[overrider(...)] ) will be consumed by the #[pendzl::implementation(PSP22)]. As result, the body of the functions will be used to implement the apropariate function in apropariate trait. As showed in above example, one can still use the default implementation if one only wants to add some logic before/after the default implementation or one can fully reimplement the function.

Similar logic applies to storage items. One may not want to use the default PSP22Data and use his PSP22CustomData. This can be achieved in two ways:

  • by implementing PSP22Storage trait for PSP22CustomData,
  • overriding all functions from PSP22Internal trait

Installation & Testing

To work with the project you need to install ink! toolchain and NodeJS's dependencies.

  1. you need an installer rustup.
  2. ink! toolchain
  3. NodeJS deps you can install via pnpm command inside tests/ folder


To build exapmles use

$ bash


If you want to run tests enter the tests/ foldr and run

$ pnpm i
$ pnpm build:debug
$ pnpm test

We are in the process of migrating all tests from ink-e2e to TS. Some tests remain in the examples folder. To run yet not migrated tests :

$ bash


Was it audited?

Contracts in this repository have not yet been audited and may contain several vulnerabilities.


pendzl is released under the MIT License.

Commit count: 0

cargo fmt