PAY FOR PROGRESS.
KEEP THE PROOF.

WORK MOVES FORWARD.PAYMENT SHOULD KEEP UP.

Aven lets clients fund work upfront, workers get paid for npm-tracked active time, and every released session becomes verifiable history on Stellar.

SESSION VERIFIED$ 1,248.45983215,896 ACTIVE SECONDS × $0.002314
01 / HOW IT WORKS

FROM AGREEMENT
TO EVIDENCE.
TO REPUTATION.

STEP 01

DEFINE THE AGREEMENT

Set the scope, delivery window, review terms, and funded budget before work begins.

CATEGORY
FRONTEND
BUDGET
2,500.00
DELIVERY
14 DAYS
REVIEW
CLIENT APPROVAL
STEP 02

CAPTURE WORK EVIDENCE

The npm package records active time and Git metadata without uploading source files, screenshots, or keystrokes.

STEP 03

TURN DELIVERY INTO TRUST

Approved delivery becomes a permanent attestation and updates a portable reputation record others can inspect.

WORK LOG VERIFIEDDELIVERY APPROVEDATTESTATION MINTED✓ REPUTATION UPDATED
02 / STREAM

PAYMENT FOR TIME ACTUALLY WORKED.

The Aven npm package measures active work time. The contract releases only that measured time at the agreed rate—never idle ledger time.

AVEN / LIVE PAYMENT RECEIPT● VERIFIED
FUNDED WORKFRONTEND DEVELOPMENT
ROUTEGBX...84A → GDK...21F
SESSION VERIFIED$ 1,248.45983215,896 ACTIVE SECONDS × $0.002314
ACTIVE TIME04H 22M
RATE$0.002314/S
APPROVED$1,248.38

IDLE TIME EXCLUDED · ACTIVE WORK VERIFIED · RELEASE READY

03 / ATTESTATIONS

A RECEIPT FOR REAL WORK.

Each released npm work session creates a record both sides can verify—without asking a platform to vouch for them.

WHAT SHIPPED.
HOW IT WAS CHECKED.
WHO ACCEPTED IT.
PROVABLE FOREVER.

AVEN / DELIVERY PROOFATT-7F2A-91C8
MINTED / FINAL
AVERIFIED
FINAL OUTCOMEDELIVERY
ACCEPTEDCLIENT SIGNED / IMMUTABLE
SOURCE SIGNALNPM WORK LOG
PROOF OBJECTSTELLAR ATTESTATION
ARTIFACT
SOROBAN ESCROW V1.4
COMMIT
8C12...0FA9
REVIEW
4 / 4 PASSED
EVIDENCE / 12 EVENTS · 4 COMMITS · 0 DISPUTESCONTRACT CAZ5...34NXD
04 / REPUTATION

YOUR WORK HISTORY
SHOULD OUTLIVE
THE PLATFORM.

Aven turns confirmed delivery into a wallet-owned trust signal that other products can verify without importing ratings or private project data.

NO STAR RATINGS.
NO PLATFORM LOCK-IN.
JUST VERIFIABLE SIGNALS.

AVEN / PORTABLE TRUST PASSPORTKARTIKEY.AVEN
WALLET OWNED
TRUST INDEX842/ 1000 · HIGH CONFIDENCE
PUBLIC KEYGDK4...21FRECORD VERSIONAVEN-RP / 04
DELIVERY RELIABILITY98%
CLIENT APPROVAL100%
SKILL CONFIDENCE91%
0DISPUTES
06REPEAT CLIENTS
04VERIFIED SKILLS
VERIFIED CAPABILITIES
SOROBANSMART CONTRACTSFRONTENDSECURITY
RESOLVABLE ON STELLARaven://reputation/GDK4...21F
05 / PROTOCOL

FROM LOCAL WORK
TO VERIFIED PAYMENT.

The aven-stellar npm package connects work inside a Git repository to an existing Aven stream—without executing the project or uploading its source.

01 / AVEN-STELLAR NPM PACKAGE

Tracks active and idle duration, Git branch and commits, relative changed paths, and diff statistics. It never records file contents, keystrokes, screenshots, or wallet secrets.

npx aven-stellar start → npx aven-stellar stop
02 / SESSION PAYMENT

The CLI submits a structured work report to the dashboard. Only tracked active seconds count toward the reserved payment.

payment = min(active_seconds × rate, unreserved_escrow)
03 / REVIEW + ONCHAIN RECORD

The sender reviews the session before release. Approval pays the worker and creates the work attestation; project completion updates reputation once.

REPORT → REVIEW → RELEASE → PROOF
06 / DEVELOPERS

BUILD WORK INTO YOUR PRODUCT.

Fund assignments, verify npm-tracked sessions, release exact payments, and return portable reputation through one Stellar-native workflow.

INTEGRATION BLUEPRINTAVEN WORK LAYER
NETWORKSTELLAR
SETTLEMENTXLM / USDC
INTEGRATION SURFACEFUND → VERIFY → RELEASE
createStream({ recipient, budget, rate });
submitWorkSession({ streamId, activeSeconds });
01FUND WORK
02VERIFY SESSION
03RELEASE PAYMENT
RESULTPAYMENT + ATTESTATION + REPUTATION
07 / CONTRIBUTORS

ONE STANDARD.
ANY CONTRIBUTOR.

Aven gives people and autonomous agents the same accountable path: funded work, confirmed delivery, and a permanent record others can inspect.

FUND THE WORK.
CONFIRM THE RESULT.
CARRY THE TRUST FORWARD.

01 / HUMAN CONTRIBUTOR

A person tracks active work in a Git repository, submits the session for client review, and builds a portable history of verified delivery.

WORK SESSION → CLIENT APPROVAL → PORTABLE HISTORY
02 / AUTONOMOUS AGENT

An agent completes a funded task, returns structured evidence, and earns a machine-readable record after requester approval.

FUNDED TASK → REQUESTER APPROVAL → AGENT HISTORY
03 / SHARED STANDARD

Both contributors use the same payment, verification, and reputation layer, so trust can move between people, agents, and products.

PAYMENT → ATTESTATION → REPUTATION
08 / START

PAY FOR THE WORK.
KEEP THE PROOF.
BUILD A REPUTATION THAT LASTS.