`signevent` does not have `proof` field

[randomlogin]

signevent results do not include proof field, thus an event cannot be connected to a root anchor (and therefore to a space).

Example:

minimal_event:

{
  "created_at": 1751378144,
  "kind": 12345,
  "tags": [
    [
      "space",
      "@cosmos"
    ]
  ],
  "content": ""
}

$ space-cli --chain regtest signevent @cosmos --input minimal_event

{
  "id": "0d9f6f0a12a44a8b52dab684479ecee7d0357bc8ad2a0d823d6ae9596a3f4743",
  "pubkey": "4e6068ae6a082ac3f084e7f026640231e483fff449aaa69707b0d439c81a253c",
  "created_at": 1751378144,
  "kind": 12345,
  "tags": [
    [
      "space",
      "@cosmos"
    ]
  ],
  "content": "",
  "sig": "79b1e07b34fa8471e4ee6b51e0bcfd218fb170b8e935b9100be1b916a043e09ca173bb610ac5c47d7f48acc0fb7041709c5d1a4a06bfa4c469ecf45a59ed4474"
}

Perhaps we can remove a check here:

spaces/client/src/bin/space-cli.rs

Lines 418 to 420 in 646c312

	if anchor {
	result = self.add_anchor(result, most_recent).await?
	}

Compare to a result of signzone:

{
  "id": "fd5e5f41c7cac3ee5f2f0cebfeb02ac4b7748e186de487e3ebf74ea8d2ac7fd3",
  "pubkey": "4e6068ae6a082ac3f084e7f026640231e483fff449aaa69707b0d439c81a253c",
  "created_at": 1751376708,
  "kind": 871222,
  "tags": [
    [
      "space",
      "@cosmos"
    ]
  ],
  "content": "AAAoAAAAAAAAAQAAB0Bjb3Ntb3MAAAEAAgAADhAABH8AAAQ=",
  "sig": "d602c1335c97cacc0ecbb48b5817155bd58250e48353e7b52622164c8f799b4ae5d843fa63ca53122bd82c0cb5be70d0a373e94a67afabeb559c849b981d47d9",
  "proof": "AQEAAtc4h8Lse5WiUwgciQziVvyesBWbkLvwBpWwQxkOViVCAQABAALnTIkfEDsxip3Vw0szL/ETJJdwXG2kZ8xSijhsuV1aDABWEAMsVSWKRLVSxkiVq7B9jTwtgc/IaNf+2xiEs+4DqwA0AQEGY29zbW9zAfvT1AD7mgIiUSBOYGiuaggqw/CE5/AmZAIx5IP/9EmqppcHsNQ5yBolPAJfm/Sw9kwFpkzxX+0s037PSfrYEg5PLg2sGk0wOnpDiw=="
}

It's important, beacuse fabric would not return events 'via space' unless they have a proof.

[randomlogin]

UPD: actually one can add a boolean -a or --anchor flag

$ space-cli --chain regtest signevent @cosmos --input minimal_event -a 
{
  "id": "0d9f6f0a12a44a8b52dab684479ecee7d0357bc8ad2a0d823d6ae9596a3f4743",
  "pubkey": "4e6068ae6a082ac3f084e7f026640231e483fff449aaa69707b0d439c81a253c",
  "created_at": 1751378144,
  "kind": 12345,
  "tags": [
    [
      "space",
      "@cosmos"
    ]
  ],
  "content": "",
  "sig": "12512b5bba185d51b06c0cac0fdc9e7fb907aa407532b3aa1b9b58e6a5c57afd0b11ef1c86cd804fd5767194e43b5aaea26fd425b2376fb37c8161528261a070",
  "proof": "AQEAAtc4h8Lse5WiUwgciQziVvyesBWbkLvwBpWwQxkOViVCAQABAALnTIkfEDsxip3Vw0szL/ETJJdwXG2kZ8xSijhsuV1aDABWEAMsVSWKRLVSxkiVq7B9jTwtgc/IaNf+2xiEs+4DqwA0AQEGY29zbW9zAfvT1AD7mgIiUSBOYGiuaggqw/CE5/AmZAIx5IP/9EmqppcHsNQ5yBolPAJfm/Sw9kwFpkzxX+0s037PSfrYEg5PLg2sGk0wOnpDiw=="
}

what do you think about enabling it by default (because without it we just make a usual nostr signed event, which is not the aim of spaced)?

[Ximik]

I think we shouldn't have proof as a separate field, because there are no events in use with have fields not defined in NIP-1.

I see 3 possible options

1. Add the proof to the space tag

{
  "tags": [
    [ "space",  "<space>", "<proof>"]
  ],
  "content": "<zone data>"
}

2. Put proof into content

{
  "kind": 12345
  "tags": [
     ["space", "<space>", "<zone data>"]
  ],
  "content": "<proof>"
}

3. Make a separate proof event similar to NIP-3

{
  "kind": 12345
  "tags": [
    ["e", "<zone-data-event-id>", "<relay-url>"]
  ],
  "content": "<proof>"
}

[randomlogin]

I think I like the first one most.

 {
  ...,
  "tags": [
    [ "space",  "<space>", "<proof>"]
  ],
  "content": "<content>"
}

[Ximik]

I think we need option 3 AND option 1 or 2 (or some variation).

1. Option 1 / 2 should be used to create an event with pubkey == space.pubkey (e.g. zone data event)
2. Option 3 should be used to sign an event with pubkey == author.pubkey (e.g. nostr post or IM).

Also maybe there is a need for the event with one-time pubkey (similar to gift wrappers) if we want to publish zone data without being the space owners (e.g. for relay resolve).