From 8a1e7bed4be45d75db8d758ed731fc0f7953e116 Mon Sep 17 00:00:00 2001 From: Aaron Blankstein Date: Thu, 29 Nov 2018 14:26:20 -0600 Subject: [PATCH] remove double As, specify signed/unsigned of integer type --- sip/sip-002-smart-contract-language.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/sip/sip-002-smart-contract-language.md b/sip/sip-002-smart-contract-language.md index 153835dc5..1bfc28287 100644 --- a/sip/sip-002-smart-contract-language.md +++ b/sip/sip-002-smart-contract-language.md @@ -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