Code: [ [ "proposal", { "end_epoch": 1547183994, "name": "jack-sparrow-new-ship", "payment_address": "yYe8KwyaUu5YswSYmB3q3ryx8XTUu9y7Ui", "payment_amount": 49, "start_epoch": 1521429194, "type": 1, "url": "https://www.dashcentral.org/black-pearl" } ] ]

Code: { "end_epoch": 1547183994, "name": "jack-sparrow-new-ship", "payment_address": "yYe8KwyaUu5YswSYmB3q3ryx8XTUu9y7Ui", "payment_amount": 49, "start_epoch": 1521429194, "type": 1, "url": "https://www.dashcentral.org/black-pearl" }

Sentinel v1.3.0 is now released! Please update your MNs per the usual method (cd /path/to/sentinel && git pull).edit: To clarify, allshould be updated to this version.edit2: Link to Sentinel on GitHub: https://github.com/dashpay/sentinel This release includes optimizations to how governance objects are represented in memory and handled in Sentinel, and (along with changes released in DashCore v12.3) allows for a newer, simpler JSON format governance objects.If you are a developer of special tools like DashCentral or DashNexus, some other action could be required, so please read on.Specifically, the multi-dimensional array and un-necessary string field are removed, leaving only the core JSON Object to be parsed and processed. This can affect how 3rd party tools parse governance objects.To demonstrate, take the example for a proposal to buy Jack Sparrow a new ship (ahem,Jack Sparrow, sorry...):Legacy format:New simplified format:You'll notice that the gobject type string (1st of inner array) is removed and gobject type is identified by the "type" field. Type 1 = proposal, type 2 = trigger. No other types should exist.Sentinel will begin creating superblock trigger objects (candidate superblocks) in this new format. DashCore was updated in v12.3 to support either format, but any tools used to parse this (e.g. possibly DashCentral or DashNexus or other integrations) will need to be updated to support either.I am happy to assist if any one needs help, please contact me with any questions.