Ecosyste.ms: Awesome

An open API service indexing awesome lists of open source software.

Awesome Lists | Featured Topics | Projects

https://github.com/solidstate-network/solidstate-solidity

💠 Upgradeable-first Solidity smart contract development library 💠
https://github.com/solidstate-network/solidstate-solidity

buidler crypto cryptocurrency eth ether ethereum hardhat library smart-contracts solidity wow

Last synced: 6 days ago
JSON representation

💠 Upgradeable-first Solidity smart contract development library 💠

Awesome Lists containing this project

README

        

# SolidState Solidity

SolidState is an upgradeable-first Solidity smart contract development library.

It consists of the following packages:

| package | description | 📕 |
| ----------------------- | ------------------------------------------------------------------------------------- | --------------------------- |
| `@solidstate/abi` | contract ABIs | [📖](./abi/README.md) |
| `@solidstate/contracts` | core contracts | [📖](./contracts/README.md) |
| `@solidstate/library` | functions for interacting with and validating contracts | [📖](./lib/README.md) |
| `@solidstate/spec` | portable tests which may be run against third-party implementations of core contracts | [📖](./spec/README.md) |

### Contracts

All contracts are designed to either be deployed through the standard `constructor` method, or referenced by a proxy. To this end, the [diamond storage](https://medium.com/1milliondevs/new-storage-layout-for-proxy-contracts-and-diamonds-98d01d0eadb) pattern is employed exclusively.

### Spec

Where possible, automated tests are designed to be imported by repositories which make use of the SolidState contracts and run against any derived contracts. This is to help prevent unintended changes to the base contract behavior.

For example, consider a custom `ERC20Base` implementation:

```solidity
import '@solidstate/contracts/token/ERC20/base/ERC20Base.sol';

contract CustomToken is ERC20Base {
// custom code...
}
```

Rather than rewrite the `ERC20Base` tests or assume that all core behavior remains untouched, one can import the included tests and run them against the custom implementation:

```javascript
describe('CustomToken', () => {
let instance;

beforeEach(async () => {
const factory = await ethers.getContractFactory('CustomToken');
instance = await factory.deploy();
await instance.deployed();
});

describeBehaviorOfERC20Base(
async () => instance,
{
args: ...,
}
);

// custom tests...
});
```

If parts of the base implementation are changed intentionally, tests can be selectively skipped:

```javascript
describeBehaviorOfERC20Base(
async () => instance,
{
args: ...
},
['#balanceOf'],
);

describe('#balanceOf', () => {
// custom tests
});
```

## Development

Install dependencies via Yarn:

```bash
yarn install
```

Setup Husky to format code on commit:

```bash
yarn prepare
```

Compile contracts via Hardhat:

```bash
yarn run hardhat compile
```

Automatically upgrade dependencies with yarn-up:

```bash
yarn upgrade-dependencies
```

### Testing

Test contracts with Hardhat and generate gas report using `hardhat-gas-reporter`:

```bash
yarn run hardhat test
```

Generate a code coverage report using `solidity-coverage`:

```bash
yarn run hardhat coverage
```

### Publication

Publish packages via Lerna:

```bash
yarn lerna-publish
```