Skip to content

no message #3

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
kodty wants to merge 1 commit into from
Closed

no message #3

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
202 changes: 85 additions & 117 deletions NisApi.src.html
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,4 +1,4 @@
<!--suppress HtmlUnknownTag -->
<!--suppress HtmlUnknownTag -->
<html>

<head>
Expand Down Expand Up @@ -524,7 +524,7 @@ <h4>Multisig accounts:</h4>
<td>
<p>Optional field in case the transaction contains a message. The
payload is the actual (possibly encrypted) message data. The payload is
allowed to have a maximal size of 512 bytes. Transaction validation detects
allowed to have a maximal size of 1024 bytes. Transaction validation detects
if the limit is exceeded and returns an error in this case.</p>
</td>
</tr>
Expand Down Expand Up @@ -2099,64 +2099,6 @@ <h2>Requesting parts of the block chain</h2>
identified by block height or block hash or can supply up to 10 blocks
beginning at a certain height.</p>

<!-- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- -->
<h3>Getting a block with a given hash</h3>

<api get>/block/get</api>


<desc>
<p class=NemNoSpacing>Gets a block from the chain that has a
given hash.</p>
</desc>

<h4>Parameter:</h4>

<table class=NemTableGrid>
<tr>
<td>
<p class=JSON>blockHash </p>
</td>
<td>
<p class=NemNoSpacing>The 256 bit sha3 hash of the block.
The hash must be supplied as hexadecimal string.</p>
</td>
</tr>
</table>

<h4>Example:</h4>

<p><a href="http://127.0.0.1:7890/block/get?blockHash=58efa578aea719b644e8d7c731852bb26d8505257e03a897c8102e8c894a99d6">http://127.0.0.1:7890/block/get?blockHash=58efa578aea719b644e8d7c731852bb26d8505257e03a897c8102e8c894a99d6</a>
</p>

<h4>Example of returned JSON object (main network):</h4>

<resp>
{
"timeStamp": 9232942,
"signature": "005f91b8908fc173a428ff8e8c4a0ee0d69e4004aed0d08f27690b6b6672ef74ccc6b89695bed5f29b0f4a812cb84bfa459f52a4e14a11e574793969f0e1a30f",
"prevBlockHash": {
"data": "f721e563b4431594c5af6f6be0a913f47f0aca6c3b8ee6a703bfe175ee54babf"
},
"type": 1,
"transactions": [
],
"version": 1744830465,
"signer": "78e121cc1cf63424651ec64251e78efda81386c9f5e9eb4cb08b2a2192c9dce5",
"height": 42803
}
</resp>

<h4>Possible Errors:</h4>

<p class=NemNoSpacing>If the block hash is not found in the
database, NIS will return a JSON error object. See
<appa>Error object</appa>
or more information of the error object and
<alnk>Appendix B: NIS Errors</alnk>
for the error message.
</p>

<!-- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- -->
<h3>Getting a block with a given height</h3>

Expand Down Expand Up @@ -3791,7 +3733,7 @@ <h2>Provisioning a namespace</h2>
</code></pre>

<p>This time the parent is set to the parent namespace, in this case the root namespace 'alice'. The rental fee for a sub-namespace
is 10% of the fee for a root namespace, i.e. 5000 XEM. Be sure to wait until you own the root namespace or NIS will respond with
is 200 XEM. Be sure to wait until you own the root namespace or NIS will respond with
an error message. Once the transaction is included in a block, you own the sub-namespace 'alice.vouchers' as long as the root namespace 'alice'
does not expire.</p>

Expand Down Expand Up @@ -3985,6 +3927,7 @@ <h3>Gathering data for the signature</h3>
mosaic supply change transactions the version must be
</p>
<li>0x68 &lt;&lt; 24 + 1 (main network)</li>
<li>0x60 &lt;&lt; 24 + 1 (mijin network)</li>
<li>0x98 &lt;&lt; 24 + 1 (test network)</li>
<b>Example (main network):</b> 0x01, 0x00, 0x00, 0x68
<p></p>
Expand All @@ -3993,6 +3936,7 @@ <h3>Gathering data for the signature</h3>
For transfer transactions and multisig aggregate modification transactions the version must be
</p>
<li>0x68 &lt;&lt; 24 + 2 (main network)</li>
<li>0x60 &lt;&lt; 24 + 2 (mijin network)</li>
<li>0x98 &lt;&lt; 24 + 2 (test network)</li>
<b>Example (main network):</b> 0x02, 0x00, 0x00, 0x68
</ul>
Expand Down Expand Up @@ -4254,23 +4198,26 @@ <h3>Gathering data for the signature</h3>

<h4colored>Provision namespace transaction part</h4colored>
<li>
<b>Length of rental fee sink's public key byte array (always 32):</b> 4 bytes (integer).
<ul>
<b>Always:</b> 0x20, 0x00, 0x00, 0x00
<b>Length of rental fee sink's Encoded Address (always 40):</b> 4 bytes (integer).
<ul>
<b>Always:</b> 0x28, 0x00, 0x00, 0x00
</ul>
</li>
<li>
<b>Public key bytes of rental fee sink:</b> 32 bytes.
<b>Address bytes of rental fee sink:</b> 40 bytes.
<ul>
<b>Always:</b> 0x3e, 0x82, 0xe1, 0xc1, 0xe4, 0xa7, 0x5a, 0xda, 0xa3, 0xcb,
0xa8, 0xc1, 0x01, 0xc3, 0xcd, 0x31, 0xd9, 0x81, 0x7a, 0x2e, 0xb9, 0x66, 0xeb,
0x3b, 0x51, 0x1f, 0xb2, 0xed, 0x45, 0xb8, 0xe2, 0x62
<b>Always (TAMESPACEWH4MKFMBCVFERDPOOP4FK7MTDJEYP35):</b> 0x35, 0x33, 0x50, 0x59, 0x45, 0x4a, 0x44, 0x54, 0x4d, 0x37,
0x4b, 0x46, 0x34, 0x50, 0x4f, 0x4f, 0x50, 0x44, 0x52, 0x45,
0x46, 0x56, 0x43, 0x42, 0x4d, 0x46, 0x4b, 0x4d, 0x34, 0x48,
0x57, 0x45, 0x43, 0x41, 0x50, 0x53, 0x45, 0x4d, 0x41, 0x54
</ul>
</li>
<li>
<b>Fental fee (always 50000000000):</b> 8 bytes (long).
<ul>
<b>Always:</b> 0x00, 0x74, 0x3b, 0xa4, 0x0b, 0x00, 0x00, 0x00
<b>Rental fee (Root always: 5000000000, Sub always: 200000000) for namespace:</b> 8 bytes (long).
<ul>
<b>Root always:</b> 0x00, 0xf2, 0x05, 0x2a, 0x01, 0x00, 0x00, 0x00
<br />
<b>Sub always:</b> 0x00, 0xc2, 0xeb, 0x0b, 0x00, 0x00, 0x00, 0x00
</ul>
</li>
<li>
Expand Down Expand Up @@ -4560,23 +4507,24 @@ <h3>Gathering data for the signature</h3>
</li>
<p>The levy structure ends here.</p>
<li>
<b>Length of creation fee sink's public key byte array (always 32):</b> 4 bytes (integer).
<b>Length of creation fee sink's encoded address byte array (always 40):</b> 4 bytes (integer).
<ul>
<b>Always:</b> 0x20, 0x00, 0x00, 0x00
<b>Always:</b> 0x28, 0x00, 0x00, 0x00
</ul>
</li>
<li>
<b>Public key bytes of creation fee sink:</b> 32 bytes.
<b>Address key bytes of creation fee sink:</b> 40 bytes.
<ul>
<b>Always:</b> 0x53, 0xe1, 0x40, 0xb5, 0x94, 0x7f, 0x10, 0x4c, 0xab, 0xc2, 0xd6, 0xfe, 0x8b,
0xae, 0xdb, 0xc3, 0x0e, 0xf9, 0xa0, 0x60, 0x9c, 0x71, 0x7d, 0x96, 0x13,
0xde, 0x59, 0x3e, 0xc2, 0xa2, 0x66, 0xd3
<b>Always (TBMOSAICOD4F54EE5CDMR23CCBGOAM2XSJBR5OLC):</b> 0x43, 0x4c, 0x4f, 0x35, 0x52, 0x42, 0x4a, 0x53, 0x58, 0x32,
+0x4d, 0x41, 0x4f, 0x47, 0x42, 0x43, 0x43, 0x33, 0x32, 0x52,
+0x4d, 0x44, 0x43, 0x35, 0x45, 0x45, 0x34, 0x35, 0x46, 0x34,
+0x44, 0x4f, 0x43, 0x49, 0x41, 0x53, 0x4f, 0x4d, 0x42, 0x54
</ul>
</li>
<li>
<b>Fee quantity:</b> 8 bytes (long).
<ul>
<b>Always: (50000000000)</b> 0x00, 0x74, 0x3b, 0xa4, 0x0b, 0x00, 0x00, 0x00
<b>Always: (5000000000)</b> 0x00, 0xf2, 0x05, 0x2a, 0x01, 0x00, 0x00, 0x00
</ul>
</li>

Expand Down Expand Up @@ -4725,45 +4673,62 @@ <h2>Transaction fees</h2>
<p class=JSON>Transfer transaction</p>
</td>
<td>
<p>The fee is the sum of the fee for transferring an amount of
XEM and the fee for appending a message to the transaction.</p>
<p>
The fee is the sum of the fee for transferring an amount of
XEM and the fee for appending a message to the transaction.
</p>
<p>1) Fees for transferring XEM to another account:<br />
<p>a) non mosaic xem transfer: 1 xem per 10_000 xem transferred, capped at 25 xem.<p>

<p>
Example: <br />
5 xem fee for a 45_000 xem transfer, 25 xem for a 500_000 xem transfer.
</p><br />

<p>2) Fees for appending a message to a transaction:<br />

<p>
b) messages: 1 xem per commenced 32 message bytes (messageLength / 32 + 1).
</p>
<p>
Example: <br />
message length of 48 bytes has 2 xem fee.
</p>
</p><br />
<p>3) Fees for transferring a mosaic to another account:<br />

<p>
c) mosaics with divisibility of 0 and a maxmimum supply of 10_000 are called small business mosaics.
1 xem fee for any transfer of a small business mosaic.
</p>

<p>1) Fees for transferring XEM to another account:<br/>
a) If the amount transferred is less than 8 XEM then the
fee is 10 - amount XEM.<br/>
Example:<br/>
Transferring 6 XEM costs 4 XEM fee.<br/>
b) If the amount transferred is greater or equal 8 XEM
then the fee is<br/>
max(2, 99 * arctan(amount / 150000)) XEM.<br/>
Example:<br/>
Transferring 100000 XEM costs 58 XEM.</p>
<p>
d) for other mosaics as before the same formula is applied to calculate the xem equivalent, then the fee for transferring xem is applied.
Call that fee xemFee. To take into account the total quantities for different mosaics, an adjustment term is calculated. <br /><br />
For a mosaic called m calculate:<br />
<ol>
<li>maxMosaicQuantity = 9_000_000_000_000_000</li>
<li>totalMosaicQuantity = mosaic m supply * 10 ^ (mosaic m divisibility)</li>
<li>supplyRelatedAdjustment = floor(0.8 * ln(maxMosaicQuantity / totalMosaicQuantity)</li>
<li>
Then the fee is calculated as:<br />
fee = max(1L, xemFee - supplyRelatedAdjustment)
</li>
</ol>
</p>

<p>2) Fees for appending a message to a transaction:<br/>
Transferring 100000 XEM costs 58 XEM.</p>
<p>Example:<br />
Mosaic with 9_000_000 supply and divisibility of 3<br />
<ol>
<li>totalMosaicQuantity = 9_000_000 * 1_000 = 9_000_000_000</li>
<li>supplyRelatedAdjustment = floor(0.8 * ln(9_000_000_000_000_000 / 9_000_000_000)) = floor(11.052) = 11</li>
<li>transferring 150 such mosaics is like transferring 150_000 xem:</li>
<li>xemFee = 15 xem</li>
<li>fee = 15 xem - 11 xem = 4 xem</li>
</ol>
</p>
</p>

<p>2) Fees for transferring a mosaic to another account:<br/>
For each mosaic that is transferred the fee is calculated the following way:<br>
a) given a mosaic with initial supply s, divisibility d and quantity q, the XEM equivalent is (round to the next smaller integer)<br/>
xemEquivalent = (8,999,999,999 * q) / (s * 10^d) <br/>
The fee is then calculated by applying 1) to xemEquivalent and in a final step adding 25% to it:<br>
fee = (apply 1) to xemEquivalent) * 1.25<br>
Example:<br/>
Suppose the transaction has an amount of 3,000,000 micro-xem and the mosaic in the attachment has an initial supply of 1,000,000,
a divisibility of 3 and a quantity of 5,000. This means that a quantity of 15,000 will be transferred.
Applying the above formula gives<br>
xemEquivalent = (8,999,999,999 * 15,000) / (1,000,000 * 1000) = 134999<br>
The result was rounded to the next smaller integer. Applying 1) to xemEquivalent gives (again after rounding) 72.<br>
So the fee is 72 * 1.25 XEM = 90 XEM.</p>

<p>3) Fees for appending a message to a transaction:<br/>
If no message or an empty message is append it costs
0 XEM. Else the fee is calculated as<br/>
2 * max(1, message length / 16)<br/>
Example:<br/>
The unencrypted message &bdquo;The New Economy
Movement will change the world!!!&ldquo; has a length 49
characters and thus will cost 2 * 49/16 = 6 XEM.</p>
</td>
</tr>
<tr>
Expand Down Expand Up @@ -4809,23 +4774,26 @@ <h2>Transaction fees</h2>
<p class=JSON>Provision namespace transaction</p>
</td>
<td>
<p>108 XEM</p>
<p>20 XEM</p>
<p>plus:</p>
<p>Fee for root namespace provisioning: 5000 XEM</p>
<p>Fee for sub-namespace provisioning: 200 XEM</p>
</td>
</tr>
<tr>
<td>
<p class=JSON>Mosaic definition creation transaction</p>
</td>
<td>
<p>108 XEM</p>
<p>20 XEM</p>
</td>
</tr>
<tr>
<td>
<p class=JSON>Mosaic supply change transaction</p>
</td>
<td>
<p>108 XEM</p>
<p>20 XEM</p>
</td>
</tr>
</table>
Expand Down