kylefang/stacks-puppet-node
1
0
Fork 0
mirror of https://github.com/alexgo-io/stacks-puppet-node.git synced 2026-01-12 22:43:42 +08:00
Code Issues Packages Projects Releases Wiki Activity

remove double As, specify signed/unsigned of integer type

Browse Source
This commit is contained in:
Aaron Blankstein
2018-11-29 14:26:20 -06:00
parent b7f4100804
commit 8a1e7bed4b
1 changed files with 4 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
sip/sip-002-smart-contract-language.md
View File

@@ -94,9 +94,9 @@ To interact with Stacks balances, smart contracts may call the
`(stacks-transfer!)` function. This function will attempt to transfer
from a given principal to another principal. This function itself
_requires_ that the operation have been signed by the transfering
principal. The `integer` type in our smart contracting language is
8-bytes, which allows it to specify the maximum amount of microstacks
spendable in a single Stacks transfer.
principal. The `integer` type in our smart contracting language is an
8-byte unsigned integer, which allows it to specify the maximum amount
of microstacks spendable in a single Stacks transfer.
Like any other smart contract transaction, this function call returns
true if the transfer was successful, and false otherwise.
@@ -223,7 +223,7 @@ Smart contracts on the Stacks blockchain will be deployed directly as
source code. The goal of the smart contracting language is that the
code of the contract defines the _ground truth_ about the intended
functionality of the contract. While seemingly banal, many systems
chose instead to use a a compiler to translate from a a friendly
chose instead to use a compiler to translate from a friendly
high-level language to a lower-level language deployed on the
blockchain. Such an architecture is needlessly dangerous. A bug in
such a compiler could lead to a bug in a deployed smart contract when