Why Signum
Signum Basics
Transactions
3 min
the transaction is an action on the docid\ eli0yw7jo qfwfx9ufq8s on behalf of an docid\ lrjdbchmhug tfn0wmehg the signum blockchain provides various types of transactions the content of the transaction depends on its type the transaction types are listed in the docid\ irb1d8bdsp2b 6fzkfldl sender and signature each transaction contains the public key of the sender account, on behalf of which the action is performed on the blockchain the transaction sent from an ordinary account (without script) must contain the sender's digital signature smart contracts create transactions by the given logic which needs no verification of the outgoing transaction transaction fee signum transactions are cheap but not free the sender is charged a fee the sender can specify any amount of fee but not less than the minimum amount the minimum fees are listed in the docid\ ygad5ktwtr3puvptwx3h5 json representation the docid\ yynxycqblmbwflxzom4c6 of signum nodes use the json representation of transactions you can send transactions to a node and read transactions stored on the blockchain via rest api in json here is an example of json representation for a normal payment { "type" 0, "subtype" 0, "timestamp" 241087409, "deadline" 1440, "senderpublickey" "1a542ea583ccd3a0d7d7ed74352cdeb7470c7ced3854724d19f211e7ac620b1e", "recipient" "13383190289605706987", "recipientrs" "s hk9d p74q xdej d6pgm", "amountnqt" "50000000000", "feenqt" "1470000", "signature" "cfb68bd09441061f20e65c0de4dc0750b79029ed27073bd21e532301668c44005748538ef378a284e427d5dfcd49e96ba15ab47b89f27157179d1f9f9c831ef3", "signaturehash" "83cbfac7978e7666fc563cbb26f5899b0b546fa9ad0ba70f936c46a2fea26b29", "fullhash" "d012dd016c5d6b4f96557f868a2a8e4bf63e41e9dd0845fa65cfac6c807aae8d", "transaction" "5722770469973463760", "attachment" { "version message" 1, "message" "f081441d761b46368ca5f6de72dea5d4768a855ba41f49a28f40373ad1f2909a", "messageistext" true }, "attachmentbytes" "014000008066303831343431643736316234363336386361356636646537326465613564343736386138353562613431663439613238663430333733616431663239303961", "sender" "17876986733297634672", "senderrs" "s 95dj qyub bfxa hjy7j", "height" 998494, "version" 1, "ecblockid" "1442524769036867118", "ecblockheight" 998482, "block" "9513413031999455343", "confirmations" 72, "blocktimestamp" 241087702, "requestprocessingtime" 1 } field description type definition of the main category of the transaction ( see docid\ irb1d8bdsp2b 6fzkfldl ) subtype definition of the transaction id timestamp seconds since genesis block (block 0) deadline value in seconds the standard is 1440 seconds senderpublickey the publisher/sender's public key recipient the recipients account id recipientrs the recipient's reed solomon address (see docid\ lgwi2uzp75rxlhsx0oeda ) in the form of s 1234 abcd 12ab 123yz amountnqt signa amount in planck (1 signa = 100000000 = 10^8 planck) feenqt fee amount in planck signature singaturehash fullhash transaction the id of this transaction attachment an attachment of a maximum of 1,000 byte arbitrary data attachmentbytes sender the sender account id senderrs the sender reed solomon address (see docid\ lgwi2uzp75rxlhsx0oeda ) in the form of s 1234 abcd 12ab 123yz height block height version a version of the transaction structure ecblockid ecblockheight block confirmation number of confirmations since the transaction was added to the blockchain blocktimestamp seconds since genesis block (block 0)