[4] Proof of Contribution: Attribution (Request for Cores, RfCs)
Overview
Implementation
Data Structures
message ContributionType {
string name = 1;
string description = 2;
bool active = 3;
}
message ContributionTypes {
repeated ContributionType types = 1;
}
message AITensorRow {
string address = 1;
repeated uint64 contributions = 2;
}
message AITensor {
repeated AITensorRow tensor = 1;
bytes AI = 2;
}
message MsgCoreGrantApplication {
option (cosmos.msg.v1.signer) = "authority";
option (amino.name) = "spawn/x/brahma/MsgCoreGrantApplication";
string authority = 1 [(cosmos_proto.scalar) = "cosmos.AddressString"];
string requester = 2 [(cosmos_proto.scalar) = "cosmos.AddressString"];
uint64 core_allocation = 3;
string title = 4;
string description = 5;
int64 created_at_height = 6;
}
// MsgRequestForCore represents the actual request to issue new Core. Requester is expected to have been a Grantee on a previously approved CoreGrant.
// On execution, this message will trigger the issuance of new Cores in accordance with each ore listed in the AITensors provided. This will also
// update the referenced AI's state-tensors.
message MsgRequestForCore {
option (cosmos.msg.v1.signer) = "requester";
option (amino.name) = "spawn/x/brahma/MsgRequestForCore";
// Requester is the requester of this RequestForCore
string requester = 1 [(cosmos_proto.scalar) = "cosmos.AddressString"];
// AITensors determine the set of cores to be issued from this MsgRequestCore
repeated AITensor AITensors = 2;
}ContributionType
ContributionTypeAITensor
AITensorMsgCoreGrantApplication
MsgCoreGrantApplicationMsgRequestForCore
MsgRequestForCoreState
AITensors
CoreGrantApplications
State Transitions
MsgRequestForCore
MsgCoreGrantApplication
Last updated