mppi-protocol 0.1.2__tar.gz → 0.1.3__tar.gz

{mppi_protocol-0.1.2 → mppi_protocol-0.1.3}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.5
 Name: mppi-protocol
-Version: 0.1.2
+Version: 0.1.3
 Summary: Shared MPPI wire bindings and exact payment primitives
 License-Expression: Apache-2.0
 License-File: LICENSE
@@ -23,6 +23,24 @@ The implementation validates catalogs and report transitions, computes exact
 amounts, signs and verifies fixed-session proofs, prepares contract calls and
 checks canonical receipt evidence. Version `0.1.1` also supplies shared discovery
 validation and the Circle Agent Wallet adapter used by both Python roles.
+Version `0.1.3`, used by `mppi-agent` 0.1.4, keeps HTTP connections alive and
+sends a step's reads as one JSON-RPC batch (`HttpJsonRpc.call_many`), and treats
+a read timeout as transient. It adds:
+
+- `ChainReader.latest`, a one-request snapshot through Multicall3, and the
+  batched steps `observe` and `session_at`; on final networks
+  (`DeploymentProfile.instant_finality`) receipts alone prove operations;
+- `ChainReader.funding`, which checks a funding signature as USDC does;
+- `ChainFollower.follow`, `refresh_at`, `confirm`, `confirmed_readiness` and
+  `on_refresh_failure`, for requests that read no chain;
+- `NotSubmittedError` and `OperationResult.cause`.
+
+Three changes are not additive. `OpeningEvidence` and `ClosingEvidence` carry the
+proving `observation` instead of a `Block`, and `ChainReader.agent_wallet` takes
+that observation. The Circle adapter pins no account code:
+`CircleAgentWallet(chain=..., address=..., checkpoint_path=...)` replaces the
+`wallet` and `implementation` pins, and its journal is format 2 (format 1 still
+loads).
 Version `0.1.2`, used by `mppi-agent` 0.1.3, adds bounded repeats of transient
 read-only JSON-RPC calls, lag-tolerant chain following
 (`ChainLagError`, `last_refresh_failure`), `HookError.detail` and

{mppi_protocol-0.1.2 → mppi_protocol-0.1.3}/README.md

@@ -8,6 +8,24 @@ The implementation validates catalogs and report transitions, computes exact
 amounts, signs and verifies fixed-session proofs, prepares contract calls and
 checks canonical receipt evidence. Version `0.1.1` also supplies shared discovery
 validation and the Circle Agent Wallet adapter used by both Python roles.
+Version `0.1.3`, used by `mppi-agent` 0.1.4, keeps HTTP connections alive and
+sends a step's reads as one JSON-RPC batch (`HttpJsonRpc.call_many`), and treats
+a read timeout as transient. It adds:
+
+- `ChainReader.latest`, a one-request snapshot through Multicall3, and the
+  batched steps `observe` and `session_at`; on final networks
+  (`DeploymentProfile.instant_finality`) receipts alone prove operations;
+- `ChainReader.funding`, which checks a funding signature as USDC does;
+- `ChainFollower.follow`, `refresh_at`, `confirm`, `confirmed_readiness` and
+  `on_refresh_failure`, for requests that read no chain;
+- `NotSubmittedError` and `OperationResult.cause`.
+
+Three changes are not additive. `OpeningEvidence` and `ClosingEvidence` carry the
+proving `observation` instead of a `Block`, and `ChainReader.agent_wallet` takes
+that observation. The Circle adapter pins no account code:
+`CircleAgentWallet(chain=..., address=..., checkpoint_path=...)` replaces the
+`wallet` and `implementation` pins, and its journal is format 2 (format 1 still
+loads).
 Version `0.1.2`, used by `mppi-agent` 0.1.3, adds bounded repeats of transient
 read-only JSON-RPC calls, lag-tolerant chain following
 (`ChainLagError`, `last_refresh_failure`), `HookError.detail` and

{mppi_protocol-0.1.2 → mppi_protocol-0.1.3}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "hatchling.build"
 
 [project]
 name = "mppi-protocol"
-version = "0.1.2"
+version = "0.1.3"
 license = "Apache-2.0"
 license-files = ["LICENSE"]
 description = "Shared MPPI wire bindings and exact payment primitives"

{mppi_protocol-0.1.2 → mppi_protocol-0.1.3}/src/mppi_protocol/capabilities.py

@@ -51,7 +51,20 @@ class FundingAuthorization:
             )
 
 
+class NotSubmittedError(RuntimeError):
+    """A wallet adapter's own durable record proves the call never reached the
+    wallet service: nothing was submitted, so the same call may be sent again.
+
+    Raise it only with that proof. Any other failure leaves the outcome unknown.
+    """
+
+
 class TransactionWallet(Protocol):
+    """A wallet adapter's transactions. ``execute`` sends ``call`` once from
+    ``address`` with zero native value and durably binds ``operation_ref`` to
+    it first; ``reconcile`` reports that same submission and never sends.
+    """
+
     @property
     def address(self) -> bytes: ...
 
@@ -61,6 +74,21 @@ class TransactionWallet(Protocol):
 
 
 class FundingWallet(TransactionWallet, Protocol):
+    """An agent's funding wallet from any provider, behind a thin adapter.
+
+    ``sign_funding_authorization`` returns bytes USDC accepts for exactly that
+    authorization from ``address``: an ECDSA signature for an account without
+    code, or bytes its ERC-1271 isValidSignature accepts. Before submitting
+    funding, the agent checks them and that its ERC-8004 agent id binds
+    ``address``. No wallet implementation or version is pinned.
+
+    A wallet whose service creates the signature when it executes declares an
+    optional ``signs_at_execute = True``: ``sign_funding_authorization`` then
+    returns a placeholder that ``execute`` replaces. The agent neither verifies
+    nor simulates the placeholder; it still checks the agent-id binding, and
+    USDC verifies the real signature on chain.
+    """
+
     def sign_funding_authorization(self, authorization: FundingAuthorization) -> bytes: ...