What feature is it?
Support for 'unstaking' and 'burn' actions in the VSL network
What problem does this feature solve?
Currently, unstaking transactions are not being parsed correctly in the VSL network. For instance, transaction 0xa48ba3b09e does not include the 'unstaking' and 'burn' actions. Here is the current parsing result: Parsing Result.
{
"data": {
"id": "0xa48ba3b09e87380b05f1205bf515a48fd66791ba25d0152e035b485efa7c3118",
"owner": "0x28F14d917fddbA0c1f2923C406952478DfDA5578",
"network": "vsl",
"index": 0,
"from": "0x827431510a5D249cE4fdB7F00C83a3353F471848",
"to": "0x28F14d917fddbA0c1f2923C406952478DfDA5578",
"tag": "collectible",
"type": "mint",
"fee": {
"amount": "2657141338975350",
"decimal": 18
},
"calldata": {
"function_hash": "0xbcdd4190"
},
"total_actions": 4,
"actions": [
{
"tag": "collectible",
"type": "mint",
"from": "0x827431510a5D249cE4fdB7F00C83a3353F471848",
"to": "0x0000000000000000000000000000000000000000",
"metadata": {
"address": "0x849f8F55078dCc69dD857b58Cc04631EBA54E4DE",
"id": "9257",
"value": "1",
"name": "Open Chips",
"symbol": "Chips",
"standard": "ERC-721"
},
"related_urls": [
"https://scan.rss3.io/tx/0xa48ba3b09e87380b05f1205bf515a48fd66791ba25d0152e035b485efa7c3118"
]
},
{
"tag": "collectible",
"type": "mint",
"from": "0x827431510a5D249cE4fdB7F00C83a3353F471848",
"to": "0x0000000000000000000000000000000000000000",
"metadata": {
"address": "0x849f8F55078dCc69dD857b58Cc04631EBA54E4DE",
"id": "9258",
"value": "1",
"name": "Open Chips",
"symbol": "Chips",
"standard": "ERC-721"
},
"related_urls": [
"https://scan.rss3.io/tx/0xa48ba3b09e87380b05f1205bf515a48fd66791ba25d0152e035b485efa7c3118"
]
},
{
"tag": "collectible",
"type": "mint",
"from": "0x827431510a5D249cE4fdB7F00C83a3353F471848",
"to": "0x0000000000000000000000000000000000000000",
"metadata": {
"address": "0x849f8F55078dCc69dD857b58Cc04631EBA54E4DE",
"id": "9259",
"value": "1",
"name": "Open Chips",
"symbol": "Chips",
"standard": "ERC-721"
},
"related_urls": [
"https://scan.rss3.io/tx/0xa48ba3b09e87380b05f1205bf515a48fd66791ba25d0152e035b485efa7c3118"
]
},
{
"tag": "collectible",
"type": "mint",
"from": "0x827431510a5D249cE4fdB7F00C83a3353F471848",
"to": "0x0000000000000000000000000000000000000000",
"metadata": {
"address": "0x849f8F55078dCc69dD857b58Cc04631EBA54E4DE",
"id": "9260",
"value": "1",
"name": "Open Chips",
"symbol": "Chips",
"standard": "ERC-721"
},
"related_urls": [
"https://scan.rss3.io/tx/0xa48ba3b09e87380b05f1205bf515a48fd66791ba25d0152e035b485efa7c3118"
]
}
],
"direction": "in",
"success": true,
"timestamp": 1728121445
},
"meta": {
"totalPages": 1
}
}
Additional description
No response
This is not a duplicated feature request or new worker proposal
What feature is it?
Support for 'unstaking' and 'burn' actions in the VSL network
What problem does this feature solve?
Currently, unstaking transactions are not being parsed correctly in the VSL network. For instance, transaction 0xa48ba3b09e does not include the 'unstaking' and 'burn' actions. Here is the current parsing result: Parsing Result.
{ "data": { "id": "0xa48ba3b09e87380b05f1205bf515a48fd66791ba25d0152e035b485efa7c3118", "owner": "0x28F14d917fddbA0c1f2923C406952478DfDA5578", "network": "vsl", "index": 0, "from": "0x827431510a5D249cE4fdB7F00C83a3353F471848", "to": "0x28F14d917fddbA0c1f2923C406952478DfDA5578", "tag": "collectible", "type": "mint", "fee": { "amount": "2657141338975350", "decimal": 18 }, "calldata": { "function_hash": "0xbcdd4190" }, "total_actions": 4, "actions": [ { "tag": "collectible", "type": "mint", "from": "0x827431510a5D249cE4fdB7F00C83a3353F471848", "to": "0x0000000000000000000000000000000000000000", "metadata": { "address": "0x849f8F55078dCc69dD857b58Cc04631EBA54E4DE", "id": "9257", "value": "1", "name": "Open Chips", "symbol": "Chips", "standard": "ERC-721" }, "related_urls": [ "https://scan.rss3.io/tx/0xa48ba3b09e87380b05f1205bf515a48fd66791ba25d0152e035b485efa7c3118" ] }, { "tag": "collectible", "type": "mint", "from": "0x827431510a5D249cE4fdB7F00C83a3353F471848", "to": "0x0000000000000000000000000000000000000000", "metadata": { "address": "0x849f8F55078dCc69dD857b58Cc04631EBA54E4DE", "id": "9258", "value": "1", "name": "Open Chips", "symbol": "Chips", "standard": "ERC-721" }, "related_urls": [ "https://scan.rss3.io/tx/0xa48ba3b09e87380b05f1205bf515a48fd66791ba25d0152e035b485efa7c3118" ] }, { "tag": "collectible", "type": "mint", "from": "0x827431510a5D249cE4fdB7F00C83a3353F471848", "to": "0x0000000000000000000000000000000000000000", "metadata": { "address": "0x849f8F55078dCc69dD857b58Cc04631EBA54E4DE", "id": "9259", "value": "1", "name": "Open Chips", "symbol": "Chips", "standard": "ERC-721" }, "related_urls": [ "https://scan.rss3.io/tx/0xa48ba3b09e87380b05f1205bf515a48fd66791ba25d0152e035b485efa7c3118" ] }, { "tag": "collectible", "type": "mint", "from": "0x827431510a5D249cE4fdB7F00C83a3353F471848", "to": "0x0000000000000000000000000000000000000000", "metadata": { "address": "0x849f8F55078dCc69dD857b58Cc04631EBA54E4DE", "id": "9260", "value": "1", "name": "Open Chips", "symbol": "Chips", "standard": "ERC-721" }, "related_urls": [ "https://scan.rss3.io/tx/0xa48ba3b09e87380b05f1205bf515a48fd66791ba25d0152e035b485efa7c3118" ] } ], "direction": "in", "success": true, "timestamp": 1728121445 }, "meta": { "totalPages": 1 } }Additional description
No response
This is not a duplicated feature request or new worker proposal