Use Proto Types in storage instead of bytes

[MitchTurner]

Linked Issues/PRs

followup to feedback from #3100

Description

Checklist

• Breaking changes are clearly marked as such in the PR description and changelog
• New behavior is reflected in tests
• The specification matches the implemented behavior (link update PR if changes are needed)

Before requesting review

• I have reviewed the code myself
• I have created follow-up issues caused by this PR and linked them here

After merging, notify other teams

[Add or remove entries as needed]

• Rust SDK
• Sway compiler
• Platform documentation (for out-of-organization contributors, the person merging the PR will do this)
• Someone else?

[mchristopher]

I think remote should be an object so it's more flexible going forward. My initial thought it that it would look like this:

message RemoteBlockResponse {
  string path = 1;
  oneof config {
    RemoteBlockConfigS3 s3 = 2;
    RemoteBlockConfigHTTP http = 3;
  }
}

message RemoteBlockConfigS3 {
  string region = 1;
  string bucket = 2;
  bool requester_pays = 3;
  optional endpoint = 4;
}

message RemoteBlockConfigHTTP {
  string endpoint = 1;
  optional map<string, string> headers = 2;
}

[MitchTurner]

Cool. Makes sense to me.

[cursor]

Bug: Transaction Serialization Fails for Multiple Types

The proto_tx_from_tx function incompletely serializes transactions. Non-Script transaction types (Create, Mint, Upgrade, Upload, Blob) are serialized as empty ProtoTransaction messages, losing all their data. For Script transactions, inputs, outputs, and metadata fields are hardcoded to empty values, resulting in critical data loss. This leads to corrupted or unusable transaction data in the protobuf representation.

Additional Locations (1)

• crates/services/block_aggregator_api/proto/api.proto#L146-L154

 

[cursor]

Bug: Generic Block Type Mismatch in Subscription

The NewBlockSubscription variant in BlockAggregatorQuery and the new_block_subscriptions field in the BlockAggregator struct now use a generic Block type. This creates a type mismatch, as the NewBlock struct (which wraps a ProtoBlock) appears to be the intended payload for new block notifications, but the Sender types now expect Blocks::Block directly.

Additional Locations (1)

• crates/services/block_aggregator_api/src/lib.rs#L137-L140