The Sign product line is quite extensive, so let's dive deeper into it. 🤷🏿‍♀️

@ethsign is an actual use-case application of the Sign Protocol (on-chain authentication protocol) built by the Sign team. Why is it called Web2-like? Because electronic signature products have been widely used in the Web2 industry for a long time.

For example:

- Globally, tools like @DocuSign are popular.

- In India, platforms like "Fadada" and "Shangshangqian" exist.

📌 However, in Web3, EthSign might be the most Web2-like digital signature platform.

Today, we'll discuss EthSign’s product features, technology implementation, and PMF (Product-Market Fit).

What is EthSign?

EthSign is a decentralized digital signature platform where users can upload and digitally sign contracts just like @DocuSign. The key differences are:

- All data is stored on the blockchain

- Signatures are on-chain verifiable

- Files are stored with encryption

- Uses Arweave storage for permanent records

📌 Interestingly, EthSign has received investment from Sequoia Capital (China, India, and the US branches), making it quite unique!

Why is EthSign Needed?

Web3 is a world where, despite smart contracts and token-based systems, "legal agreements" are still essential. However, traditional digital signature tools don’t fully fit into Web3.

💡 Some key problems:

1. No "Proof of Agreement" in on-chain cooperation

- In Web3, DAO voting, smart contract execution, and token distribution happen on-chain.

- But agreements between team members (e.g., token sharing, job contracts) still rely on Discord chats or screenshots.

1. Traditional document signature tools are unsuitable for Web3 projects

- Services like DocuSign require email verification and KYC.

- Web3 needs a "DocuSign-like simple but wallet-connected, encrypted, and decentralized tool."

---

EthSign's Product Features

1. Contract Creation

- Login via MetaMask, OKX Wallet, or Particle Network (Google/Twitter login)

- Upload PDFs or choose from ready-made templates

- Set signature positions, encryption level, and expiry time

1. Contract Signing

- Locally decrypt encrypted contracts and sign

- Multi-chain wallet support (EVM, Bitcoin, Solana, TON)

1. Contract Management

- Access all signed contracts from the backend

- Final signed documents are stored on Arweave – permanent and verifiable!

---

Technology Implementation

1. Data Encryption

EthSign offers three encryption modes:

- Unencrypted: Open data for everyone

- AES-256-GCM (Symmetric Encryption): A single password grants access

- AES-256-GCM + ECIES (Asymmetric Encryption):

• Private key-based encryption (true Web3 style)

• Only signers can read documents – even the EthSign team can't!

1. Signature Verification

- Every signer’s signature is verifiable via their wallet

- Signed documents get the EthSign Certified tag

- Users can manually verify contracts stored on Arweave

1. Data Storage Architecture

- AWS S3 (Temp Storage) + Arweave (Permanent Storage)

- During signing: Stored on AWS S3

- After signing: Uploaded to Arweave (immutable storage)

---

Business Model and PMF

EthSign’s Business Model

- Enterprise subscriptions

- Template & API access

- Custom services for large clients

However, EthSign's main revenue source currently comes from TokenTable, not direct signature services.

Has EthSign Achieved PMF (Product-Market Fit)?

Not yet. Key reasons:

1. Web3 users don’t take digital contracts seriously

2. Non-Web3 businesses don’t understand the value of blockchain contracts

But EthSign’s strong technology foundation could make it a leading Web3 infrastructure in the future.

---

🔥 Conclusion

While EthSign hasn’t reached mainstream adoption yet, it showcases the Sign team’s strong technological capabilities.

📌 If Web3 industry adoption for legal documents grows, EthSign could become the leading solution.

Big respect to @realyanxin @Potterlee222 @ClaireMa12 @Jerry_ZZQ and other dedicated builders!

#SIGN