养肾穴位
- 关元穴
- 太溪穴
- 涌泉穴
- 肾腧穴
夏秋之交,一年之中这个时候是灸关元的最好时机
【艾灸方法】:用艾条温和灸关元穴5—10分钟,一天一次
【拔罐方法】:用气罐留罐关元穴10—15分钟,隔天一次
取穴:采用仰卧的姿势,关元穴位于脐下三寸处,有培元固本、补益下焦之功,凡元气亏损均可使用。
关元穴的主治病症:
第1步强壮穴:作为保健强身长寿穴,用灸法。
第2步诊生死:用指头按穴,如果指下感到无力空空,离手时,穴凹无弹力,胸下坚硬如石头,大限已到,活不久。
第3步助孕:子宫虚寒不孕者,要常灸此穴。
第4步补肾虚:脐下肾间之气藏于此穴。肾虚而腰酸或阳痿者,用灸法。
第5步治痛经:冰品引发的痛经,热敷或灸此穴。
第6步治虚喘:喘哮发作面色苍白,用灸法,特效。
第7步治小肠病:因为小肠募穴,所以治小肠各种疾病。
第8步治糖尿病:强肾可缓解糖尿病并发症,需配合足三里、三阴交穴。
第9步治排尿不顺:灸后尿排顺,也可以用拍法,五指并拢空拍,一次连续拍108下效果最好。
第10步治各种血症:本穴为血液循环的强壮剌激点,又为先天气海,元阴元阳在此交会,虚症用灸,平时多揉按拍可促进血液循环。
open /Library/Developer/CommandLineTools/Packages/macOS_SDK_headers_for_macOS_10.14.pkg
Problem solved: just download Command Line Tools (macOS 10.14) for Xcode 10. Hope that solves other people’s problems.
https://developer.apple.com/download/more/
clion 应该检测到这个路径
/Library/Developer/CommandLineTools/usr/bin/c++
/Library/Developer/CommandLineTools/usr/bin/cc
git config --global http.proxy http://192.168.0.107:7890 |
导致项目延期的问题:
brew update |
安装binaryen
git clone https://github.com/WebAssembly/binaryen.git |
编译llvm支持WASM
mkdir ~/wasm-compiler |
echo “export WASM_LLVM_CONFIG=/opt/wasm/bin/llvm-config” >> ~/.bash_profile/opt/wasm” >> ~/.bash_profile
echo “export WASM_ROOT=
echo “export LLVM_DIR=/usr/local/Cellar/llvm@4/4.0.1_1/lib/cmake/llvm” >> ~/.bash_profile
source ~/.bash_profile
N(active) and “active”_n.value is the same, it converts string into base32 string representation of unsigned 64-bit integer. However, the former is deprecated now and the latter is the new standard in the latest eosio.cdt. “active”_n is a little bit different, it is converting string into a name object.
#define INLINE_ACTION_SENDER(…) BOOST_PP_OVERLOAD(INLINE_ACTION_SENDER,VA_ARGS)(VA_ARGS)
在编译阶段把 base32 编码的字符串转换为 uint64_t 数值 |
封装 uint64_t 数值,去掉数学计算,打印输出 base32 字符串 |
contracts/eosiolib/types.h |
go get -u github.com/gin-gonic/gin |
“lldb-server”: executable file not found in $PATH
preferences-debugger-Use Native Backend
could not launch process: decoding dwarf section info at offset 0x0: too short。
1、更新dlv,go get -u github.com/derekparker/delve/cmd/dlv
2、修改Goland的配置,Help->Edit Custom Properties中增加新版dlv的路径配置:dlv.path=/path/go/bin/dlv
input command in term
// get help information |
tyleraccount
Description EOS Token Sale Claim Key
Public key EOS5p6VPhWXp6UBojRsYbimjuwWsBLth6aFTsMrnuFoX2f2oM4LGZ
Private key 5HubX63BtvNRnRKUuXNLNR9FD34FxnudQuGdmev8kA3c26NCW4y
cleos -u http://192.168.1.85:8888 get table astyler12312 astyler12312 |
1.2.x 旧版本方式
#使用 -o 生成wast文件和wasm文件 |
1.3.x 新版本方式
eosio-cpp -abigen ./xx.cpp |
cleos -u https://api-kylin.eoslaomao.com set contract astyler12312 ./buyname |
push action |
查询套餐
cleos -u http://192.168.1.85:8888 get table vip vip prices |
eosiocpp是一个c++生成wasm和ABI文件的工具。 |
An EOSIO Smart Contract consists of a set of action and type definitions.
Action definitions specify and implement the behaviors of the contract.
The type definitions specify the required content and structures.
EOSIO actions operate primarily in a message-based communication architecture. A client invokes actions by sending (pushing) messages to nodeos.
EOSIO Smart Contracts can communicate with each other, e.g., to have another contract perform some operation pertinent to the completion of the current transaction, or to trigger a future transaction outside of the scope of the current transaction.
EOSIO supports two basic communication models, inline and deferred.
Communication among contracts should be considered as occurring asynchronously. The asynchronous communication model can result in spam, which the resource limiting algorithm will resolve.
There is no guarantee that a deferred action will be executed.
Action types are actually base32 encoded 64-bit integers.This means they are limited to the characters a-z, 1-5, and ‘.’ for the first 12 characters. If there is a 13th character then it is restricted to the first 16 characters (‘.’ and a-p).
By means of confirmation, you should see the transaction in the transaction history with the block number of which it is included.
From a global view of an EOSIO blockchain, every node in the EOSIO network gets a copy of and runs every action in every contract.
Some of the nodes are doing the actual work of the contract, while others are processing in order to prove the validity of the transaction blocks.
receiver is the account that is currently processing the action.
code is the account that authorized the contract.
action is the ID of the currently running action.
Every transaction must execute in 30ms or less. If a transaction contains several actions, and the sum of these actions is greater than 30ms, the entire transaction will fail. In situations without concurrency requirements for their actions this can be circumvented by including the CPU consuming actions in separate transactions.
EOSIO中的合约可以相互通信。它是通过基于消息的通信架构实现的。
EOS通信模型就是他们沟通的方式。通信模型有两种类型:Inline Communication Model(内联通信模型)和Deferred Communication Model(延时通信模型)。
用户从智能合约A执行操作(Action #1)。当操作开始执行时,它会触发另外两个操作:来自智能合约B的操作Action #1.1和来自智能合约C的操作Action #1.2。一切都在当前交易中完成。
在当前交易中执行并与其完成相关的操作,称为inline action即内联操作。
重要的是要记住内联操作是作为调用操作的一部分执行的。因此,它们与原始交易的范围和权限相同。这是他们将被执行的保证。如果其中一个操作失败,则整个交易将失败。
根据生产者的判断,延时的操作最好可以安排在稍后的时间运行。无法保证延期操作将执行。
即使它们不属于同一交易,它们也具有发送它们的合约的权限。
交易可以包含N个操作。但是,每个交易必须在30ms或更短的时间内执行。如果交易包含多个操作,并且这些操作的总和大于30毫秒,则整个交易将失败。