[
"db5cee34a2a36010dde86a58971ab73583270485",{
"trx": {
"expiration": "2014-12-02T20:10:47",
"delegate_slate_id": null,
"operations": [{
"type": "define_delegate_slate_op_type",
"data": {
"slate": {
"supported_delegates": [
266,
317,
335,
371,
875,
1193,
4458,
4914,
[.....]
I'm looking into adding support for slates but it's surprisingly complicated. While yours is fairly straightforward, I currently would classify that transaction as an account update since that is what happens on the second operation of that transaction. However the "define_delegate_slate_op_type" is included quite often and I'm not really sure it's always the case of someone actually updating their slate. When you use the publish_slate command, does it immediately broadcast a transaction or does it get tacked on to the next transaction you make?
Here's an example of a slightly more complicated transaction from block #1097825:
"515eed9a038e04e24641669108ecfbb1ad070c31",
{
"trx" : {
"expiration" : "2014-11-25T02:32:22",
"delegate_slate_id" : null,
"operations" : [
{
"type" : "define_delegate_slate_op_type",
"data" : {
"slate" : {
"supported_delegates" : [
1,
6,
10,
59,
66,
266,
306,
334,
337,
338,
371,
795,
1193,
2151,
2156,
2158,
3324,
3649,
5464,
5570,
5589,
5722,
6006,
6212,
6582,
6939,
8679,
9810,
9811,
9870,
9871,
9878,
9879,
9880,
9882,
10082,
10155,
10171,
10173,
10174,
10206,
10207,
10213,
10214,
10243,
10287,
10288,
10323,
10425,
10510,
11028,
12313,
12314,
12316,
14020,
14758,
21537,
21539,
22353,
30739,
30919
]
}
}
},
{
"type" : "deposit_op_type",
"data" : {
"amount" : 38558728581,
"condition" : {
"asset_id" : 0,
"slate_id" : 3.158111506591852e+18,
"type" : "withdraw_signature_type",
"data" : {
"owner" : "BTS2FstgYG33DGa1WySZKUnL8r5rqTrfR9ts",
"memo" : {
"one_time_key" : "BTS5ZNTRbhprCCAnorSq65MGSmYN43xb3pSHXSMk1LaGn453DPADP",
"encrypted_memo_data" : "a7b76f8e863fdb02032482757907b1ed467994e886a527b75d6854a10730ff32a0a4219fa964fbee58f6968ce1d2846801357abb0c1af0459b93c4b4d62a0bce"
}
}
}
}
},
{
"type" : "define_delegate_slate_op_type",
"data" : {
"slate" : {
"supported_delegates" : [
1,
6,
10,
59,
66,
266,
306,
307,
317,
334,
335,
337,
338,
371,
795,
875,
1193,
2151,
2156,
2158,
3324,
3649,
4458,
4914,
5464,
5570,
5589,
5722,
6006,
6212,
6582,
6939,
8679,
9810,
9811,
9870,
9871,
9872,
9878,
9879,
9880,
9882,
9954,
10082,
10155,
10171,
10173,
10174,
10206,
10207,
10213,
10214,
10243,
10287,
10288,
10306,
10323,
10425,
10493,
10510,
11028,
11083,
11099,
12313,
12314,
12316,
13721,
14020,
14758,
16658,
21130,
21537,
21539,
21706,
22353,
23569,
23728,
30739,
30919
]
}
}
},
{
"type" : "withdraw_op_type",
"data" : {
"balance_id" : "BTSBHXs4ECfmUQTH7tKufTXAMpvB3UMD8987",
"amount" : 32887363825,
"claim_input_data" : ""
}
},
{
"type" : "withdraw_op_type",
"data" : {
"balance_id" : "BTSDMTbpf2Ym1d41vZYjx4PDoVWD62Vc6b2T",
"amount" : 1250374756,
"claim_input_data" : ""
}
},
{
"type" : "withdraw_op_type",
"data" : {
"balance_id" : "BTSDn8dJoeX7DS3eQe4kia1Dee1C9fhrtmHy",
"amount" : 1203985000,
"claim_input_data" : ""
}
},
{
"type" : "withdraw_op_type",
"data" : {
"balance_id" : "BTSFvedctmXoLXZR92443VsPoMcDEq4mGC2M",
"amount" : 1526035000,
"claim_input_data" : ""
}
},
{
"type" : "withdraw_op_type",
"data" : {
"balance_id" : "BTSGVFM5Eybt3Th1DVkndbZV1hUnkyspQUwT",
"amount" : 1549985000,
"claim_input_data" : ""
}
},
{
"type" : "withdraw_op_type",
"data" : {
"balance_id" : "BTSLaiCf1q2xqsrnBtf6CMkfL7UnWB6SVLXF",
"amount" : 65000000,
"claim_input_data" : ""
}
},
{
"type" : "withdraw_op_type",
"data" : {
"balance_id" : "BTSMJBRPBoGTtwvB39cdJBXtFVC8kq6RmxwM",
"amount" : 10000000,
"claim_input_data" : ""
}
},
{
"type" : "withdraw_op_type",
"data" : {
"balance_id" : "BTSP63x6Pc5drid61wd7wKLMh3Hz7RvjGus3",
"amount" : 66000000,
"claim_input_data" : ""
}
}
]
That transaction actually includes TWO define_delegate_slate_op_type operations, one with 61 delegates the other with 79 delegates. There are also 8 withdraw_op_type operations, none of which withdraw to an account like they normally do but to 8 different public keys.
The delegate account is identified nowhere, which I find strange, so there's no way for me to tell who actually published this slate. Basically, it's complicated.. Looking through the transactions I see a lot of transactions like this, so unless someone can explain how this all works I'm not sure I can properly add slates at the moment..
This is I guess a slate published by a non-delegate, guess I'll just ignore those for now. I would still like to know why there are two slate operations in there though.