SEP-8: Real Time Access Control

Author	Devs Do Something
Status	Proposed
Type	Software
Network	All
Implementor	ArshaanB
Release	V4.0
Created	2024-10-18

Simple Summary

There is a need for the contracts to move away from merkle root-based access lists. The following challenges exist with the current merkle root structure:

A list of 1,000 addresses may take up to ten minutes to generate and publish on chain When a new address needs to be added, the merkle root needs to be regenerated and re-published to the network These two issues make it such that the system cannot facilitate high-scale transactions.

There needs to be a way to publish the merkle root information to the smart contract in a manner that scales with new address additions.

Abstract

Merkle root-based access lists require multiple interactions with centralized and decentralized networks. The first being the merkle root generation which can take ten minutes to generate and instantiate onchain. The next bottleneck occurs when a new address needs to be added to the merkle root. This makes it prohibitive for high-scale, live applications. A decentralized, real-time solution can provide smart-contract based applications the desired solution at web-scale.

Motivation

Currently if servicing the number of users that Soft Protocol has serviced in the past, it can cost hundreds of thousands of dollars to register each address onchain as they come. This is not sustainable for airdrops or token sales as it inhibits the user experience.

Specification

Overview

By enabling a centralized or decentralized system that can collect new addresses and provide a proof that can be submitted to the smart contract in real time.

Rationale

The contracts will be deployed on the Base network, including the Sale and Claims contracts, need a way to collect addresses on unique lists. Additionally, after an address is on a list, a proof needs to be generated for submission into the smart contract to prove its on the list. This proof needs to be based on ECDSA and also consumable by conventional smart contract libraries.

Technical Specification

TBD