diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index ff3d740..d0a2082 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -1,110 +1,502 @@
-# Contributing
+# Contributing to OnChainTestKit
 
-All contributions are welcome, from the tiniest typo to a brand new article.
-Translations in all languages are welcome (or, for that matter, original
-articles in any language). Send a pull request or open an issue any time of day
-or night.
+Thank you for your interest in contributing to OnChainTestKit! We value contributions from the community and appreciate your time and effort.
 
-**Please prepend the tag `[language/lang-code]` to your issues and pull
-requests.** For example, `[python/en]` for English Python. This will help
-everyone pick out things they care about.
+---
+
+## Table of Contents
+
+- [Getting Started](#-getting-started)
+- [Development Workflow](#-development-workflow)
+- [Code Style Guidelines](#-code-style-guidelines)
+- [Testing Guidelines](#-testing-guidelines)
+- [Documentation](#-documentation)
+- [Reporting Bugs](#-reporting-bugs)
+- [Suggesting Features](#-suggesting-features)
+- [Code Review Process](#-code-review-process)
+- [Getting Help](#-getting-help)
+
+---
+
+## 🚀 Getting Started
+
+### Prerequisites
+
+Before you begin, ensure you have the following installed:
+
+- **Node.js** 14.0.0 or higher
+- **npm**, yarn, or pnpm
+- **Git**
+- **Playwright Test**
+
+### Development Environment Setup
+
+Follow these steps to set up your local development environment:
+
+#### 1. Fork and Clone
+
+```bash
+git clone https://github.com/YOUR-USERNAME/https-github.com-joe10832-onchaintestkit.git
+cd https-github.com-joe10832-onchaintestkit
+```
+
+#### 2. Install Dependencies
+
+```bash
+npm install
+```
+
+#### 3. Build the Project
+
+```bash
+npm run build
+```
+
+#### 4. Prepare Wallet Extensions
+
+```bash
+npm run prepare-metamask
+npm run prepare-coinbase
+npm run prepare-phantom
+```
+
+#### 5. Configure Environment
+
+```bash
+export E2E_TEST_SEED_PHRASE="test test test test test test test test test test test junk"
+```
+
+> ⚠️ **Security Warning**: Never use real seed phrases or funds for testing!
+
+#### 6. Verify Setup
+
+```bash
+npm test
+```
+
+---
+
+## 🔄 Development Workflow
+
+### 1. Create a Feature Branch
 
-We're happy for any contribution in any form, but if you're making more than one
-major change (i.e. translations for two different languages) it would be super
-cool of you to make a separate pull request for each one so that someone can
-review them more effectively and/or individually.
+Always work on a dedicated branch for your changes:
 
-## Style Guidelines
+```bash
+# For new features
+git checkout -b feature/descriptive-feature-name
 
-* **Keep lines under 80 chars**
-  * Try to keep line length in code blocks to 80 characters or fewer.
-  * Otherwise, the text will overflow and look odd.
-  * This and other potential pitfalls to format the content consistently are
-     identified by [markdownlint](https://github.com/markdownlint/markdownlint).
-* **Prefer example to exposition**
-  * Try to use as few words as possible.
-  * Code examples are preferred over exposition in all cases.
-* **Eschew surplusage**
-  * We welcome newcomers, but the target audience for this site is programmers
-     with some experience.
-  * Try to avoid explaining basic concepts except for those specific to the
-     language in question.
-  * Keep articles succinct and scannable. We all know how to use Google here.
-* **Use UTF-8**
+# For bug fixes
+git checkout -b fix/descriptive-bug-name
 
-### Header configuration
+# For documentation
+git checkout -b docs/descriptive-doc-change
+```
+
+### 2. Make Your Changes
+
+Follow these principles while making changes:
 
-The actual site generates HTML files from these Markdown ones.
-The markdown files can contain extra metadata before the actual markdown,
-called frontmatter.
+- ✅ Write clean, maintainable code
+- ✅ Follow existing code structure and patterns
+- ✅ Add tests for new features or bug fixes
+- ✅ Update documentation for API changes
+- ✅ Keep commits atomic and focused
 
-The following fields are necessary for English articles about programming
-languages:
+### 3. Test Your Changes
 
-* `name`: The human-readable name of the programming language
-* `contributors`: A list of [*author*, *URL*] lists to credit, *URL* is optional
+Run comprehensive checks before committing:
 
-Other fields:
+```bash
+# Run all tests
+npm test
 
-* `category`: The category of the article. So far, can be one of *language*,
-  *tool* or *Algorithms & Data Structures*. Defaults to *language* if omitted.
-* `filename`: The filename for this article's code. It will be fetched, mashed
-  together, and made downloadable.
+# Check code style
+npm run lint
 
-Translations should also include:
+# Auto-fix linting issues
+npm run lint:fix
 
-* `translators`: A list of [*translator*, *URL*] lists to credit, *URL* is optional
+# Format code
+npm run format
+
+# Build to verify compilation
+npm run build
+```
+
+### 4. Commit Your Changes
+
+We follow the [Conventional Commits](https://www.conventionalcommits.org/) specification:
+
+```bash
+git add .
+git commit -m "type: brief description of changes"
+```
+
+**Commit Types:**
+
+| Type | Description | Example |
+|------|-------------|---------|
+| `feat` | New feature | `feat: add support for Phantom wallet` |
+| `fix` | Bug fix | `fix: resolve connection timeout issue` |
+| `docs` | Documentation only | `docs: update installation guide` |
+| `style` | Code style/formatting | `style: apply consistent indentation` |
+| `refactor` | Code restructuring | `refactor: simplify config builder` |
+| `test` | Test additions/changes | `test: add wallet integration tests` |
+| `chore` | Maintenance tasks | `chore: update dependencies` |
+| `perf` | Performance improvement | `perf: optimize wallet loading` |
+
+**Example Commits:**
+
+```bash
+git commit -m "feat: add multi-chain support for Base network"
+git commit -m "fix: resolve MetaMask extension loading error"
+git commit -m "docs: add fork mode configuration examples"
+```
+
+### 5. Push to Your Fork
+
+```bash
+git push origin feature/your-feature-name
+```
 
-Non-English articles inherit frontmatter values from the English article (if it exists)
-but you can overwrite them.
+### 6. Submit a Pull Request
 
-Here's an example header for Ruby:
+1. Navigate to the [repository](https://github.com/MunyayLLC/https-github.com-joe10832-onchaintestkit)
+2. Click **"New Pull Request"**
+3. Select your feature branch
+4. Fill out the PR template completely
+5. Link any related issues
+6. Submit for review
 
-```yaml
 ---
-name: Ruby
-filename: learnruby.rb
-contributors:
-    - ["Doktor Esperanto", "http://example.com/"]
-    - ["Someone else", "http://someoneelseswebsite.com/"]
+
+## 📝 Code Style Guidelines
+
+### TypeScript/JavaScript Standards
+
+**Code Organization:**
+
+```typescript
+// 1. External imports first
+import { test, expect } from '@playwright/test';
+
+// 2. Internal imports second
+import { configure, createOnchainTest } from '@coinbase/onchaintestkit';
+
+// 3. Type definitions
+interface WalletConfig {
+  seedPhrase: string;
+  password: string;
+}
+
+// 4. Implementation
+export function setupWallet(config: WalletConfig) {
+  // Implementation
+}
+```
+
+**Best Practices:**
+
+- ✅ Use TypeScript for all new code
+- ✅ Leverage TypeScript's type system fully
+- ✅ Use meaningful, descriptive names
+- ✅ Add JSDoc comments for public APIs
+- ✅ Keep functions small and focused (< 50 lines)
+- ✅ Prefer pure functions when possible
+- ✅ Handle errors explicitly
+
+**Example:**
+
+```typescript
+/**
+ * Configures a wallet for testing
+ * @param seedPhrase - Test wallet seed phrase
+ * @param password - Wallet password
+ * @returns Configured wallet instance
+ * @throws {Error} If seed phrase is invalid
+ */
+export function configureWallet(
+  seedPhrase: string,
+  password: string
+): WalletInstance {
+  if (!seedPhrase || seedPhrase.split(' ').length !== 12) {
+    throw new Error('Invalid seed phrase: must be 12 words');
+  }
+  
+  return new WalletInstance({ seedPhrase, password });
+}
+```
+
+### Code Quality Checklist
+
+- ☑️ **Type Safety** - No `any` types without justification
+- ☑️ **Error Handling** - All errors handled appropriately
+- ☑️ **Documentation** - Public APIs have JSDoc comments
+- ☑️ **Testing** - New code includes tests
+- ☑️ **Performance** - No obvious performance issues
+
+### Project Structure
+
+```
+src/
+├── cli/                  # CLI tools and commands
+│   ├── prepare-coinbase.mjs
+│   ├── prepare-metamask.mjs
+│   └── prepare-phantom.mjs
+├── contracts/            # Smart contract utilities
+│   └── SmartContractManager.ts
+├── node/                 # Local node management
+│   ├── LocalNodeManager.ts
+│   ├── NetworkInterceptor.ts
+│   └── types.ts
+├── utils/                # Shared utilities
+│   └── ConnectorUtil.ts
+├── wallets/              # Wallet implementations
+│   ├── BaseWallet.ts
+│   ├── types.ts
+│   ├── Coinbase/
+│   ├── MetaMask/
+│   └── Phantom/
+├── configBuilder.ts      # Configuration builder
+├── constants.ts          # Shared constants
+├── createOnchainTest.ts  # Test creation
+├── index.ts              # Public API exports
+└── types.ts              # Shared types
+```
+
 ---
+
+## 🧪 Testing Guidelines
+
+### Writing Tests
+
+**Test Organization:**
+
+- Place tests in the `tests/` directory
+- Mirror the `src/` directory structure
+- Use descriptive test file names (`*.test.ts` or `*.spec.ts`)
+
+**Test Structure:**
+
+```typescript
+import { test, expect } from '@playwright/test';
+import { configure, createOnchainTest } from '@coinbase/onchaintestkit';
+
+test.describe('Wallet Connection', () => {
+  test('should connect MetaMask wallet successfully', async () => {
+    // Arrange - Set up test conditions
+    const config = configure()
+      .withMetaMask()
+      .withSeedPhrase({
+        seedPhrase: process.env.E2E_TEST_SEED_PHRASE!,
+        password: 'TestPassword123'
+      })
+      .build();
+    
+    // Act - Perform the action
+    const { page, wallet } = await createOnchainTest(config);
+    await page.goto('https://test-dapp.com');
+    await wallet.connect();
+    
+    // Assert - Verify the outcome
+    expect(await wallet.isConnected()).toBe(true);
+  });
+  
+  test('should handle connection rejection gracefully', async () => {
+    // Test error scenarios
+  });
+});
 ```
 
-### Syntax highlighter
+**Testing Best Practices:**
+
+- ✅ Test one thing per test
+- ✅ Use descriptive test names
+- ✅ Test both success and failure paths
+- ✅ Keep tests independent and isolated
+- ✅ Clean up resources after tests
+- ✅ Use meaningful assertions
+
+---
+
+## 📚 Documentation
+
+### When to Update Documentation
+
+Update documentation when you:
+
+- Add new features or APIs
+- Change existing behavior
+- Fix bugs that affect usage
+- Add new configuration options
 
-[Pygments](https://pygments.org/languages/) is used for syntax highlighting.
+### Documentation Files
 
-### Should I add myself as a contributor?
+| File | Purpose |
+|------|---------|
+| `README.md` | Project overview and quick start |
+| `CONTRIBUTING.md` | Contribution guidelines (this file) |
+| `docs/` | Detailed guides and API reference |
+| `example/` | Working code examples |
+| JSDoc comments | Inline API documentation |
 
-If you want to add yourself to contributors, keep in mind that contributors get
-equal billing, and the first contributor usually wrote the whole article. Please
-use your judgment when deciding if your contribution constitutes a substantial
-addition or not.
+### Documentation Style
 
-## Building the site locally
+**Writing Guidelines:**
 
-Install Python. On macOS this can be done with [Homebrew](https://brew.sh/).
+- ✅ Be clear and concise
+- ✅ Include code examples
+- ✅ Explain the "why" behind decisions
+- ✅ Keep examples up to date
+- ✅ Use proper markdown formatting
+- ✅ Add links to related documentation
 
-```sh
-brew install python
+**Example:**
+
+```markdown
+## Configuring Fork Mode
+
+Fork mode allows you to test against a snapshot of mainnet at a specific block:
+
+\```typescript
+const config = configure()
+  .withLocalNode({
+    fork: 'https://eth-mainnet.g.alchemy.com/v2/YOUR-KEY',
+    forkBlockNumber: 18500000 // Pin to specific block
+  })
+  .build();
+\```
+
+This ensures reproducible tests by using a consistent blockchain state.
 ```
 
-Then clone two repos, install dependencies and run.
+---
+
+## 🐛 Reporting Bugs
+
+### Before Submitting a Bug Report
+
+1. ✅ **Search existing issues** - Check if it's already reported
+2. ✅ **Test with latest version** - Verify bug exists in current release
+3. ✅ **Verify configuration** - Ensure your setup is correct
+4. ✅ **Create minimal reproduction** - Isolate the issue
+
+### Bug Report Template
 
-```sh
-# Clone website
-git clone https://github.com/adambard/learnxinyminutes-site
-# Clone docs (this repo) nested in website
-git clone https://github.com/<YOUR-USERNAME>/learnxinyminutes-docs ./learnxinyminutes-site/source/docs/
+Include the following information:
 
-# Install dependencies
-cd learnxinyminutes-site
-pip install -r requirements.txt
+**Description**
+Clear and concise description of the bug.
 
-# Run
-python build.py
-cd build
-python -m http.server
+**Steps to Reproduce**
+1. Configure wallet with...
+2. Run test with...
+3. Observe error...
 
-# open http://localhost:8000/ in your browser of choice
+**Expected Behavior**
+What should happen?
+
+**Actual Behavior**
+What actually happens?
+
+**Environment**
+- OS: [e.g., macOS 13.0, Ubuntu 22.04]
+- Node version: [e.g., v18.16.0]
+- Package version: [e.g., 1.2.0]
+- Wallet: [e.g., MetaMask 11.0.0]
+
+**Code Sample**
+```typescript
+// Minimal reproducible example
 ```
+
+**Additional Context**
+Screenshots, error messages, or other relevant information.
+
+---
+
+## 💡 Suggesting Features
+
+We welcome feature suggestions! To propose a new feature:
+
+1. ✅ **Check existing issues** - See if it's already suggested
+2. ✅ **Open an issue** - Use the `enhancement` label
+3. ✅ **Describe the use case** - Explain the problem it solves
+4. ✅ **Provide examples** - Show how it would work
+5. ✅ **Consider alternatives** - Discuss other approaches
+
+---
+
+## 🔍 Code Review Process
+
+### Review Criteria
+
+Reviewers evaluate submissions based on:
+
+| Aspect | What We Check |
+|--------|---------------|
+| **Correctness** | Does it work as intended? No bugs? |
+| **Tests** | Are there adequate tests? Do they pass? |
+| **Documentation** | Is it well documented? |
+| **Style** | Does it follow our guidelines? |
+| **Performance** | Are there performance implications? |
+| **Security** | Are there security concerns? |
+| **Breaking Changes** | Is backward compatibility maintained? |
+
+### Review Timeline
+
+- **Initial Review**: Within 1-3 business days
+- **Feedback**: Maintainers provide constructive feedback
+- **Iteration**: Make requested changes
+- **Approval**: Once approved, PR will be merged
+
+---
+
+## 🚫 What NOT to Contribute
+
+Please avoid:
+
+- ❌ **Breaking changes** without prior discussion
+- ❌ **Large refactors** without approval
+- ❌ **Failing tests** or linting errors
+- ❌ **Unrelated changes** in a single PR
+- ❌ **Real credentials** or secrets in code
+- ❌ **Dependencies** without justification
+
+---
+
+## 📞 Getting Help
+
+Need assistance with your contribution?
+
+- 💬 **[Discussions](https://github.com/MunyayLLC/https-github.com-joe10832-onchaintestkit/discussions)** - Ask questions and share ideas
+- 📧 **PR Comments** - Ask questions directly in your pull request
+- 📖 **[Documentation](./docs/)** - Check the comprehensive guides
+- 🐛 **[Issues](https://github.com/MunyayLLC/https-github.com-joe10832-onchaintestkit/issues)** - Report problems or request features
+
+---
+
+## 🎉 Recognition
+
+Contributors are valued members of our community:
+
+- ✨ Listed in project contributors
+- 📝 Credited in release notes (for significant contributions)
+- 🌟 Part of our blockchain testing community
+
+---
+
+## 📄 License
+
+By contributing to OnChainTestKit, you agree that your contributions will be licensed under the MIT License.
+
+---
+
+<div align="center">
+
+**Thank you for contributing to OnChainTestKit!**
+
+Every contribution, no matter the size, helps make blockchain testing better for everyone. 🚀
+
+</div>
diff --git a/README.md b/README.md
index 10b6d04..bf940b1 100644
--- a/README.md
+++ b/README.md
@@ -1,90 +1,282 @@
-Formatting.**# Project Title
+# OnChainTestKit
 
-## Quickstart
+[![npm version](https://img.shields.io/npm/v/@coinbase/onchaintestkit.svg)](https://www.npmjs.com/package/@coinbase/onchaintestkit)
+[![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](https://opensource.org/licenses/MIT)
 
-Instructions on how to quickly get started with this project.
+End-to-end testing toolkit for blockchain applications, powered by Playwright.
 
-## Why use
+---
+
+## Table of Contents
+
+- [Features](#-features)
+- [Installation](#-installation)
+- [Quick Start](#-quick-start)
+- [Configuration](#-configuration)
+- [Supported Wallets](#-supported-wallets)
+- [Documentation](#-documentation)
+- [Contributing](#-contributing)
+- [License](#-license)
 
-Reasons to use this project.
+---
+
+## 🚀 Features
 
-## Getting Commercial Support
+- **🔗 Blockchain Testing** - Comprehensive E2E testing for Web3 applications
+- **🎭 Playwright Powered** - Built on Playwright for reliable, fast automation
+- **🔐 Multi-Wallet Support** - Native integration with MetaMask, Coinbase Wallet, and Phantom
+- **🌐 Network Flexibility** - Test on mainnet, testnets, or forked local nodes
+- **🛠️ Simple Configuration** - Intuitive, chainable API for easy setup
+- **📝 TypeScript First** - Full type definitions for enhanced developer experience
 
-Information on how to get commercial support for this project.
+---
 
-## Contribute
+## 📦 Installation
 
-Guidelines on how to contribute to this project.<https://stackblitz.com/~/github.com/MunyayLLC/https-github.com-joe10832-onchaintestkit/pull/286https://stackblitz.com/~/github.com/MunyayLLC/https-github.com-joe10832-onchaintestkit/pull/288https://stackblitz.com/~/github.com/MunyayLLC/https-github.com-joe10832-onchaintestkit/pull/286?file=package.json>
+Install OnChainTestKit using your preferred package manager:
 
-- **Write and maintain documentation (`README.md`, `CONTRIBUTING.md # Enterprise-Ready Software Engineering Project
+```bash
+# npm
+npm install @coinbase/onchaintestkit
 
-Welcome to the **Enterprise-Ready Software Engineering Project**. This repository is designed for professional development in Python, Java, and C++ with a focus on enterprise-grade solutions, scalability, and maintainability.
+# yarn
+yarn add @coinbase/onchaintestkit
+
+# pnpm
+pnpm add @coinbase/onchaintestkit
+```
+
+### Prerequisites
+
+- **Node.js** 14.0.0 or higher
+- **Playwright Test**: Install as dev dependency
+  ```bash
+  npm install --save-dev @playwright/test
+  ```
 
 ---
 
-## 🚀 Business Focus
+## 🎯 Quick Start
+
+### Step 1: Prepare Wallet Extensions
+
+```bash
+# Prepare MetaMask extension
+npm run prepare-metamask
 
-This project is tailored for **business enterprise-ready** solutions, ensuring professional-grade software engineering practices. It emphasizes:
+# Alternatively, use npx
+npx prepare-metamask
+```
 
-- **Scalability**: Designed to handle enterprise-level workloads.
-- **Maintainability**: Code structured for long-term use and collaboration.
-- **Integration**: Seamless integration with existing enterprise systems.
+### Step 2: Configure Environment
+
+Set up your test environment variables:
+
+```bash
+export E2E_TEST_SEED_PHRASE="test test test test test test test test test test test junk"
+```
+
+> ⚠️ **Security Warning**: Only use test seed phrases. Never use real wallet credentials or funds.
+
+### Step 3: Write Your First Test
+
+```typescript
+import { configure, createOnchainTest } from '@coinbase/onchaintestkit';
+import { test } from '@playwright/test';
+
+// Configure test environment
+const config = configure()
+  .withMetaMask()
+  .withSeedPhrase({
+    seedPhrase: process.env.E2E_TEST_SEED_PHRASE,
+    password: 'TestPassword123'
+  })
+  .build();
+
+// Write your test
+test('should connect wallet and interact with dApp', async () => {
+  const { page, wallet } = await createOnchainTest(config);
+  
+  // Navigate to your dApp
+  await page.goto('https://your-dapp.com');
+  
+  // Connect wallet
+  await wallet.connect();
+  
+  // Add your test logic here
+});
+```
 
 ---
 
-## 🧑‍💻 Your Role
+## 🔧 Configuration
+
+### Basic Configuration
+
+Simple wallet configuration for testing:
+
+```typescript
+import { configure } from '@coinbase/onchaintestkit';
+
+const config = configure()
+  .withMetaMask()
+  .withSeedPhrase({
+    seedPhrase: process.env.E2E_TEST_SEED_PHRASE,
+    password: 'PASSWORD'
+  })
+  .build();
+```
+
+### Fork Mode Testing
+
+Test against a forked version of mainnet for deterministic, reproducible tests:
+
+```typescript
+const forkConfig = configure()
+  .withLocalNode({
+    fork: 'https://eth-mainnet.g.alchemy.com/v2/your-api-key',
+    forkBlockNumber: 18500000, // Pin to specific block for consistency
+    chainId: 1,
+  })
+  .withMetaMask()
+  .withSeedPhrase({
+    seedPhrase: process.env.E2E_TEST_SEED_PHRASE,
+    password: 'PASSWORD'
+  })
+  .build();
+```
+
+### Multi-Network Configuration
+
+Configure custom networks for comprehensive testing:
+
+```typescript
+import { baseSepolia } from 'viem/chains';
+
+const networkConfig = configure()
+  .withMetaMask()
+  .withSeedPhrase({ 
+    seedPhrase: process.env.E2E_TEST_SEED_PHRASE, 
+    password: 'PASSWORD' 
+  })
+  .withNetwork({
+    name: baseSepolia.name,
+    rpcUrl: baseSepolia.rpcUrls.default.http[0],
+    chainId: baseSepolia.id,
+    symbol: baseSepolia.nativeCurrency.symbol,
+  })
+  .build();
+```
+
+---
+
+## 🔐 Supported Wallets
+
+OnChainTestKit provides first-class support for the most popular Web3 wallets:
 
-- **Role Type**: `{role_type}` expert in `{domain}`
-- **Focus Area**: `{key_skill_area}`
+| Wallet | Description | Command |
+|--------|-------------|---------|
+| **MetaMask** | Most widely used Ethereum wallet | `npm run prepare-metamask` |
+| **Coinbase Wallet** | Coinbase's self-custody solution | `npm run prepare-coinbase` |
+| **Phantom** | Leading Solana wallet with Ethereum support | `npm run prepare-phantom` |
 
-As a contributor, your expertise in `{domain}` will help shape the success of this project. Focus on `{key_skill_area}` to ensure high-quality contributions.
+### Preparing Wallet Extensions
+
+```bash
+# Prepare all wallets at once
+npm run prepare-metamask && npm run prepare-coinbase && npm run prepare-phantom
+
+# Or prepare individually as needed
+npm run prepare-metamask
+npm run prepare-coinbase
+npm run prepare-phantom
+```
 
 ---
 
-## 📜 Code Guidelines
+## 📚 Documentation
+
+Explore comprehensive guides and resources:
+
+- **[Installation Guide](./docs/installation.md)** - Detailed setup instructions
+- **[User Guide](./docs/guide.md)** - Complete usage documentation
+- **[Examples](./example/)** - Working code examples
+- **[API Reference](./docs/)** - Full API documentation
+
+---
+
+## 🧪 Testing
+
+Run the complete test suite:
+
+```bash
+npm test
+```
+
+---
 
-### General Guidelines
+## 🤝 Contributing
 
-- Use **language-specific conventions** for Python, Java, and C++.
-- Follow **design patterns** and **best practices** for enterprise software.
-- Optimize for **performance**, **readability**, and **scalability**.
+We welcome contributions from the community! See our [Contributing Guide](./CONTRIBUTING.md) for details on:
 
-### Python
+- Setting up your development environment
+- Code style guidelines
+- Submitting pull requests
+- Reporting bugs and requesting features
 
-- Follow [PEP 8](https://peps.python.org/pep-0008/) for coding standards.
-- Use type hints and docstrings for better readability.
-- Write unit tests using `unittest` or `pytest`.
+### Quick Development Setup
 
-### Java
+```bash
+# Clone and navigate to repository
+git clone https://github.com/MunyayLLC/https-github.com-joe10832-onchaintestkit.git
+cd https-github.com-joe10832-onchaintestkit
 
-- Adhere to [Oracle's Java Code Conventions](https://www.oracle.com/java/technologies/javase/codeconventions-introduction.html).
-- Use Maven or Gradle for dependency management.
-- Write JUnit tests for all major components.
+# Install dependencies and build
+npm install
+npm run build
 
-### C++
+# Run tests
+npm test
 
-- Follow [Google's C++ Style Guide](https://google.github.io/styleguide/cppguide.html).
-- Use `CMake` for build configuration.
-- Ensure memory safety and avoid undefined behavior.
+# Code quality checks
+npm run format
+npm run lint
+```
 
 ---
 
-## 🔧 Integration
+## 📄 License
 
-This project is designed to integrate seamlessly with enterprise systems. Key integration points include:
+This project is licensed under the MIT License. See the [LICENSE](LICENSE) file for details.
 
-- **APIs**: RESTful APIs for communication between services.
-- **Databases**: Support for relational and NoSQL databases.
-- **CI/CD Pipelines**: Automated testing and deployment workflows.
+---
+
+## 🙏 Acknowledgments
+
+Built with ❤️ by Coinbase and powered by Playwright for robust blockchain testing.
+
+---
+
+## 🔗 Resources
+
+- **[GitHub Repository](https://github.com/MunyayLLC/https-github.com-joe10832-onchaintestkit)** - Source code and development
+- **[npm Package](https://www.npmjs.com/package/@coinbase/onchaintestkit)** - Package registry
+- **[Issue Tracker](https://github.com/MunyayLLC/https-github.com-joe10832-onchaintestkit/issues)** - Bug reports and feature requests
 
 ---
 
-## 📚 Further Reading
+## 💬 Support
+
+Need help? We're here for you:
 
-- [Python Best Practices](https://realpython.com/)
-- [Java Design Patterns](https://java-design-patterns.com/)
-- [C++ Modern Practices](https://isocpp.org/)
+- 📖 **[Documentation](./docs/)** - Comprehensive guides and tutorials
+- 🐛 **[Report Issues](https://github.com/MunyayLLC/https-github.com-joe10832-onchaintestkit/issues)** - Found a bug? Let us know
+- 💡 **[Request Features](https://github.com/MunyayLLC/https-github.com-joe10832-onchaintestkit/issues)** - Have an idea? Share it with us
 
 ---
 
-For questions or support, please open an issue or contact the project maintainer.
\ No newline at end of file
+<div align="center">
+
+**⚠️ Important**: Always use test accounts and never use real funds when testing blockchain applications.
+
+</div>