Devnet

Protocol Address 6PnB...FtT2

Period Loading...Sale Loading...
Acceptable use policy

Acceptable use for eeteel

This policy defines prohibited behavior, expected conduct, and enforcement boundaries for Share Economy Protocol interfaces and related services. App-level enforcement does not reverse finalized on-chain outcomes.

Last updated: 2026-03-11Terms of serviceRisk disclosure
Policy scope

What this governs

This policy applies to use of eeteel web interfaces, related operational services, and public-facing protocol tooling.

  • Share dashboard sessions and wallet-connected interfaces.
  • Public APIs, indexing-backed views, and protocol inspection surfaces.
  • Support, policy, and abuse-reporting channels.
Boundary conditions

What this does not govern

Some outcomes are controlled by blockchain finality and wallet custody rather than app-level moderation.

  • Non-custodial wallet ownership and private key management.
  • Reversal of finalized on-chain purchases, stakes, or claims.
  • External project quality, token value, or legal characterization.
Prohibited use

Behavior that is not allowed

The following categories can lead to warning, suspension, or permanent termination.

Prohibited

Illegal finance and sanctions violations

Illegal value-transfer or sanctions-evasion activity is not allowed.

  • Fraud, money laundering, terrorist financing, or knowingly facilitating these acts.
  • Sanctions evasion or routing activity through prohibited jurisdictions.
  • Using eeteel interfaces to conceal source of funds or beneficial ownership.
Prohibited

Protocol-state deception

Misrepresentation of protocol status or funding intent is prohibited.

  • Falsely representing a distribution as funded when it is not.
  • Misleading participants about claim readiness or stake status.
  • Presenting unsupported assets or routes as protocol-approved distributions.
Prohibited

Interface and claim-flow abuse

Do not abuse protocol interfaces or workflow assumptions.

  • Spamming repeated claim attempts to pressure app infrastructure or users.
  • Coordinated misuse of interface flows to create misleading activity signals.
  • Attempts to bypass visible protocol rules through deceptive UI or social behavior.
Prohibited

Platform abuse and security attacks

Do not harm service availability, user safety, or trust surfaces.

  • Credential stuffing, phishing, malware delivery, or social engineering.
  • Unauthorized scraping, API abuse, or denial-of-service behavior.
  • Attempts to bypass authentication, authorization, or rate limits.
Protocol examples

Examples of unacceptable behavior

Concrete cases that violate this policy in Share Economy Protocol workflows.

Behavior

Advertising a distribution as claimable before the funded vault actually contains the advertised asset.

Why prohibited

Misleads participants about protocol state and claim readiness.

Behavior

Impersonating the project team or support in order to obtain wallet signatures or secret recovery data.

Why prohibited

Creates direct wallet-compromise risk and user harm.

Behavior

Automating repeated high-frequency claim or dashboard requests to degrade service reliability.

Why prohibited

Harms availability for legitimate users and abuses shared infrastructure.

Behavior

Knowingly publishing false instructions that tell users wallet shares are automatically claim-ready.

Why prohibited

Misrepresents protocol mechanics and can cause unsafe or wasteful user actions.

Enforcement

How policy enforcement works

Actions are proportional to severity, recurrence, and operational risk.

  • Issue warnings and request corrective action.
  • Temporarily rate-limit, suspend, or disable app-level access.
  • Permanently terminate access in severe or repeated cases.
  • Preserve records and report activity where required by applicable law.
Finality reminderEnforcement occurs at the application and service level. It does not alter on-chain data or reverse finalized protocol actions.
Expected conduct

Allowed and encouraged behavior

These practices improve safety and clarity for participants and funders.

  • Describe shares, stake, and claim readiness truthfully.
  • Use explorer links and transparency surfaces when discussing funded assets or protocol state.
  • Communicate distribution details clearly if funding a vault or announcing a claimable asset.
  • Protect credentials, verify wallet actions, and report abuse promptly.
Questions or reports

Report abuse or get clarification

Start with self-service guidance. If still blocked, contact support with a clear incident summary.

Related documents