Question 1

What is OmeShare?

Accepted Answer

OmeShare is a platform where creators build, publish, and remix interactive Code Builds using HTML, CSS, JavaScript, WebGL, and 3D. Create something worth sharing — publish your work, discover creators, and remix builds from the community. OmeShare also supports creator tokens on Base for builders who want to launch their own creator economy.

Question 2

How do I create a profile?

Accepted Answer

To create a profile on OmeShare, connect your wallet, then set up your public display name, handle, bio, and avatar. Your wallet address becomes your unique identifier. You can enhance your profile by connecting integrations like X (Twitter) and sharing your Code Builds with the community.

Question 3

Why connect a wallet?

Accepted Answer

Your wallet is your identity on OmeShare. Connecting a wallet verifies that you control a real blockchain address, which serves as the foundation for your profile and creator token capabilities. Wallet connection is read-only — OmeShare never accesses your private keys or controls your funds.

Question 4

Is OmeShare a bank or financial institution?

Accepted Answer

No. OmeShare is not a bank, credit union, or financial institution. OmeShare does not offer banking services, loans, or financial products. OmeShare is a creation, publishing, and discovery platform for interactive Code Builds, with optional creator token features.

Question 5

Is OmeShare an investment platform?

Accepted Answer

No. OmeShare is not an investment platform and does not provide investment advice. OmeShare provides creation tools, publishing, and discovery for Code Builds. Creator tokens, where available, are optional and users must conduct their own due diligence before engaging with any token.

Question 6

What is a Code Build?

Accepted Answer

A Code Build is an interactive project created with HTML, CSS, JavaScript, WebGL, and 3D. You write code directly in the OmeShare CodeBuilder, preview it live in a sandboxed runtime, and publish it for the community to discover, run, and remix. Code Builds can range from simple animations to full 3D scenes, games, and interactive experiences.

Question 7

How do I create a Code Build?

Accepted Answer

Go to the CodeBuilder page and start writing code in the Input Your Code panel. You can paste full HTML documents, raw JavaScript, raw CSS, or mixed HTML/CSS/JS — OmeShare automatically detects the format. Click Process & Run to preview your code in the sandboxed runtime. When you're happy with it, click Save Block to save it as a reusable block, or publish it for the community to discover.

Question 8

What are blocks in a Code Build?

Accepted Answer

Blocks are individual code segments that make up a Code Build. Each block can contain HTML, CSS, JavaScript, or a mix. Blocks are executed in order, so later blocks can build on top of earlier ones — for example, Block 1 might set up a 3D scene with window.OME_WORLD, and Block 2 can add furniture to that scene. You can enable, disable, reorder, duplicate, and delete blocks independently.

Question 9

What code formats are supported?

Accepted Answer

OmeShare's CodeBuilder accepts many valid web code formats: full HTML documents, HTML fragments, raw JavaScript (including IIFEs and arrow functions), ES module JavaScript with import statements, raw CSS, mixed HTML/CSS/JS, script-tag wrapped JavaScript, style-tag wrapped CSS, and Markdown-fenced code blocks. You don't need to wrap raw JavaScript in <script> tags — the builder detects the format automatically.

Question 10

How does the Code Build runtime work?

Accepted Answer

Code Builds run in an isolated iframe on a separate origin from the main OmeShare app. This sandbox allows WebGL, Canvas 2D, and WebGPU while preventing user code from accessing OmeShare auth tokens, cookies, localStorage, or the parent DOM. The runtime supports Three.js (with legacy API compatibility), Canvas 2D, WebGL/WebGL2, and additive blocks that share the same window context.

Question 11

Can I use Three.js in my Code Build?

Accepted Answer

Yes. Three.js is fully supported in OmeShare Code Builds. If your code uses the THREE global without importing it, OmeShare automatically adds a compatibility bridge that provides window.THREE with legacy API aliases (e.g. BoxBufferGeometry maps to BoxGeometry). You can also use ES module imports from CDN URLs. Only one version of Three.js is loaded to prevent conflicts.

Question 12

What is remixing a Code Build?

Accepted Answer

Remixing lets you copy a published Code Build into your own workspace, modify it, and publish your version. This is core to OmeShare's creative community — you can learn from other creators' code, build on their ideas, and share your remix. The original creator is credited on your remix.

Question 13

How do I publish a Code Build?

Accepted Answer

After creating and testing your Code Build in the builder, click Publish to make it publicly discoverable. Published builds appear on the Code Builds page and can be found by other creators. You can set your build's title, description, category, and tags before publishing. You can also capture a snapshot thumbnail for your build.

Question 14

What does Run All Blocks do?

Accepted Answer

Run All Blocks executes all enabled blocks in your Code Build at once, in order. This lets you quickly see the combined result of all your blocks working together, rather than running each block individually. You can still run individual blocks with Process & Run when you want to test a specific block in isolation.

Question 15

How do Save Code and Update work?

Accepted Answer

Save Code persists the current code in a block directly, without requiring a performance validation run. Update saves the block and includes validation metadata if available. Both ensure the block knows exactly what code to run. When your code matches the saved version, the panel shows 'Saved'. When you make changes, it shows 'Unsaved' to remind you to save again.

Question 16

How are runtime errors shown?

Accepted Answer

When a Code Build encounters a runtime error, the affected block's header shows 'see line X' with the specific line number highlighted in red in the code editor. The error message appears below the editor. Errors are attributed to the specific block that caused them, so you know exactly which code to fix. Detection and runtime errors are separate — if your JavaScript is valid but fails at runtime, it's still recognized as JavaScript.

Question 17

Can I create additive blocks that share state?

Accepted Answer

Yes. All enabled blocks in a Code Build execute in the same iframe window, so they share global state. A common pattern is Block 1 setting up window.OME_WORLD with a Three.js scene, renderer, and camera, then Block 2 (and later blocks) accessing window.OME_WORLD to add objects, furniture, lighting, and interactions. Blocks execute in order, so dependencies from earlier blocks are available to later ones.

Question 18

Which wallets are supported?

Accepted Answer

OmeShare supports MetaMask, Coinbase Wallet, WalletConnect, Trust Wallet, Phantom, Rainbow, and Rabby. On desktop, MetaMask and Coinbase Wallet work as browser extensions. On mobile, WalletConnect and deep-links to MetaMask/Coinbase in-app browsers are supported. Additional WalletConnect-compatible wallets can also be used.

Question 19

Does OmeShare control my wallet?

Accepted Answer

No. OmeShare never has control over your wallet. Wallet connections are read-only and use standard Web3 protocols. OmeShare cannot move funds, sign transactions on your behalf, or access your private keys. You retain full custody at all times.

Question 20

Can OmeShare move my funds?

Accepted Answer

No. OmeShare cannot move, transfer, or access your funds. OmeShare has no access to your private keys and cannot initiate transactions from your wallet. All transactions require your explicit approval through your wallet's interface.

Question 21

How do I disconnect my wallet?

Accepted Answer

Click the wallet button in the header or sidebar, then select 'Disconnect' from the dropdown menu. This removes the wallet connection from OmeShare but does not affect your wallet or funds. You can reconnect at any time.

Question 22

What blockchain networks are supported?

Accepted Answer

OmeShare currently supports Base (chain ID 8453) as the primary network for creator tokens. The platform also recognizes Ethereum (1), Polygon (137), and Arbitrum (42161) for wallet connections and balance display. Creator token features require switching to the Base network.

Question 23

Can OmeShare recover my lost wallet?

Accepted Answer

No. OmeShare cannot recover lost wallets, lost private keys, or lost seed phrases. Wallet recovery is entirely dependent on your wallet provider's recovery mechanisms. OmeShare recommends storing your seed phrase securely and never sharing it with anyone.

Question 24

How do I connect my wallet on mobile?

Accepted Answer

On mobile, OmeShare supports WalletConnect and deep-links to wallet in-app browsers. The recommended path is WalletConnect, which opens a QR or wallet selector so you can approve the connection from a mobile wallet app. For MetaMask or Coinbase Wallet on mobile, tapping the wallet button will deep-link to the wallet's in-app browser, where OmeShare can auto-connect using the injected provider. Make sure you have the wallet app installed.

Question 25

How do I switch blockchain networks?

Accepted Answer

OmeShare prompts you to switch networks when an action requires a specific chain. For creator token deployment, you need Base (chain ID 8453). When your wallet is on a different network, a 'Switch to Base' button appears. Clicking it sends a network-switch request to your wallet, which you must approve. You can also switch networks manually in your wallet app.

Question 26

What is a profile?

Accepted Answer

A profile on OmeShare represents a creator with a connected wallet. Profiles display public information such as display name, handle, bio, avatar, published Code Builds, and forum posts. Profiles are how other creators discover your work and connect with you.

Question 27

Why is my profile public?

Accepted Answer

OmeShare is a discovery and creation platform — profiles are public by design so that users can discover creators and their Code Builds. However, you control what information is displayed. Sensitive data such as private documents and integration credentials are never shown publicly.

Question 28

How do I update my profile?

Accepted Answer

You can update your display name, handle, bio, avatar, and social links from your profile settings. Changes are saved to your public profile and reflected immediately. You can also manage your published Code Builds and forum posts from your dashboard.

Question 29

Can individuals create profiles?

Accepted Answer

Yes. Anyone can create a profile by connecting a wallet and setting up a display profile. Individual creators, developers, designers, and hobbyists are all welcome on OmeShare.

Question 30

What are forum posts on a profile page?

Accepted Answer

The Forum tab on every public profile page is where the profile owner can post text, images, and videos to communicate with followers. Only the profile owner — verified by matching the connected wallet — can create posts. Visitors can view, heart, and report posts.

Question 31

How does OmeShare protect users?

Accepted Answer

OmeShare protects users through multiple layers: wallet-based identity verification, sandboxed Code Build runtime isolation, fraud monitoring, abuse reporting systems, and community moderation. Code Builds run in isolated iframes that cannot access OmeShare auth tokens, cookies, or user data. However, no system is completely secure — users must always conduct their own due diligence.

Question 32

How is my information stored?

Accepted Answer

OmeShare stores profile data, wallet addresses, Code Build sources, and published builds in Firebase databases. Private keys are never stored. Code Build source code is stored as written — OmeShare never rewrites your saved source. Device information (IP, browser) is collected for security and analytics purposes as described in the Privacy Policy.

Question 33

Does OmeShare custody funds?

Accepted Answer

No. OmeShare does not custody, hold, or manage any user funds. All funds remain in your wallet at all times. Creator token transactions, where available, are direct wallet-to-contract interactions. OmeShare never intermediates transactions.

Question 34

Can OmeShare access my wallet?

Accepted Answer

No. OmeShare cannot access your wallet. Wallet connections use standard Web3 protocols that keep private keys on your device. OmeShare receives only your public wallet address and can request transaction approvals — but every transaction requires your explicit approval through your wallet interface. OmeShare cannot sign transactions on your behalf.

Question 35

What happens if I lose my wallet?

Accepted Answer

If you lose access to your wallet, OmeShare cannot recover it, restore it, or transfer your profile to a new wallet. You would need to recover your wallet through your wallet provider's recovery process (seed phrase). If recovery is not possible, you can connect a new wallet, but your previous profile and published builds will not transfer automatically.

Question 36

How do I report fraud or suspicious activity?

Accepted Answer

You can report suspected fraud, impersonation, or policy violations through the Report Abuse page. All reports are reviewed by OmeShare's moderation team. Appropriate action is taken based on the findings, which may include content removal, account suspension, or reporting to authorities where legally required.

Question 37

Is Code Build code sandboxed?

Accepted Answer

Yes. All Code Build code runs in an isolated iframe on a different origin from the main OmeShare app. The sandbox allows scripts and same-origin (required for WebGL) but the iframe is NOT same-origin with OmeShare, so user code cannot access OmeShare auth tokens, cookies, localStorage, or the parent DOM. This is a core security boundary of the platform.

Question 38

What risks exist when using OmeShare?

Accepted Answer

Key risks include: (1) Creator tokens, where available, are volatile and may lose value; (2) Blockchain transactions are irreversible; (3) OmeShare does not guarantee profitability, project success, or profile legitimacy; (4) OmeShare provides creation and discovery tools, not guarantees; (5) Users are responsible for their own decisions; (6) Connected wallets remain user-controlled — OmeShare cannot recover lost wallets or reverse transactions. Users must verify information independently.

Question 39

Does OmeShare provide investment advice?

Accepted Answer

No. OmeShare does not provide financial, investment, tax, or legal advice. OmeShare provides creation tools, publishing, and discovery for Code Builds. Creator tokens, where available, are optional features. Users are solely responsible for evaluating any tokens, profiles, or blockchain transactions. Always consult a qualified professional for financial advice.

Question 40

What responsibilities belong to users?

Accepted Answer

Users are responsible for: (1) Conducting independent research and due diligence; (2) Understanding the risks of blockchain transactions; (3) Protecting their wallet credentials and seed phrases; (4) Evaluating any tokens or profiles before engaging; (5) Accepting responsibility for their decisions; (6) Complying with all applicable laws and regulations; (7) Reporting suspicious activity to OmeShare.

Question 41

Does OmeShare guarantee project success?

Accepted Answer

No. OmeShare does not guarantee the performance, value, legality, or success of any Code Build, profile, token, or creator listed on the platform. OmeShare provides creation and discovery tools to help users build and share their work, but these are tools only. Listings do not represent endorsements.

Question 42

Are published Code Builds endorsements?

Accepted Answer

No. OmeShare is a creation and discovery platform. Published Code Builds and profiles are user-generated content. Listings do not represent endorsements by OmeShare. OmeShare provides tools for creation and discovery but does not endorse any specific Code Build, token, profile, or creator. Users must conduct their own due diligence.

Question 43

What information is public vs. private?

Accepted Answer

Public information includes: display name, handle, bio, avatar, wallet address, published Code Builds, and forum posts. Private information includes: private keys (never stored), integration credentials, device information, and usage analytics. You control what public information is displayed on your profile.

Question 44

What are legal acceptances and why do I need them?

Accepted Answer

OmeShare requires users to explicitly accept legal agreements before connecting a wallet, creating tokens, or connecting integrations. These acceptances are stored and auditable. When legal documents are updated, users must re-accept the new version. This ensures users are always aware of the current terms and disclosures.

Frequently Asked Questions

Getting Started

CodeBuilds

Wallets

Profiles

Security

Legal & Risk Disclosure

More resources