> **Can't find what you're looking for?** Use `search_docs` on the docs MCP server at `https://docs.prividium.com/api/mcp` to find what you need. > > **Have feedback?** Use `submit_feedback` on the same MCP server. We publish release notes when a Prividium release is cut. Your environment may receive the release later. Ask your administrator about its rollout schedule. ## v1.313.0 — November 5, 2026 ### Improvements * After you create a contract in the admin panel, its Function Permissions tab opens, so you can assign permissions right away. * Policy approvals show the decoded contract call: the contract, the method and each named argument. * API-key errors on RPC say what is wrong. A malformed key reports the expected format, and repeated `X-API-Key` headers are reported. Unknown or revoked keys still get one generic error. * Organization admins see API-key authentication failures for their organization's M2M applications. The admin panel shows the last IP each key was used from. ### Fixes * When a transaction send times out while waiting for inclusion, `eth_sendRawTransaction` returns the transaction hash instead of an error. The transaction is already in the mempool, so do not resend it. * Node errors that reveal no other user's data, such as "block not found" or "block range too large", reach the client with their original code and text. * An upstream RPC call that does not answer within 30 seconds returns `Upstream RPC request timed out` instead of hanging. * Editing a contract template permission keeps its organization scope. ### Upgrade notes * An RPC batch holds at most 20 operations by default, and each operation counts against the caller's rate limit. Split larger batches into several requests. * Requests that are not yet authenticated are rate-limited per IP address. * Template permissions shared outside their organization are set back to organization-only during the upgrade. Share them again where that was intended. * The admin and user panels serve their files from their own containers by default. ## v1.312.0 — October 29, 2026 ### Fixes * Requests with very large or malformed encoded call arguments are rejected with a clear error before processing. * Explicit call blocks now also apply to contract calls made with very short calldata (fallback calls). ### Upgrade notes * Permission checks now enforce limits on encoded call arguments: 1 MiB of raw calldata, 256 KiB of decoded bytes, 4,096 decoded values, and 32 levels of nesting. Calls over these limits were previously accepted and are now rejected. The limits are generous; no action is needed for normal usage. ## v1.311.1 — October 22, 2026 ### Fixes * Contract function permissions accept function signatures written without the `function` keyword. A signature that cannot be parsed returns a clear error. * Prividium rejects TLS certificates issued through recently compromised intermediate certificate authorities when it fetches keys from a sign-in provider. ## v1.311.0 — October 15, 2026 ### Fixes * An address configured as public, such as the chain's fee collector, shows its real balance and nonce to its owner, so collected fees can be withdrawn. Other users still see a zero balance. ### Upgrade notes * With `NODE_ENV=production`, the API refuses to start when `SIWE_HMAC_SECRET` contains the example value from `.env.example`. Set a random secret before you upgrade. ## v1.310.0 — October 9, 2026 ### Improvements * The admin panel groups role permissions by feature and offers permissions only for features enabled in the deployment. ### Fixes * Prividium checks native transfers against the signed-in user's wallet and authorizes simulations against the user's permissions. * The RPC accepts legacy, EIP-2930, and EIP-1559 transactions and rejects other types. * Prividium rejects very large JSON-RPC requests before processing. ### Upgrade notes * `eth_call` and `eth_estimateGas` now require a signed-in session. * If an application asks users to sign typed data, an administrator must grant `eip712Domain()` permission on the relevant contracts. * JSON-RPC batches are limited to 1,000 requests. Method names and string IDs are limited to 128 characters. ## v1.309.0 — October 2, 2026 ### Improvements * “Login with Prividium” gives each connected application its own session. Users can see these sessions in the User Panel. * Machine-to-machine (M2M) applications can now check their own identity and permissions through the API. ### Fixes * `eth_call` and `eth_estimateGas` reject a `from` address that the caller does not own. Calls without `from` continue to work. ### Upgrade notes * Signing out of the User Panel does not end application sessions. Users can select “Revoke All Others” to end them early. ## v1.307.0 — September 24, 2026 ### Improvements * Audit logs record changes to API applications, their roles, and organization default roles, including the before and after state. * Documentation links in the panels open the hosted Prividium docs, and the admin panel links to the API reference. ### Fixes * The Event Permissions tab shows a contract's rules regardless of address casing, and newly added rules appear without a refresh. * The User Panel reports when Add Network leaves a wallet connected to the plain RPC URL instead of its tokenized URL. * Fixed intermittent failed or slow requests.