From 5aa5c81a4249e04ad29d147272f4a3af0a1ece21 Mon Sep 17 00:00:00 2001 From: Pedro Gomes Date: Mon, 13 Feb 2023 13:35:51 +0100 Subject: [PATCH] Remove message max for Relay API --- docs/specs/servers/relay/relay-server-rpc.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/specs/servers/relay/relay-server-rpc.md b/docs/specs/servers/relay/relay-server-rpc.md index c1563b5ea..217f0e9cf 100644 --- a/docs/specs/servers/relay/relay-server-rpc.md +++ b/docs/specs/servers/relay/relay-server-rpc.md @@ -9,7 +9,7 @@ This document aims to create the JsonRpc contract between a client and a server. The following definitions are shared concepts across all JSON-RPC methods for the Relay API: - **topic** - (hex string - 32 bytes) a target topic for the message to be subscribed by the receiver. -- **message** - (utf8 string - variable - max 10,000 bytes) a plaintext message to be relayed to any subscribers on the topic. +- **message** - (utf8 string - variable) a plaintext message to be relayed to any subscribers on the topic. - **ttl** - (uint32 - 4 bytes) a storage duration for the message to be cached server-side in **seconds** (aka time-to-live). - **tag** - (uint32 - 4 bytes) a label that identifies what type of message is sent based on the rpc method used. - **id** - (hex string - 32 bytes) a unique identifier for each subscription targeting a topic.