cbf (Fri, 03 Feb 2017 06:31:42 GMT):
User User_1 added by cbf.
rjones (Fri, 03 Feb 2017 06:31:51 GMT):
Has joined the channel.
rjones (Fri, 03 Feb 2017 06:32:26 GMT):
Has left the channel.
jimthematrix (Fri, 03 Feb 2017 19:50:45 GMT):
Has joined the channel.
karkal (Fri, 03 Feb 2017 19:57:55 GMT):
Has joined the channel.
jiangyaoguo (Sat, 04 Feb 2017 01:33:26 GMT):
Has joined the channel.
shimron (Sat, 04 Feb 2017 02:43:58 GMT):
Has joined the channel.
genggjh (Sat, 04 Feb 2017 03:46:38 GMT):
Has joined the channel.
ray (Sun, 05 Feb 2017 08:42:49 GMT):
Has joined the channel.
baohua (Mon, 06 Feb 2017 06:09:50 GMT):
Has joined the channel.
baohua (Mon, 06 Feb 2017 06:10:22 GMT):
ping:grinning:
ray (Mon, 06 Feb 2017 08:09:43 GMT):
:grin:
david.peyronnin (Mon, 06 Feb 2017 09:53:18 GMT):
Has joined the channel.
Honglei (Mon, 06 Feb 2017 14:30:11 GMT):
Has joined the channel.
xixuejia (Tue, 07 Feb 2017 00:29:20 GMT):
Has joined the channel.
liutc (Tue, 07 Feb 2017 01:05:47 GMT):
Has joined the channel.
liutc (Tue, 07 Feb 2017 01:05:55 GMT):
@baohua pang!
baohua (Tue, 07 Feb 2017 01:06:15 GMT):
Morning :)
liutc (Tue, 07 Feb 2017 01:09:39 GMT):
Why does HLP choose to migrate from Slack to this new tool?
baohua (Tue, 07 Feb 2017 01:13:41 GMT):
i guess the cost is too much
cbf (Tue, 07 Feb 2017 01:17:56 GMT):
@liutc basically, @baohua is correct. We were using a free Slack plan, which limits the amount of searchable history to 10k lines. That's about 2.5 days worth of activity! If we upgraded to a paid Slack account, with 5400 members it would cost us in the range of $300,000 USD/year... far too expensive. We can self-host RocketChat, which is not as slick but offers the basic capabilities we need for just a few thousand for the entire year, including the storage for the archived messages.
baohua (Tue, 07 Feb 2017 01:19:26 GMT):
And open-source project should encourage open-source tools :)
liutc (Tue, 07 Feb 2017 01:20:10 GMT):
@cbf this makes sense. Searching history is important and 300K per year is a relatively large number :P
cbf (Tue, 07 Feb 2017 01:20:23 GMT):
indeed;-)
baohua (Tue, 07 Feb 2017 01:23:11 GMT):
personally, i feel rocketchat better than slack in experience. Hope the network connection is stable in future...
Donald Liu (Tue, 07 Feb 2017 01:32:33 GMT):
Has joined the channel.
lignyxg (Tue, 07 Feb 2017 01:36:20 GMT):
Has joined the channel.
grapebaba (Tue, 07 Feb 2017 01:45:13 GMT):
@baohua disagree, IMO rocket UI is very poor :smiling_imp: especially in mobile
baohua (Tue, 07 Feb 2017 01:47:45 GMT):
aha, i'm using the web UI, good enough to me. u know :hamster:
baohua (Tue, 07 Feb 2017 01:48:35 GMT):
only if it's stable to connect, then that's fine. consider irc....
baohua (Tue, 07 Feb 2017 02:06:14 GMT):
Hyperledger Technical Community,
We are getting ready to launch the Hyperledger Summer Internship Program. In preparation for this, we are calling for Mentors (and project suggestions) from the Community.
If you are interested in potentially mentoring an intern, please indicate your interest by completing the following form by Friday, February 17th https://goo.gl/forms/3MvSU13hX0XVlQj33.
jojocheung (Tue, 07 Feb 2017 02:08:01 GMT):
Has joined the channel.
liutc (Tue, 07 Feb 2017 02:28:45 GMT):
@baohua who will pay for this program? will be intern be paid?
baohua (Tue, 07 Feb 2017 02:33:48 GMT):
@toddb I guess this program is free to join for mentors? But not sure whether those intern can get paid :)
toddb (Tue, 07 Feb 2017 02:33:48 GMT):
Has joined the channel.
atian15 (Tue, 07 Feb 2017 02:49:53 GMT):
Has joined the channel.
crazybit (Tue, 07 Feb 2017 05:32:05 GMT):
Has joined the channel.
Hangyu (Tue, 07 Feb 2017 06:09:44 GMT):
Has joined the channel.
zlliu (Tue, 07 Feb 2017 08:12:28 GMT):
Has joined the channel.
yp (Tue, 07 Feb 2017 09:35:23 GMT):
Has joined the channel.
niechen (Tue, 07 Feb 2017 18:18:06 GMT):
Has joined the channel.
myu (Tue, 07 Feb 2017 19:59:01 GMT):
Has joined the channel.
myu (Tue, 07 Feb 2017 20:01:29 GMT):
Correct. Mentors are volunteers from the community who are interested in mentoring student developers. Yes, the interns will be paid. The internship will be 3 months long during the summer. A stipend if $5,500 will be paid to the interns provided they are making satisfactory progress and successfully complete the project.
baohua (Wed, 08 Feb 2017 01:26:01 GMT):
@myu Thanks, and need the mentors to to SF or just communicate on line?
lafenicecc (Wed, 08 Feb 2017 02:11:02 GMT):
Has joined the channel.
myu (Wed, 08 Feb 2017 02:59:10 GMT):
@baohua Intern and mentors can be based anywhere. It would be great if it so happens that the mentors and interns are from the same city and can meet face to face. But that's not a requirement at all. They will most likely use virtual tools to work together.
baohua (Wed, 08 Feb 2017 02:59:56 GMT):
thanks, min!
py (Wed, 08 Feb 2017 03:25:17 GMT):
Has joined the channel.
yp (Wed, 08 Feb 2017 03:57:20 GMT):
@baohua 可否中文简单描述下Hyperledger Technical Community
yp (Wed, 08 Feb 2017 03:58:42 GMT):
Hyperledger Summer Internship Program.
daijianw (Wed, 08 Feb 2017 08:18:38 GMT):
Has joined the channel.
Eagel (Wed, 08 Feb 2017 11:21:41 GMT):
Has joined the channel.
baohua (Thu, 09 Feb 2017 02:48:17 GMT):
hi, will have the weekly meeting next Wed morning, pls update the agenda and attendee list, thanks! https://wiki.hyperledger.org/groups/twgc/meeting/2017-02-15
baohua (Thu, 09 Feb 2017 02:48:28 GMT):
@all
chenxl (Thu, 09 Feb 2017 03:30:54 GMT):
Has joined the channel.
guhaihua (Thu, 09 Feb 2017 03:32:43 GMT):
Has joined the channel.
liutc (Thu, 09 Feb 2017 13:51:11 GMT):
@baohua what's form of this weekly meeting? online meeting via this chat tool or a call?
baohua (Thu, 09 Feb 2017 13:54:57 GMT):
FYI. https://wiki.hyperledger.org/groups/tsc/technical-working-group-china
baohua (Thu, 09 Feb 2017 13:55:34 GMT):
Currently use a local phone call. may migrate to other call/webmeeting system when ready.
liutc (Thu, 09 Feb 2017 14:01:54 GMT):
It is so-called "local phone call", but it has global numbers, you know :P
MikeMayori (Thu, 09 Feb 2017 19:44:04 GMT):
Has joined the channel.
Donald Liu (Fri, 10 Feb 2017 01:34:43 GMT):
BTW: Number: 800-820-0027 (toll free) and 400-821-0751 (caller paid) ... both numbers are meant to be for location/local in China. Cheers.
lfeagan (Fri, 10 Feb 2017 03:33:16 GMT):
Has joined the channel.
hydrachain (Sat, 11 Feb 2017 06:03:36 GMT):
Has joined the channel.
hydrachain (Sat, 11 Feb 2017 06:04:23 GMT):
大家好！
hydrachain (Sat, 11 Feb 2017 06:07:59 GMT):
请问在Fabric 6.0下，如何基于Go 来添加新的用户？就如同Java SDK下通过Member创建新用户实现register 和enroll.
hydrachain (Sat, 11 Feb 2017 06:07:59 GMT):
请问在Fabric 0.6下，如何基于Go 来添加新的用户？就如同Java SDK下通过Member创建新用户实现register 和enroll.
hydrachain (Sat, 11 Feb 2017 06:07:59 GMT):
请问在Fabric 0.6下，是否支持动态添加节点呢？
sha256cn (Sat, 11 Feb 2017 07:40:03 GMT):
Has joined the channel.
hydrachain (Sun, 12 Feb 2017 13:47:09 GMT):
我在Fabric 0.6下添加用户，代码基本结构如下： peerClientConn, err = peer.NewPeerClientConnection()
ecapClient = pb.NewECAPClient(peerClientConn)
ecapClient.CreateCertificatePair(context.Background(), req)
hydrachain (Sun, 12 Feb 2017 13:47:09 GMT):
我在Fabric 0.6下添加用户，代码基本结构如下： peerClientConn, err = peer.NewPeerClientConnection()
ecapClient = pb.NewECAPClient(peerClientConn)
ecapClient.CreateCertificatePair(context.Background(), req)
hydrachain (Sun, 12 Feb 2017 13:47:09 GMT):
我在Fabric 0.6下添加用户，代码基本结构如下：
peerClientConn, err = peer.NewPeerClientConnection()
...
ecapClient = pb.NewECAPClient(peerClientConn)
...
ecapClient.CreateCertificatePair(context.Background(), req)
运行时错误如下：
Failed to CreateCertificatePair: [rpc error: code = 12 desc = unknown service protos.ECAP]
好像是没有连上ECA，这个问题该如何解决呢？
hydrachain (Sun, 12 Feb 2017 13:47:09 GMT):
我基于Go在Fabric 0.6下添加User，代码基本结构如下：
peerClientConn, err = peer.NewPeerClientConnection()
...
ecapClient = pb.NewECAPClient(peerClientConn)
...
ecapClient.CreateCertificatePair(context.Background(), req)
运行时错误如下：
Failed to CreateCertificatePair: [rpc error: code = 12 desc = unknown service protos.ECAP]
好像是没有连上ECA，这个问题该如何解决呢？
hydrachain (Sun, 12 Feb 2017 13:47:09 GMT):
我基于Go在Fabric 0.6 Enroll User，代码基本结构如下：
peerClientConn, err = peer.NewPeerClientConnection()
...
ecapClient = pb.NewECAPClient(peerClientConn)
...
ecapClient.CreateCertificatePair(context.Background(), req)
运行时错误如下：
Failed to CreateCertificatePair: [rpc error: code = 12 desc = unknown service protos.ECAP]
好像是没有连上ECA，这个问题该如何解决呢？
oxygengj (Mon, 13 Feb 2017 01:26:17 GMT):
Has joined the channel.
zerppen (Mon, 13 Feb 2017 06:16:29 GMT):
Has joined the channel.
zerppen (Mon, 13 Feb 2017 06:16:42 GMT):
大家好
zhengjun (Mon, 13 Feb 2017 07:37:56 GMT):
Has joined the channel.
zhengjun (Mon, 13 Feb 2017 07:38:51 GMT):
大家好，我是三一集团投资的树根互联技术有限公司研发vp
zhengjun (Mon, 13 Feb 2017 07:41:06 GMT):
Julian邀请我加入t wg，请多指教
baohua (Mon, 13 Feb 2017 09:13:14 GMT):
welcome~
zhangchao (Tue, 14 Feb 2017 03:14:20 GMT):
Has joined the channel.
zhangchao (Tue, 14 Feb 2017 03:17:41 GMT):
各位好，我是日立中国的区块链主任研究员张超，很高兴加入Hyperledger chat group
zhangchao (Tue, 14 Feb 2017 03:18:29 GMT):
希望跟各位hyperledger参与方精诚合作
shibo.lin (Tue, 14 Feb 2017 03:36:06 GMT):
Has joined the channel.
jiangyaoguo (Tue, 14 Feb 2017 06:48:55 GMT):
欢迎
baohua (Tue, 14 Feb 2017 06:56:15 GMT):
welcome !
bluebird88 (Tue, 14 Feb 2017 10:12:04 GMT):
Has joined the channel.
bluebird88 (Tue, 14 Feb 2017 10:12:45 GMT):
各位好，我是闫洪坤，HL个人学习者，希望向各位多多学习！
jamessheen (Tue, 14 Feb 2017 14:56:54 GMT):
Has joined the channel.
xixuejia (Wed, 15 Feb 2017 00:33:53 GMT):
@bluebird88 welcome
baohua (Wed, 15 Feb 2017 01:36:48 GMT):
Dear all, the meeting will start at 10AM, FYI. https://wiki.hyperledger.org/groups/twgc/meeting/2017-02-15.
Number: 800-820-0027 (toll free) and 400-821-0751 (caller paid)
aratic (Wed, 15 Feb 2017 01:42:57 GMT):
Has joined the channel.
grapebaba (Wed, 15 Feb 2017 01:57:07 GMT):
code是多少来着
grapebaba (Wed, 15 Feb 2017 01:57:13 GMT):
@baohua
baohua (Wed, 15 Feb 2017 01:57:55 GMT):
Participant Code: 71173794
grapebaba (Wed, 15 Feb 2017 01:58:41 GMT):
看到了
baohua (Wed, 15 Feb 2017 01:59:00 GMT):
Thanks for the reminder :)
aratic (Wed, 15 Feb 2017 02:07:56 GMT):
你好 这里是吴思捷, 爱好者 希望能混个脸熟/参与/帮上忙
aratic (Wed, 15 Feb 2017 02:10:01 GMT):
bluemix已经有 blockchain 用了
aratic (Wed, 15 Feb 2017 02:10:48 GMT):
3月几号呢
aratic (Wed, 15 Feb 2017 02:13:10 GMT):
能有人加一下我的手机号么 目前是手机拨入的.. AT&T老贵了
aratic (Wed, 15 Feb 2017 02:13:22 GMT):
主题是
供应链 文化 金融 三个方向? 人数是5人队?
aratic (Wed, 15 Feb 2017 02:23:21 GMT):
还有微信群?
aratic (Wed, 15 Feb 2017 02:25:27 GMT):
readthedocs那个页面, 感觉目录都不稳定啊, 总的maillist应该最近在考虑重新整理
aratic (Wed, 15 Feb 2017 02:28:06 GMT):
md与其它格式应该是能转的, 只是样式固定一些
Eagel (Wed, 15 Feb 2017 02:33:53 GMT):
392881753@qq.com 杨圣磊
grapebaba (Wed, 15 Feb 2017 02:39:58 GMT):
可以用skype拨
aratic (Wed, 15 Feb 2017 02:41:13 GMT):
大意了..
aratic (Wed, 15 Feb 2017 02:41:46 GMT):
我以前翻过葡萄爸爸的github!
aratic (Wed, 15 Feb 2017 02:42:53 GMT):
谢谢你的提醒 下次:)
grapebaba (Wed, 15 Feb 2017 02:44:08 GMT):
:sweat_smile:
aratic (Wed, 15 Feb 2017 02:44:15 GMT):
哦, 这个电话会议400是国内的, 还好
aratic (Wed, 15 Feb 2017 02:48:53 GMT):
用这个的好处是有些散户没Slack啊, 这个直接能进, Hyperledger社区架的服务器吧, 估计, 另外, i18n建议还是提交回主站, 然后同步一份吧, 个人博客每天脚本抓都行
aratic (Wed, 15 Feb 2017 02:50:04 GMT):
我也注意到了主站的文档目录最近在整理.
grapebaba (Wed, 15 Feb 2017 03:04:13 GMT):
400也是市话啊，可以用个电信的手机拨800
baohua (Wed, 15 Feb 2017 03:07:11 GMT):
Meeting minutes today: https://wiki.hyperledger.org/groups/twgc/meeting/2017-02-15, thanks for all attendees.
liutc (Wed, 15 Feb 2017 03:42:03 GMT):
关于doc，我最希望每个文档都加个对应版本的tag，现在完全是乱的
baohua (Wed, 15 Feb 2017 03:50:53 GMT):
good point....
zhangchao (Wed, 15 Feb 2017 05:29:32 GMT):
看了今天的meeting minutes，说是有个hachathon在今年，请问是大约在什么时候，在哪个城市，以便提前作安排
baohua (Wed, 15 Feb 2017 06:02:27 GMT):
3.11/12 at shanghai, will have the official announcement in this week.
bluebird88 (Thu, 16 Feb 2017 01:32:13 GMT):
文档和最终的实现非常不一致，看了文档发现实现不是这个样子的。
bluebird88 (Thu, 16 Feb 2017 01:33:01 GMT):
另外，建议动员国内的社区力量进行文档维护，这样才会有更好的东西给大家
baohua (Thu, 16 Feb 2017 03:30:44 GMT):
yeap, an i18 work team has been organized through the mail-list. already started and now it's calling for more volunteers. @Kewei_Sun
Kewei_Sun (Thu, 16 Feb 2017 03:30:44 GMT):
Has joined the channel.
Kewei_Sun (Thu, 16 Feb 2017 03:37:17 GMT):
@baohua 我们正在收集文档翻译的需求，并且找到合适的平台， 目前的文档确实需要比较多的工作来规整一下。大家多提需求， 希望能把最需要的东西先做出来。另外，calling for more volunteers!
zhangchao (Thu, 16 Feb 2017 03:38:30 GMT):
看了下v1的consensus architecture，发现变化很大啊，将节点分成了endorse和普通peer，看起来是为了提高transaction的执行效率，但是怎么保证endorse节点中立可靠也是个很大的问题，尤其是谁hold这些节点，谁就有话语权。感觉v1的变得复杂了。
liutc (Thu, 16 Feb 2017 07:10:46 GMT):
@Kewei_Sun 我觉得这个阶段都不是翻译，是写。好多东西没的翻译……
grapebaba (Thu, 16 Feb 2017 07:33:31 GMT):
我们可以联系下@joshhus ，他主要负责文档更新，问问他哪些是ready的@Kewei_Sun
Kewei_Sun (Thu, 16 Feb 2017 08:13:53 GMT):
@grapebaba 好建议，我联络一下
aratic (Thu, 16 Feb 2017 09:07:06 GMT):
```所以对比corda看的话, 都是向着封闭/靠近真实模型了, 因为有兼管的需求, 传统银行CA那套是比较保险的
wutongtree (Thu, 16 Feb 2017 09:54:14 GMT):
Has joined the channel.
alviontaran (Thu, 16 Feb 2017 16:26:14 GMT):
Has joined the channel.
baohua (Fri, 17 Feb 2017 01:29:38 GMT):
@zhengjun we're here :)
RoseChild (Fri, 17 Feb 2017 03:09:08 GMT):
Has joined the channel.
RoseChild (Fri, 17 Feb 2017 03:10:10 GMT):
大家好，菜鸟一个，入门学习，寻找组织中
RoseChild (Fri, 17 Feb 2017 03:12:08 GMT):
对于文档，我有话说，确实好乱。找文档、镜像等花掉了一天半，结果还是分错的文档，比较打击积极性
baohua (Fri, 17 Feb 2017 03:28:09 GMT):
@RoseChild We are refining the documentation now, since the code is still in changing, will update the doc soon after the release.
yong (Fri, 17 Feb 2017 03:53:31 GMT):
Has joined the channel.
yong (Fri, 17 Feb 2017 03:55:13 GMT):
大家好，我在编译hyperledger时遇到如下编译问题，请大家帮我看看怎么解决
yong (Fri, 17 Feb 2017 03:55:14 GMT):
docker images -q hyperledger/fabric-peer | xargs -I '{}' docker rmi -f '{}'
docker images -q hyperledger/fabric-orderer | xargs -I '{}' docker rmi -f '{}'
docker images -q hyperledger/fabric-ccenv | xargs -I '{}' docker rmi -f '{}'
docker images -q hyperledger/fabric-javaenv | xargs -I '{}' docker rmi -f '{}'
docker images -q hyperledger/fabric-buildenv | xargs -I '{}' docker rmi -f '{}'
docker images -q hyperledger/fabric-testenv | xargs -I '{}' docker rmi -f '{}'
docker images -q hyperledger/fabric-zookeeper | xargs -I '{}' docker rmi -f '{}'
docker images -q hyperledger/fabric-kafka | xargs -I '{}' docker rmi -f '{}'
cd gotools && make clean
make[1]: Entering directory '/home/yong/go/src/github.com/hyperledger/fabric/gotools'
make[1]: Leaving directory '/home/yong/go/src/github.com/hyperledger/fabric/gotools'
make: stat: Makefile: Permission denied
make: *** No rule to make target 'install'. Stop.
Makefile:153: recipe for target 'build/docker/gotools' failed
make: *** [build/docker/gotools] Error 2
Kewei_Sun (Fri, 17 Feb 2017 04:58:21 GMT):
@joshhus I noticed that the current document is hosted on the readthedocs, we have some volunteers who are trying to translate them into Chinese, is it possible to have a Chinese version added to the current repository? thanks!
joshhus (Fri, 17 Feb 2017 04:58:21 GMT):
Has joined the channel.
baohua (Fri, 17 Feb 2017 05:33:20 GMT):
@yong from the log, may be u need to run with root privilege
yong (Fri, 17 Feb 2017 05:35:00 GMT):
@baohua 是在root权限下编译的
baohua (Fri, 17 Feb 2017 05:36:36 GMT):
strange, what's the output of "git pull; make peer"
bluebird88 (Fri, 17 Feb 2017 06:07:42 GMT):
@baohua : 最新的文档在哪里看？ github上的也不是最新的，包括下一代架构；
bluebird88 (Fri, 17 Feb 2017 06:07:51 GMT):
只能看代码？
aratic (Fri, 17 Feb 2017 06:20:30 GMT):
没有install 这个target, 先make clean 再make peer, 代码旧的话, 先git pull
aratic (Fri, 17 Feb 2017 06:20:52 GMT):
docker本身需要你用户在docker组, 这个需要在装完docker之后usermod一下
aratic (Fri, 17 Feb 2017 06:22:52 GMT):
文档目前得以英文 官方为主吧, readthedocs里在目录在整理, 有些散的markdown在代码目录 docs下面,
aratic (Fri, 17 Feb 2017 06:24:54 GMT):
按步骤来大多是没问题, 但是现在目录对刚来的是有点难看, sdk / chaincode developer 那个条目很不显眼了, 原来的tutor归到了starter kit, 耐心点翻喽
yong (Fri, 17 Feb 2017 08:34:05 GMT):
@baohua hyperledger的开发环境有要求马？我是fedora25
baohua (Fri, 17 Feb 2017 08:37:26 GMT):
all linux should be OK :)
yp (Fri, 17 Feb 2017 09:45:43 GMT):
@yong makefile里面没有定义install
yp (Fri, 17 Feb 2017 09:45:55 GMT):
# - all (default) - builds all targets and runs all tests/checks
# - checks - runs all tests/checks
# - peer - builds a native fabric peer binary
# - orderer - builds a native fabric orderer binary
# - unit-test - runs the go-test based unit tests
# - behave - runs the behave test
# - behave-deps - ensures pre-requisites are availble for running behave manually
# - gotools - installs go tools like golint
# - linter - runs all code checks
# - native - ensures all native binaries are available
# - docker[-clean] - ensures all docker images are available[/cleaned]
# - peer-docker[-clean] - ensures the peer container is available[/cleaned]
# - orderer-docker[-clean] - ensures the orderer container is available[/cleaned]
# - protos - generate all protobuf artifacts based on .proto files
# - clean - cleans the build area
# - dist-clean - superset of 'clean' that also removes persistent state
yp (Fri, 17 Feb 2017 09:46:38 GMT):
如果用docker方式的话，执行`make docker`
yp (Fri, 17 Feb 2017 09:50:25 GMT):
看错了。。出错的是gotools/Makefile。。那应该是权限问题
yp (Fri, 17 Feb 2017 09:57:01 GMT):
@yong 网上有个解决方法
yp (Fri, 17 Feb 2017 09:57:01 GMT):
It's not working because you typically need to be the "root" user to invoke make install. In the directory where you're trying to run make, Use the su command to become "root" (you'll be prompted for the password), then run make install.
Only "root" has write permissions to most of the directories and files outside of your $HOME directory. This is part of the Unix-style security paradigm.
zhenbing (Sat, 18 Feb 2017 17:28:48 GMT):
Has joined the channel.
caoyin (Sun, 19 Feb 2017 14:49:29 GMT):
Has joined the channel.
ztluo (Sun, 19 Feb 2017 15:31:26 GMT):
Has joined the channel.
HenryZhang (Sun, 19 Feb 2017 16:21:29 GMT):
Has joined the channel.
allwelder (Mon, 20 Feb 2017 15:17:49 GMT):
Has joined the channel.
Ying (Tue, 21 Feb 2017 02:31:30 GMT):
Has joined the channel.
yong (Tue, 21 Feb 2017 03:23:35 GMT):
用make all进行编译时，找不到命令。
yong (Tue, 21 Feb 2017 03:23:37 GMT):
unit-tests_1 | Running tests...
unit-tests_1 | declare -x CORE_PEER_MSPCONFIGPATH="/etc/hyperledger/fabric/msp/sampleconfig"
unit-tests_1 | declare -x CORE_VM_DOCKER_ATTACHSTDOUT="true"
unit-tests_1 | declare -x GOPATH="/opt/gopath"
unit-tests_1 | declare -x GOROOT="/opt/go"
unit-tests_1 | declare -x GO_LDFLAGS="-X github.com/hyperledger/fabric/common/metadata.Version=0.7.0-snapshot-351f1b8"
unit-tests_1 | declare -x HOME="/root"
unit-tests_1 | declare -x HOSTNAME="0db599344e53"
unit-tests_1 | declare -x OLDPWD
unit-tests_1 | declare -x ORDERER_CFG_PATH="/etc/hyperledger/fabric"
unit-tests_1 | declare -x ORDERER_GENERAL_LOCALMSPDIR="/etc/hyperledger/fabric/msp/sampleconfig"
unit-tests_1 | declare -x PATH="/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/opt/go/bin:/opt/gopath/bin"
unit-tests_1 | declare -x PEER_CFG_PATH="/etc/hyperledger/fabric"
unit-tests_1 | declare -x PWD="/opt/gopath/src/github.com/hyperledger/fabric"
unit-tests_1 | declare -x SHLVL="1"
unit-tests_1 | declare -x TEST_PKGS="github.com/hyperledger/fabric/..."
unit-tests_1 | declare -x UNITTEST_VP_1_ENV_CORE_PEER_ADDRESSAUTODETECT="true"
unit-tests_1 | declare -x UNITTEST_VP_1_ENV_CORE_PEER_MSPCONFIGPATH="/etc/hyperledger/fabric/msp/sampleconfig"
unit-tests_1 | declare -x UNITTEST_VP_1_ENV_PEER_CFG_PATH="/etc/hyperledger/fabric"
unit-tests_1 | declare -x UNITTEST_VP_1_NAME="/unittest_unit-tests_1/unittest_vp_1"
unit-tests_1 | declare -x UNITTEST_VP_1_PORT="tcp://172.17.0.2:7051"
unit-tests_1 | declare -x UNITTEST_VP_1_PORT_7051_TCP="tcp://172.17.0.2:7051"
unit-tests_1 | declare -x UNITTEST_VP_1_PORT_7051_TCP_ADDR="172.17.0.2"
unit-tests_1 | declare -x UNITTEST_VP_1_PORT_7051_TCP_PORT="7051"
unit-tests_1 | declare -x UNITTEST_VP_1_PORT_7051_TCP_PROTO="tcp"
unit-tests_1 | declare -x UNIT_TEST_PEER_IP="vp"
unit-tests_1 | declare -x VP_1_ENV_CORE_PEER_ADDRESSAUTODETECT="true"
unit-tests_1 | declare -x VP_1_ENV_CORE_PEER_MSPCONFIGPATH="/etc/hyperledger/fabric/msp/sampleconfig"
unit-tests_1 | declare -x VP_1_ENV_PEER_CFG_PATH="/etc/hyperledger/fabric"
unit-tests_1 | declare -x VP_1_NAME="/unittest_unit-tests_1/vp_1"
unit-tests_1 | declare -x VP_1_PORT="tcp://172.17.0.2:7051"
unit-tests_1 | declare -x VP_1_PORT_7051_TCP="tcp://172.17.0.2:7051"
unit-tests_1 | declare -x VP_1_PORT_7051_TCP_ADDR="172.17.0.2"
unit-tests_1 | declare -x VP_1_PORT_7051_TCP_PORT="7051"
unit-tests_1 | declare -x VP_1_PORT_7051_TCP_PROTO="tcp"
unit-tests_1 | declare -x VP_ENV_CORE_PEER_ADDRESSAUTODETECT="true"
unit-tests_1 | declare -x VP_ENV_CORE_PEER_MSPCONFIGPATH="/etc/hyperledger/fabric/msp/sampleconfig"
unit-tests_1 | declare -x VP_ENV_PEER_CFG_PATH="/etc/hyperledger/fabric"
unit-tests_1 | declare -x VP_NAME="/unittest_unit-tests_1/vp"
unit-tests_1 | declare -x VP_PORT="tcp://172.17.0.2:7051"
unit-tests_1 | declare -x VP_PORT_7051_TCP="tcp://172.17.0.2:7051"
unit-tests_1 | declare -x VP_PORT_7051_TCP_ADDR="172.17.0.2"
unit-tests_1 | declare -x VP_PORT_7051_TCP_PORT="7051"
unit-tests_1 | declare -x VP_PORT_7051_TCP_PROTO="tcp"
unit-tests_1 | ./unit-test/run.sh: line 29: gocov: command not found
unit-tests_1 | ./unit-test/run.sh: line 29: gocov-xml: command not found
yong (Tue, 21 Feb 2017 03:24:30 GMT):
绝对路径执行gocov和gocov-xml又提示没有文件
yong (Tue, 21 Feb 2017 03:25:09 GMT):
麻烦帮我看看，怎么解决？@baohua
baohua (Tue, 21 Feb 2017 04:04:53 GMT):
try `make clean; make peer`
shimron (Tue, 21 Feb 2017 08:42:52 GMT):
尝试enroll admin的时候，出现下面这个错
shimron (Tue, 21 Feb 2017 08:42:53 GMT):
vagrant@vagrant-ubuntu-trusty-64:~/fabric-ca$ fabric-ca client enroll -config client-config.json admin adminpw http://192.168.33.10:7054 csr.json
2017/02/21 08:41:19 [INFO] Fabric-ca Client Configuration File: client-config.json
open http://192.168.33.10:7054: no such file or directory
shimron (Tue, 21 Feb 2017 08:43:15 GMT):
哪位能帮忙解答下，是什么原因呢
zerppen (Tue, 21 Feb 2017 09:54:57 GMT):
请问 有在fabric源码基础上 更改java 的Chaincode进行测试过的吗
yong (Tue, 21 Feb 2017 12:06:43 GMT):
go install github.com/hyperledger/fabric/vendor/github.com/BurntSushi/toml: mkdir /opt/gopath/pkg/linux_amd64: permission denied
go install github.com/hyperledger/fabric/vendor/github.com/Sirupsen/logrus: mkdir /opt/gopath/pkg/linux_amd64: permission denied
go install github.com/hyperledger/fabric/vendor/github.com/syndtr/goleveldb/leveldb/comparer: mkdir /opt/gopath/pkg/linux_amd64: permission denied
go install github.com/hyperledger/fabric/vendor/github.com/syndtr/goleveldb/leveldb/util: open /opt/gopath/pkg/linux_amd64/github.com/hyperledger/fabric/vendor/github.com/syndtr/goleveldb/leveldb/util.a: no such file or directory
go install github.com/hyperledger/fabric/gossip/common: mkdir /opt/gopath/pkg/linux_amd64: permission denied
go install github.com/hyperledger/fabric/vendor/github.com/spf13/pflag: open /opt/gopath/pkg/linux_amd64/github.com/hyperledger/fabric/vendor/github.com/spf13/pflag.a: no such file or directory
go install github.com/hyperledger/fabric/vendor/github.com/eapache/go-resiliency/breaker: mkdir /opt/gopath/pkg/linux_amd64: permission denied
go install github.com/hyperledger/fabric/vendor/github.com/golang/snappy: mkdir /opt/gopath/pkg/linux_amd64: permission denied
go install github.com/hyperledger/fabric/vendor/github.com/eapache/queue: mkdir /opt/gopath/pkg/linux_amd64: permission denied
go install github.com/hyperledger/fabric/vendor/github.com/Knetic/govaluate: mkdir /opt/gopath/pkg/linux_amd64: permission denied
go install github.com/hyperledger/fabric/vendor/github.com/davecgh/go-spew/spew: mkdir /opt/gopath/pkg/linux_amd64: permission denied
go install github.com/hyperledger/fabric/vendor/github.com/klauspost/crc32: mkdir /opt/gopath/pkg/linux_amd64: permission denied
go install github.com/hyperledger/fabric/vendor/github.com/syndtr/goleveldb/leveldb/storage: open /opt/gopath/pkg/linux_amd64/github.com/hyperledger/fabric/vendor/github.com/syndtr/goleveldb/leveldb/storage.a: no such file or directory
go install github.com/hyperledger/fabric/vendor/github.com/golang/protobuf/proto: mkdir /opt/gopath/pkg/linux_amd64: permission denied
go install github.com/hyperledger/fabric/vendor/gopkg.in/yaml.v2: mkdir /opt/gopath/pkg/linux_amd64: permission denied
go install github.com/hyperledger/fabric/vendor/github.com/rcrowley/go-metrics: mkdir /opt/gopath/pkg/linux_amd64: permission denied
go install github.com/hyperledger/fabric/vendor/github.com/miekg/pkcs11: mkdir /opt/gopath/pkg/linux_amd64: permission denied
Makefile:133: recipe for target 'build/docker/bin/peer' failed
yong (Tue, 21 Feb 2017 12:07:09 GMT):
执行make docker的输出错误
baohua (Wed, 22 Feb 2017 00:38:15 GMT):
@shimron 看起来你指定了 `ca`的地址 http://192.168.33.10:7054 。得确保这个地址上 ca 服务启动起来了
baohua (Wed, 22 Feb 2017 00:38:28 GMT):
@yong 又是权限问题？试试 root？
yong (Wed, 22 Feb 2017 02:22:21 GMT):
@baohua 就是root权限 执行sudo -E make docker
shimron (Wed, 22 Feb 2017 02:47:25 GMT):
@baohua 问题解决了，之前用的是master上编译出binary，切换到v1.0.0-preview之后重新go install就没这个问题
aratic (Wed, 22 Feb 2017 03:42:49 GMT):
@yong 你的系统上docker装好后, 你的用户需要在docker组, 用非root用户 试一下hello-world image
shimron (Wed, 22 Feb 2017 06:34:54 GMT):
请教下，msp包下的sampleconfig几类文件分别表示什么意思，怎么去生成这些文件？
shimron (Wed, 22 Feb 2017 06:36:44 GMT):
admincerts和cacerts内容相同，应该是enroll新用户后生成的cert.pem；keystore下的应该就是用户的key.pem
shimron (Wed, 22 Feb 2017 06:37:14 GMT):
但signcerts的内容有所不同，不知道怎么去生成
shimron (Wed, 22 Feb 2017 06:38:27 GMT):
还是说这个signcert下的文件其实是fabric-ca server init后生成的server-cert.pem ?
ZengLingYou (Wed, 22 Feb 2017 07:08:28 GMT):
Has joined the channel.
ZengLingYou (Wed, 22 Feb 2017 07:10:19 GMT):
刚开始接触hyperledger, win10下能直接用go开发fabric吗，还是一定要在Linux下？
ZengLingYou (Wed, 22 Feb 2017 07:13:48 GMT):
或者一定要装vagrant?
ZengLingYou (Wed, 22 Feb 2017 07:15:05 GMT):
我只安装了go, 编译就报错了，..\..\..\..\vendor\github.com\miekg\pkcs11\pkcs11.go:29:18: fatal error: ltdl.h: No such file or directory
aratic (Wed, 22 Feb 2017 07:15:12 GMT):
先看文档, 然后嗯, 听说是有人在Windows下开发, 用Vagrant弄的Ubuntu的虚拟机
aratic (Wed, 22 Feb 2017 07:16:02 GMT):
满世界的依赖关系, 个人觉得直接用Windows会比装个虚拟机来的麻烦
aratic (Wed, 22 Feb 2017 07:19:05 GMT):
我从gerrit拉下来代码make总有些奇怪的go的unrecognized import, 网页打开库的地址能看, 但是go get 就报错或者超时, 即使开了代理, 蛮奇怪, 以前没碰到(虽然有些第三方依赖要手动装
aratic (Wed, 22 Feb 2017 07:20:06 GMT):
这里还是打算抹掉, 看文档慢慢重来 = =
ZengLingYou (Wed, 22 Feb 2017 07:21:21 GMT):
感觉国内的网络是个硬伤，go get很多次才搞下来那些import.
ZengLingYou (Wed, 22 Feb 2017 07:22:19 GMT):
结果还是编译不了，没有gcc, 搞好gcc,继续报错，好麻烦的
aratic (Wed, 22 Feb 2017 07:22:36 GMT):
以前docker里的image都在墙后面, 挂代理半天下1G断了那才叫哭, 直接在Linode开个国外的机器就是秒过
aratic (Wed, 22 Feb 2017 07:23:43 GMT):
你在windows下玩gcc啊, 感觉移植的不好使, 虽然有mingw32什么的,
ZengLingYou (Wed, 22 Feb 2017 07:24:00 GMT):
本来想在docker里拉个image玩的，结果半夜里面断了，就放弃了。
ZengLingYou (Wed, 22 Feb 2017 07:24:11 GMT):
mingw64
aratic (Wed, 22 Feb 2017 08:06:47 GMT):
抹掉重新来make就过了, 可能是以前下载现在不用的依赖包的问题, 或者我过程中不小心用了sudo, 不管了
aratic (Wed, 22 Feb 2017 08:23:42 GMT):
折腾半天, 原来Debian上的golang默认是1.3 需求1.7+ 真是.
Eagel (Wed, 22 Feb 2017 08:32:05 GMT):
我有编译好的"v1.0.0-preview" docker 镜像，需要吗？
Eagel (Wed, 22 Feb 2017 08:32:53 GMT):
REPOSITORY TAG IMAGE ID CREATED SIZE
hyperledger/fabric-ca latest 815af98a859c 5 days ago 184 MB
hyperledger/fabric-ca x86_64-0.7.0-snapshot-179a307 815af98a859c 5 days ago 184 MB
hyperledger/fabric-kafka latest 2aa8ab0fb34e 6 days ago 1.3 GB
hyperledger/fabric-kafka x86_64-0.7.0-snapshot-c7b3fe0 2aa8ab0fb34e 6 days ago 1.3 GB
hyperledger/fabric-zookeeper latest 0bc1f31a99c6 6 days ago 1.31 GB
hyperledger/fabric-zookeeper x86_64-0.7.0-snapshot-c7b3fe0 0bc1f31a99c6 6 days ago 1.31 GB
hyperledger/fabric-testenv latest 7b2d514b62e8 6 days ago 1.39 GB
hyperledger/fabric-testenv x86_64-0.7.0-snapshot-c7b3fe0 7b2d514b62e8 6 days ago 1.39 GB
hyperledger/fabric-orderer latest 93448fbea638 6 days ago 179 MB
hyperledger/fabric-orderer x86_64-0.7.0-snapshot-c7b3fe0 93448fbea638 6 days ago 179 MB
hyperledger/fabric-peer latest 32406efefe8b 6 days ago 183 MB
hyperledger/fabric-peer x86_64-0.7.0-snapshot-c7b3fe0 32406efefe8b 6 days ago 183 MB
hyperledger/fabric-javaenv latest c4cb0322d2ef 6 days ago 1.42 GB
hyperledger/fabric-javaenv x86_64-0.7.0-snapshot-c7b3fe0 c4cb0322d2ef 6 days ago 1.42 GB
hyperledger/fabric-ccenv latest 4b574559fac3 6 days ago 1.29 GB
hyperledger/fabric-ccenv x86_64-0.7.0-snapshot-c7b3fe0 4b574559fac3 6 days ago 1.29 GB
hyperledger/fabric-baseimage x86_64-0.3.0 f4751a503f02 3 weeks ago 1.27 GB
hyperledger/fabric-baseos x86_64-0.3.0 c3a4cf3b3350 3 weeks ago 161 MB
Eagel (Wed, 22 Feb 2017 08:34:44 GMT):
大概468.6MB，需要的话我上传云盘分享给大家
aratic (Wed, 22 Feb 2017 08:34:52 GMT):
谢谢, 我这里再试试, 搞不定再单独找你要 :)
Eagel (Wed, 22 Feb 2017 08:35:39 GMT):
..\..\..\..\vendor\github.com\miekg\pkcs11\pkcs11.go:29:18: fatal error: ltdl.h: No such file or directory
Eagel (Wed, 22 Feb 2017 08:36:08 GMT):
这个问题是缺少libtool的头文件
Eagel (Wed, 22 Feb 2017 08:36:30 GMT):
自己编编译一个，或者装个就好了
guhaihua (Wed, 22 Feb 2017 08:36:55 GMT):
@shimron 用fabric-ca最新版，使用fabric-ca-server 和fabric-ca-client来enroll
shimron (Wed, 22 Feb 2017 08:37:00 GMT):
可以先试试make gotools， 成功的话再make docker，我是这么搞的 还算顺利
shimron (Wed, 22 Feb 2017 08:37:40 GMT):
@guhaihua singcert文件下的pem是咋生成的
Eagel (Wed, 22 Feb 2017 08:40:01 GMT):
fabric-ca 都是参考啥文档在用，我都没成功的enroll过
guhaihua (Wed, 22 Feb 2017 08:51:46 GMT):
@Eagel 我在gerrit上提交一个readme：https://gerrit.hyperledger.org/r/#/c/6275/，可以enroll成功
shimron (Wed, 22 Feb 2017 08:56:52 GMT):
https://github.com/hyperledger/fabric/blob/v1.0.0-preview/docs/Setup/ca-setup.md
shimron (Wed, 22 Feb 2017 08:57:04 GMT):
这里有个，目前我参照的是它
Eagel (Wed, 22 Feb 2017 09:00:32 GMT):
谢谢了，我试试
shimron (Wed, 22 Feb 2017 09:03:02 GMT):
@guhaihua 我目前启动了一个ca服务和一个orderer服务，现在想加入一个peer进去，该怎么弄呢？证书要怎么生成？我看了peer的main函数里，默认读取了msp/sampleconfig下的证书
zerppen (Wed, 22 Feb 2017 09:12:48 GMT):
请问一下 我执行make peer后 里面的examples测试成功。后改动chaincode/java部分源码，启动时报了以下错误，需要重新执行make peer操作吗？
zerppen (Wed, 22 Feb 2017 09:13:06 GMT):
16:53:53.658 [dockercontroller] deployImage -> ERRO 017 Error building images: dial unix /var/run/docker.sock: connect: connection refused
16:53:53.659 [dockercontroller] deployImage -> ERRO 018 Image Output:
********************
********************
16:53:53.661 [dockercontroller] Start -> ERRO 019 start-could not recreate container cannot connect to Docker endpoint
16:53:53.661 [chaincode] Launch -> ERRO 01a launchAndWaitForRegister failed Error starting container: cannot connect to Docker endpoint
zerppen (Wed, 22 Feb 2017 09:14:39 GMT):
我用gradle编译时没有抛异常
liutc (Thu, 23 Feb 2017 03:10:49 GMT):
有兄弟了解1.0 java sdk里面对enroll用户支持的情况么？现在还是todo，有计划啥时候做么？
grapebaba (Thu, 23 Feb 2017 06:57:22 GMT):
有没有朋友有兴趣和时间帮我们一起实现fabric python SDK的，可以私信 @baohua
baohua (Thu, 23 Feb 2017 07:10:38 GMT):
python sdk 是继 node sdk 后，社区又一大着力点！欢迎感兴趣的志愿者一起来开发：https://wiki.hyperledger.org/projects/fabric-sdk-py.md！
aratic (Thu, 23 Feb 2017 07:12:46 GMT):
这里是思捷, 我能写python, 但是目前换了机器, 还在弄代理/环境
aratic (Thu, 23 Feb 2017 07:15:19 GMT):
先尝试用用, 之前看过go/java的SDK
grapebaba (Thu, 23 Feb 2017 07:24:29 GMT):
欢迎
aratic (Thu, 23 Feb 2017 07:26:28 GMT):
fabric-sdk-py的makefile, docker直接指到了yeasy, 哈哈 (目前还在围观Jira, 看啥时候能插上手 :) )
aratic (Thu, 23 Feb 2017 07:33:43 GMT):
我先过一下meeting minutes跟gerrit, 看最近在搞啥, 能参与写sdk的机会可不多, 嘿嘿
liuzhudong (Thu, 23 Feb 2017 07:43:19 GMT):
Has joined the channel.
CarlXK (Thu, 23 Feb 2017 08:02:53 GMT):
Has joined the channel.
aratic (Thu, 23 Feb 2017 09:39:26 GMT):
有个问题想问一下, fabric有法律条款/合规的考量么, 没找着文档, 我上次在深圳福田, Yaoguo回答的问题里有涉及到的可能的方法, 在链上记载形如外部扫描件的base64, 或者引用条款的哈希值, 但如何产生确定效力, 还得搭建这个区块链的主人自已操心哈?
baohua (Thu, 23 Feb 2017 13:47:23 GMT):
这个跟电子证据一样 除了技术上提高可信度 也需要一些非技术方面的考量。 明天上午的 sdk 例会，欢迎参加。https://wiki.hyperledger.org/projects/fabric-sdk-py/meetings/20170224.md
ray (Thu, 23 Feb 2017 17:10:28 GMT):
https://chat.hyperledger.org/channel/fabric-sdk-py
it says: No channel with name "fabric-sdk-py" was found!
baohua (Fri, 24 Feb 2017 01:06:17 GMT):
strange @rjones several people report this not found error. @ray let me invite u.
rjones (Fri, 24 Feb 2017 01:06:18 GMT):
Has joined the channel.
rjones (Fri, 24 Feb 2017 02:07:34 GMT):
@baohua invite me as well please
aratic (Fri, 24 Feb 2017 03:53:35 GMT):
@baohua invite me as well please, even it seems too late = =
baohua (Fri, 24 Feb 2017 04:00:02 GMT):
done
CarlXK (Fri, 24 Feb 2017 06:45:36 GMT):
fabric的代码该从哪里看起，有人给指条路？
jiangyaoguo (Fri, 24 Feb 2017 07:09:07 GMT):
可以先从设计文档看起，看完设计再根据自己的兴趣找到对应的模块代码看起
jiangyaoguo (Fri, 24 Feb 2017 07:11:47 GMT):
@CarlXK
jiangyaoguo (Fri, 24 Feb 2017 07:19:54 GMT):
https://github.com/hyperledger/fabric/blob/master/docs/abstract_v1.md
CarlXK (Fri, 24 Feb 2017 07:23:54 GMT):
好的，谢谢
aratic (Fri, 24 Feb 2017 09:07:36 GMT):
有个中国特色的问题想问一下, 大家是怎么解决网络问题的, 我有socket (shadowsocks / proxychains) 代理但是docker / vagrant 里头默认没走代理, 而且配置了的话好像跟他自治的网络有冲突, 总是会有些依赖包需要fetch, 是他俩网络配置比较麻烦么, 怎么饶过的呢, 有思考/参考方向是再好不过 :)
Ying (Fri, 24 Feb 2017 09:14:41 GMT):
[ ](https://chat.hyperledger.org/channel/twg-china?msg=Korxtj8XJiXn6nWur) @aratic 到云上开个虚机就搞定啦，欢迎光顾京东云
aratic (Fri, 24 Feb 2017 09:59:55 GMT):
啊哈? 我以前是在Linode租的机器解决的问题, 现在在国内的供应商, 你们的机器能读google? 需要我留档么 (怕 =__=
ray (Fri, 24 Feb 2017 10:24:18 GMT):
[ ](https://chat.hyperledger.org/channel/twg-china?msg=Korxtj8XJiXn6nWur) @aratic
https://hyperledger-fabric.readthedocs.io/en/latest/dev-setup/devenv/#notes
vagrant plugin: vagrant-proxyconf
zerppen (Sun, 26 Feb 2017 05:00:02 GMT):
请问一下大家，我按照JAVAChaincode.md执行deploy/invoke/query.我用的fabric v0.6的源码执行SimpleSample没有问题;更改过core/chaincode/shim/java/src/main/java/org/hyperledger/java/shim下面的几处代码后,make clean再make peer 没有报异常（build.gradle中添加了依赖） 但是测试SimpleSample就来问题了。第一次query的时候，提示『Error: Error querying chaincode: rpc error: code = 2 desc = Error:Failed to launch chaincode spec(premature execution - chaincode (27cb2925013a5e8f27b41be748e6767c3fbc7bfdfe2453c2640f9069e75c4db38735fa3b6b8cac78e212a1c97193f3bfb2f9b810ce0a11f437a96b330d508fbd) is being launched)』 这里我的理解是chaincode正在运行，后几次执行query也得到相应结果。大约2分钟左右后，提示『Error: Error querying chaincode: rpc error: code = 2 desc = Error:Failed to launch chaincode spec(Could not get deployment transaction for 27cb2925013a5e8f27b41be748e6767c3fbc7bfdfe2453c2640f9069e75c4db38735fa3b6b8cac78e212a1c97193f3bfb2f9b810ce0a11f437a96b330d508fbd - LedgerError - ResourceNotFound: ledger: resource not found)
』 查看 peer node日志，显示『12:45:36.183 [chaincode] Launch -> ERRO 01a launchAndWaitForRegister failed Timeout expired while starting chaincode 27cb2925013a5e8f27b41be748e6767c3fbc7bfdfe2453c2640f9069e75c4db38735fa3b6b8cac78e212a1c97193f3bfb2f9b810ce0a11f437a96b330d508fbd(networkid:dev,peerid:jdoe,tx:27cb2925013a5e8f27b41be748e6767c3fbc7bfdfe2453c2640f9069e75c4db38735fa3b6b8cac78e212a1c97193f3bfb2f9b810ce0a11f437a96b330d508fbd)』 反复多次，都是这个结果
aratic (Sun, 26 Feb 2017 05:38:10 GMT):
我翻到一篇docker的文章，看到引用的名字很熟悉， 是yeasy， 还挺早， 哈哈， https://www.gitbook.com/book/philipzheng/docker_practice/details
aratic (Sun, 26 Feb 2017 05:58:37 GMT):
谢谢! @ray
baohua (Sun, 26 Feb 2017 10:38:58 GMT):
Dear all
We will have the group meeting at 10AM next Wednesday morning, please feel free to update the attendee list and the agenda before the join. Thanks!
https://wiki.hyperledger.org/groups/twgc/meeting/2017-03-01
silentspark (Mon, 27 Feb 2017 02:57:20 GMT):
Has joined the channel.
stevenkcolin (Tue, 28 Feb 2017 01:36:36 GMT):
Has joined the channel.
stevenkcolin (Tue, 28 Feb 2017 01:37:02 GMT):
hello, baohua,, hello everyone
stevenkcolin (Tue, 28 Feb 2017 01:38:15 GMT):
我是陈琳，区块链技术爱好者，区块链学堂作者，正在研究超级账本技术，很高兴认识大家。
jiangyaoguo (Tue, 28 Feb 2017 02:02:15 GMT):
欢迎
baohua (Tue, 28 Feb 2017 02:05:17 GMT):
how to contribute to hyperledger lifecycle, welcome for comments!
baohua (Tue, 28 Feb 2017 02:05:21 GMT):
Message Attachments
baohua (Wed, 01 Mar 2017 01:48:40 GMT):
Dear all, today's meeting agenda can be found at https://wiki.hyperledger.org/groups/twgc/meeting/2017-03-01.
baohua (Wed, 01 Mar 2017 01:52:13 GMT):
Number: 800-820-0027 (toll free) and 400-821-0751 (caller paid)
Passcode: 71173794
baohua (Wed, 01 Mar 2017 02:23:09 GMT):
@scott-long
scott-long (Wed, 01 Mar 2017 02:23:09 GMT):
Has joined the channel.
scott-long (Wed, 01 Mar 2017 02:23:22 GMT):
Thanks
CarlXK (Wed, 01 Mar 2017 02:50:32 GMT):
1. peer是由channel创建者来邀请加入的
2. peer加入channel后可以自行install和instantiate chaincode
加入channel的peer节点拥有者可以拿到所有数据？那peer只能有选择(某些联盟成员)或者中心化的来部署？
CarlXK (Wed, 01 Mar 2017 02:59:23 GMT):
@jiangyaoguo @baohua
jiangyaoguo (Wed, 01 Mar 2017 03:09:14 GMT):
@CarlXK 中心化部署的意思是？
CarlXK (Wed, 01 Mar 2017 03:10:53 GMT):
不能所有联盟成员都部署一个peer，有的时候并不想让联盟成员都看到所有信息，毕竟联盟成员的信息地位可能也不对等
CarlXK (Wed, 01 Mar 2017 03:11:23 GMT):
中心化部署就是，比如技术提供放为整个联盟提供服务，就让技术方来中心化部署所有peer order
CarlXK (Wed, 01 Mar 2017 03:14:22 GMT):
银行 核心企业 供应商 ； 在一个channel上面，并不想让供应商看到 核心企业和银行之间的交易信息
CarlXK (Wed, 01 Mar 2017 03:16:30 GMT):
能做到么
CarlXK (Wed, 01 Mar 2017 03:18:22 GMT):
3个银行 1个核心企业 5家供应商 ； 在一个channel上面，并不想让供应商之间互相看到 或者 银行之间互相看到
CarlXK (Wed, 01 Mar 2017 03:23:39 GMT):
难道设计的时候，每三方（银行、核心企业、供应商）都要有一个channel？ 这样channel会不会太多……
baohua (Wed, 01 Mar 2017 03:28:44 GMT):
channel 不重，如果强调隔离性的话 用 channel 是比较合适的选择
CarlXK (Wed, 01 Mar 2017 03:38:19 GMT):
cc也不重么
CarlXK (Wed, 01 Mar 2017 03:40:59 GMT):
因为这样cc也会很多，而且大部分都是类似的cc
CarlXK (Wed, 01 Mar 2017 03:41:40 GMT):
多channel之间能公用cc么
jiangyaoguo (Wed, 01 Mar 2017 03:42:24 GMT):
目前的模型应该还没考虑channel内再进行一些交易隔离
jiangyaoguo (Wed, 01 Mar 2017 03:42:40 GMT):
channel间cc的代码是可以共享的，数据不共享
CarlXK (Wed, 01 Mar 2017 03:44:13 GMT):
会在后续版本考虑channel内的交易隔离么，如果现在用channel来隔离意味着以后就一直会这样了
jiangyaoguo (Wed, 01 Mar 2017 05:38:38 GMT):
如果不想让某些节点看到数据，就不要让这个节点加入channel，不同的数据可视范围划分不同的channel，节点可以选择不同的channel加入，加入多个channel也不冲突，不一定要在channel内再隔离
jiangyaoguo (Wed, 01 Mar 2017 05:39:27 GMT):
有什么样的需求一定要channel内再隔离吗？
xixuejia (Wed, 01 Mar 2017 06:16:15 GMT):
我也在考虑这个问题，如果channel内的所有参与者都有权限记账的话，那它可能看到它本没有权限查看的state账本。那么同一个channel的参与者是否都应该有权限拥有记账节点呢?
CarlXK (Wed, 01 Mar 2017 06:44:25 GMT):
倒没有一定要强求在channel中进行隔离，只是用channel隔离会造成channel太多的问题，不知道后续会不会对架构或维护上造成一些麻烦
CarlXK (Wed, 01 Mar 2017 06:45:16 GMT):
只能走一步看一步
jiangyaoguo (Wed, 01 Mar 2017 06:47:30 GMT):
channel内记账的权限可以在chaincode内做一些限制，但是同一个channel内目前state应该是公开的，大家都可以看到
CarlXK (Wed, 01 Mar 2017 06:50:05 GMT):
channel上，用cc是可以做一些用户(非peer拥有方)的权限控制的
也就是对User可以做权限控制，但是不能对peer做控制
xixuejia (Wed, 01 Mar 2017 06:58:29 GMT):
所以说一个channel内只适合做私有链，不适合联盟链?
CarlXK (Wed, 01 Mar 2017 07:01:14 GMT):
联盟链也可以，但是账本上所有都是共享
CarlXK (Wed, 01 Mar 2017 07:08:49 GMT):
fabric-ca生成的证书，怎么放到peer/order/cli里面，这个有个sample么 @baohua @jiangyaoguo
CarlXK (Wed, 01 Mar 2017 07:11:11 GMT):
一直没有看到有关于这方面的描述，原来gettingstarted里面用的是生成的证书，可是也没说怎么生成的
CarlXK (Wed, 01 Mar 2017 07:11:27 GMT):
有相关文档么
rayoo (Wed, 01 Mar 2017 07:14:09 GMT):
Has joined the channel.
rayoo (Wed, 01 Mar 2017 07:24:14 GMT):
@baohua 请问Fabric 1.0把权限管理去掉了吗? 0.6中还有的
CarlXK (Wed, 01 Mar 2017 07:31:18 GMT):
权限管理没去掉
CarlXK (Wed, 01 Mar 2017 07:31:37 GMT):
以前叫membership，现在叫ca
fallingarrow (Wed, 01 Mar 2017 07:31:47 GMT):
Has joined the channel.
Donald Liu (Wed, 01 Mar 2017 07:39:49 GMT):
[ ](https://chat.hyperledger.org/channel/twg-china?msg=5HyyfHSXCrs4wPQod) @CarlXK http://hyperledger-fabric.readthedocs.io/en/latest/Setup/ca-setup/
rjones (Wed, 01 Mar 2017 08:01:51 GMT):
Has left the channel.
ray (Wed, 01 Mar 2017 10:40:02 GMT):
Some guy asked via mailing list: did we get any ready-to-deploy env just like the one described in "getting started" doc but support SBFT ordering service?
FlyingTiger (Thu, 02 Mar 2017 01:21:09 GMT):
Has joined the channel.
baohua (Thu, 02 Mar 2017 01:34:00 GMT):
aha, the getting started one does not use SBFT, but it should support SBFT, i guess.
baohua (Thu, 02 Mar 2017 02:49:18 GMT):
@ray bad news, SBFT is not ready :violin:
ray (Thu, 02 Mar 2017 02:56:42 GMT):
Okay, I will reply that mail and try to explain it. I read the code and think it's not ready too (config flag is ignored), but I need to confirm it ;-)
Liew.SC (Thu, 02 Mar 2017 02:58:30 GMT):
Has joined the channel.
yong (Thu, 02 Mar 2017 06:19:15 GMT):
@baohua [yong@bogon fabric]$ sudo -E make docker
Building build/docker/bin/peer
# github.com/hyperledger/fabric/vendor/github.com/miekg/pkcs11
vendor/github.com/miekg/pkcs11/pkcs11.go:29:18: fatal error: ltdl.h: No such file or directory
#include
yong (Thu, 02 Mar 2017 06:20:31 GMT):
我安装了ltdl开发包，但依然提示错误。而且代码上看，应该是被屏蔽了的
Eagel (Thu, 02 Mar 2017 07:13:17 GMT):
我也遇到这个问题
Eagel (Thu, 02 Mar 2017 07:13:29 GMT):
我直接改了下Makefile
Eagel (Thu, 02 Mar 2017 07:13:42 GMT):
CGO_FLAGS = CGO_CFLAGS=" -I/Users/xxxxxx/usr/include"
yong (Thu, 02 Mar 2017 07:14:14 GMT):
@Eagel OK,我马上试试
Eagel (Thu, 02 Mar 2017 07:14:22 GMT):
还改了下fabric/vendor/github.com/miekg/pkcs11源文件
Eagel (Thu, 02 Mar 2017 07:14:39 GMT):
#cgo darwin LDFLAGS: -lltdl -L/usr/local/lib/ -I/usr/local/share/libtool -L/Users/xxxxxxxx/usr/lib
Eagel (Thu, 02 Mar 2017 07:16:09 GMT):
我编译安装libtool的prefix是/Users/xxxxxx/usr
Eagel (Thu, 02 Mar 2017 07:16:18 GMT):
这个根据你自己的环境来
Eagel (Thu, 02 Mar 2017 07:17:25 GMT):
pkcs11.go,这个文件
WeiweiZhong (Thu, 02 Mar 2017 08:09:26 GMT):
Has joined the channel.
yong (Thu, 02 Mar 2017 08:33:55 GMT):
@Eagel 我按照你的方法改了，还是不性。我是直接安装在/usr/local/include目录下的，我用gcc 编译引用ltdl头文件和库，都可以。但就是不行。
baohua (Thu, 02 Mar 2017 09:19:34 GMT):
@yong 我刚试了最新代码 普通用户下 `make peer` 没问题，`make docker` 卡在网络拉包上了 :bicyclist:
yong (Thu, 02 Mar 2017 09:51:35 GMT):
@baohua 我这儿还是老问题，不关怎么弄，依然如此
yong (Thu, 02 Mar 2017 09:52:20 GMT):
make peer也没问题
baohua (Thu, 02 Mar 2017 12:22:03 GMT):
嗯 去 fabric 或 fabric-ci channel 问问看看
Ying (Thu, 02 Mar 2017 23:35:43 GMT):
[ ](https://chat.hyperledger.org/channel/twg-china?msg=DDyci3QCCcoSBaWBa) @baohua 你放在dockerhub
Ying (Thu, 02 Mar 2017 23:40:13 GMT):
[ ](https://chat.hyperledger.org/channel/twg-china?msg=DDyci3QCCcoSBaWBa) @baohua 你放在dockerhub上的最新镜像有启动的compose文件吗？我试着起了一次，peer和ca似乎不能连上。谢谢。
baohua (Fri, 03 Mar 2017 01:18:21 GMT):
FYI. https://github.com/yeasy/docker-compose-files/blob/master/hyperledger/1.0/
CarlXK (Fri, 03 Mar 2017 03:26:05 GMT):
➜ source git:(master) docker-compose -f docker-2peer.yml up
Creating network "source_bridge" with the default driver
Creating orderer
Creating peer0
Creating peer1
ERROR: for peer1 Cannot start service peer1: Mounts denied: amespaces for more info.
.
/src/github.com/hyperledger/fabric/examples
is not shared from OS X and is not known to Docker.
You can configure shared paths from Docker -> Preferences... -> File Sharing.
See https://docs.docker.com/docker-for-mac/osxfs/#n
ERROR: for peer0 Cannot start service peer0: Mounts denied: amespaces for more info.
.
/src/github.com/hyperledger/fabric/examples
is not shared from OS X and is not known to Docker.
You can configure shared paths from Docker -> Preferences... -> File Sharing.
See https://docs.docker.com/docker-for-mac/osxfs/#n
ERROR: Encountered errors while bringing up the project.
CarlXK (Fri, 03 Mar 2017 03:26:31 GMT):
@baohua 直接在mac上面编译然后启动报这个错误
CarlXK (Fri, 03 Mar 2017 03:28:02 GMT):
为什么会报¥not shared, 我整个/User都是在shared目录中国
baohua (Fri, 03 Mar 2017 03:28:16 GMT):
seems problem with mac-docker, can u find some linux server to try?
CarlXK (Fri, 03 Mar 2017 03:28:46 GMT):
用vagrant就没有这个问题
baohua (Fri, 03 Mar 2017 03:31:28 GMT):
because vagrant boots up a linux ....
baohua (Fri, 03 Mar 2017 03:34:08 GMT):
btw are u using docker mac, remember do not use docker toolbox...
CarlXK (Fri, 03 Mar 2017 03:36:51 GMT):
using docker for mac
Ying (Fri, 03 Mar 2017 07:44:44 GMT):
[ ](https://chat.hyperledger.org/channel/twg-china?msg=fg2EqQbfRmvzbKoG2) @baohua 太感谢啦！
liuzhudong (Fri, 03 Mar 2017 08:17:08 GMT):
@baohua 现在fabric执行一次交易大概要多长时间啊，我这边测试发现invoke 成功之后query值没有改变，要等一段时间才修改啊，是电脑问题么
baohua (Fri, 03 Mar 2017 08:24:03 GMT):
发下你具体的部署环境看看？正常挺快的
liuzhudong (Fri, 03 Mar 2017 08:25:43 GMT):
正常是多久呢，我这边要20 -- 30秒左右才可以查到值
baohua (Fri, 03 Mar 2017 08:27:58 GMT):
得看你这边具体情况了 包括咋测的 这种数据没有统一前提下 不好比较
stevenkcolin (Sat, 04 Mar 2017 04:55:42 GMT):
@baohua 我想问个很简单的问题。
stevenkcolin (Sat, 04 Mar 2017 04:55:45 GMT):
peer chaincode install -n test_ac -p github.com/hyperledger/fabric/examples/chaincode/go/chaincode_example02
stevenkcolin (Sat, 04 Mar 2017 04:56:26 GMT):
这里我发现这个代码地址 github.com/hyperledger/fabric/examples/chaincode/go/chaincode_example02 是本地的。（因为我断网也能部署成功）
stevenkcolin (Sat, 04 Mar 2017 04:56:45 GMT):
但我找不到他的绝对路径在哪里
stevenkcolin (Sat, 04 Mar 2017 05:36:26 GMT):
我重新说下我的问题，我进入了peer0的地址
LindeMacBook-Pro:/ linchen$ docker exec -it fabric-peer0 bash
root@peer0:/go/src/github.com/hyperledger/fabric#
我的问题是 /go/src/github.com/hyperledger/fabric这是个相对路径，我想找到/go/src的绝对路径在哪里。
baohua (Sat, 04 Mar 2017 09:25:55 GMT):
`/go/src/github.com/hyperledger/fabric` 这个是绝对路径 chaincode 就在下面的 examples/....里
stevenkcolin (Sun, 05 Mar 2017 00:12:32 GMT):
早
zhangguangfeng (Sun, 05 Mar 2017 15:07:27 GMT):
Has joined the channel.
yong (Mon, 06 Mar 2017 03:13:55 GMT):
root@fu-yong:/opt/gopath/src/github.com/hyperledger/fabric/docs/source# docker-compose -f docker-2peer.yml up
Starting orderer
Starting peer1
Starting peer0
Starting cli
Attaching to orderer, peer0, peer1, cli
orderer | standard_init_linux.go:178: exec user process caused "exec format error"
peer0 | standard_init_linux.go:178: exec user process caused "exec format error"
orderer exited with code 1
peer1 | standard_init_linux.go:178: exec user process caused "exec format error"
peer0 exited with code 1
peer1 exited with code 1
^CGracefully stopping... (press Ctrl+C again to force)
Stopping cli ... done
yong (Mon, 06 Mar 2017 03:15:08 GMT):
我的docker版本信息是：
yong (Mon, 06 Mar 2017 03:15:09 GMT):
root@fu-yong:/opt/gopath/src/github.com/hyperledger/fabric/docs/source# docker version
Client:
Version: 17.03.0-ce
API version: 1.26
Go version: go1.7.5
Git commit: 3a232c8
Built: Tue Feb 28 08:01:32 2017
OS/Arch: linux/amd64
Server:
Version: 17.03.0-ce
API version: 1.26 (minimum version 1.12)
Go version: go1.7.5
Git commit: 3a232c8
Built: Tue Feb 28 08:01:32 2017
OS/Arch: linux/amd64
Experimental: false
CarlXK (Wed, 08 Mar 2017 07:15:47 GMT):
channel之间的chaincode在后续版本可以互相调用嘛
Hangyu (Wed, 08 Mar 2017 07:46:18 GMT):
现在就可以调用啊，不过只能·query，即使invoke对账本也没有任何影响
CarlXK (Wed, 08 Mar 2017 07:55:32 GMT):
channel之间啊，不是channel内部哦
baohua (Wed, 08 Mar 2017 07:57:19 GMT):
我记得目前是 可能会读到 但不可以写
CarlXK (Wed, 08 Mar 2017 08:10:29 GMT):
OK
CarlXK (Wed, 08 Mar 2017 08:11:01 GMT):
cryptogen这个工具做完了么，生成证书的时候不需要用到root certificates？
CarlXK (Wed, 08 Mar 2017 08:12:10 GMT):
我看他就自己生成了ca的证书……而且是一个组织一个root 根证书，按道理来说不是该一个组织是一个intermedia ca server 么
CarlXK (Wed, 08 Mar 2017 08:13:16 GMT):
cryptogen应该用root certificates来 生成intermedia ca server证书及其他证书才对啊
Hangyu (Wed, 08 Mar 2017 08:13:37 GMT):
刚刚执行了一下example04，channel间chaincode之间可以调用，invoke的话对账本没有任何影响，但是query可以
CarlXK (Wed, 08 Mar 2017 08:14:24 GMT):
peer要同时join到两个channel对吧
Hangyu (Wed, 08 Mar 2017 08:14:36 GMT):
对的
CarlXK (Wed, 08 Mar 2017 08:38:46 GMT):
Message Attachments
CarlXK (Wed, 08 Mar 2017 08:39:58 GMT):
@Hangyu @baohua 看下图里面的状况，我理解是不可以调用，未来版本会不会加入授权调用……虽然实现上看起来有点复杂
CarlXK (Wed, 08 Mar 2017 08:41:20 GMT):
类似于两个进程，cc是模块代码，channel是数据库， 同一个进程内部代码模块调用没有问题，跨进程间呢
baohua (Wed, 08 Mar 2017 08:41:29 GMT):
1.0里面应该不会允许 对其它 cc 空间的写
CarlXK (Wed, 08 Mar 2017 08:45:06 GMT):
要是能调用就好了，要不然只能应用自己处理
Ying (Thu, 09 Mar 2017 01:17:06 GMT):
各位早～请问怎么注册JIRA账户？谢谢
Not a member? To request an account, please contact your JIRA administrators.
CarlXK (Thu, 09 Mar 2017 01:19:47 GMT):
跟 gerrit一样，用Linux Foundation ID
Ying (Thu, 09 Mar 2017 01:22:09 GMT):
喔～我试试，谢谢@CarlXK
baohua (Thu, 09 Mar 2017 01:37:16 GMT):
@hightall
hightall (Thu, 09 Mar 2017 01:37:16 GMT):
Has joined the channel.
CarlXK (Thu, 09 Mar 2017 05:17:05 GMT):
Message Attachments
CarlXK (Thu, 09 Mar 2017 05:19:29 GMT):
@baohua @Ying @Hangyu
Could peer0's certificate be signed by both root CAs (or intermediate CAs) in org1 and org2?
One organization should be all banks(bank1 bank2 bank……) or mixed business parties(bank1, corp1, corp2), or both ok?
One root CA (or intermediate CA) should be only bind with one orgnization or can cross multi orgnization?
Ying (Thu, 09 Mar 2017 05:24:31 GMT):
[ ](https://chat.hyperledger.org/channel/twg-china?msg=yKwQPyXJuTQp2ycFy) @CarlXK 没试过
CarlXK (Thu, 09 Mar 2017 05:36:21 GMT):
唉，看不懂代码就是烦啊，搞不清这些问题
baohua (Thu, 09 Mar 2017 06:47:45 GMT):
i guess not, let's confirm at the fabric-ca channel
CarlXK (Thu, 09 Mar 2017 06:49:56 GMT):
i bring these questions to fabric-crypto channel, but no one answer it :joy:
CarlXK (Thu, 09 Mar 2017 06:53:45 GMT):
i guess this could be happened, it's reasonable
CarlXK (Thu, 09 Mar 2017 06:54:59 GMT):
also bring it to #fabric-ca channel
YE.Yaocheng (Fri, 10 Mar 2017 03:20:00 GMT):
Has joined the channel.
kuangchao (Fri, 10 Mar 2017 03:47:18 GMT):
Has joined the channel.
AlanLee (Fri, 10 Mar 2017 04:19:19 GMT):
Has joined the channel.
CarlXK (Fri, 10 Mar 2017 07:10:55 GMT):
@baohua fabric里auditor怎么进行审计，大概是个怎么样的过程，这个在做了还是在规划
CarlXK (Fri, 10 Mar 2017 08:05:20 GMT):
在哪里设置block的生成规则？
JatinderBali (Fri, 10 Mar 2017 15:55:27 GMT):
Has joined the channel.
baohua (Mon, 13 Mar 2017 03:43:42 GMT):
Dear all, we will have meeting this Wendesday morning at 10 AM, pls help update the agenda and the attendee list, thanks! https://wiki.hyperledger.org/groups/twgc/meeting/2017-03-15
CarlXK (Mon, 13 Mar 2017 06:24:10 GMT):
@baohua @Hangyu fabric现在存储用couchdb，大文件存储也跟couchdb一样还是说另外封装了其他机制？
baohua (Mon, 13 Mar 2017 06:24:58 GMT):
大文件不建议 完整上 chain 毕竟不是纯数据库
CarlXK (Mon, 13 Mar 2017 06:25:42 GMT):
基本的图片文件应该还是没问题吧 5- 10M
baohua (Mon, 13 Mar 2017 06:26:45 GMT):
没限制 只是不建议 :)
CarlXK (Mon, 13 Mar 2017 06:27:12 GMT):
如果要额外附加一个分布式FS来做存储，考虑到存储链外的可变性，那链上数据也不可信了啊
CarlXK (Mon, 13 Mar 2017 06:33:30 GMT):
所以fabric对couchdb的调用是封装了还是透传？
coldplay1987 (Mon, 13 Mar 2017 06:33:34 GMT):
Has joined the channel.
JasonD (Mon, 13 Mar 2017 06:39:14 GMT):
Has joined the channel.
zhangchao (Mon, 13 Mar 2017 06:39:52 GMT):
放一个hash在链上就够l
zhangchao (Mon, 13 Mar 2017 06:40:06 GMT):
没必要整个数据都放在链上
CarlXK (Mon, 13 Mar 2017 06:42:48 GMT):
放hash和链接也可以，那就要保证外部数据不会丢不会挂
zhangchao (Mon, 13 Mar 2017 06:43:39 GMT):
必须得放HASH啊，链接不能保证数据完整
CarlXK (Mon, 13 Mar 2017 06:44:26 GMT):
链接+文件的hash值
CarlXK (Mon, 13 Mar 2017 06:44:51 GMT):
肯定要有hash，要不被改了咋办
CarlXK (Mon, 13 Mar 2017 07:07:20 GMT):
存储了权限这个又要做控制……
CarlXK (Mon, 13 Mar 2017 07:31:21 GMT):
链外存储有什么 分布式 存储 带权限的方案？
CarlXK (Mon, 13 Mar 2017 09:58:16 GMT):
peer可以取到加入到的channel下其他方的信息和公钥嘛？ @baohua @Ying @zhangchao
Ying (Mon, 13 Mar 2017 10:00:29 GMT):
没这接口吧？@CarlXk
CarlXK (Mon, 13 Mar 2017 10:01:54 GMT):
java中 我是没看到这个接口
CarlXK (Mon, 13 Mar 2017 10:02:25 GMT):
看起来nodejs中也没提供啊
xixuejia (Mon, 13 Mar 2017 10:44:33 GMT):
@CarlXK channel创始块里有
xixuejia (Mon, 13 Mar 2017 10:44:33 GMT):
@CarlXK channel创世块里有
CarlXK (Mon, 13 Mar 2017 10:44:58 GMT):
怎么取到呢，sdk里么提供
hydrachain (Mon, 13 Mar 2017 10:45:59 GMT):
实在不行，也可在应用中自己实现
xixuejia (Mon, 13 Mar 2017 10:46:13 GMT):
我不清楚SDK有没有提供接口..
CarlXK (Mon, 13 Mar 2017 10:46:39 GMT):
看了目前sdk没提供的，应用也没法实现啊
xixuejia (Mon, 13 Mar 2017 10:46:52 GMT):
实现应该不难，从最新的config block里读取所有的参与者
CarlXK (Mon, 13 Mar 2017 10:49:06 GMT):
好吧，再看看怎么搞，能实现就行
JasonD (Tue, 14 Mar 2017 02:44:42 GMT):
我在使用 0.6， 目前看到数据库是key-value结构的数据库，那比如我有个Item，然后item
JasonD (Tue, 14 Mar 2017 02:46:32 GMT):
item的transfer要记录下来，如果这些记录特别多呢，这样要怎么来设计？
JasonD (Tue, 14 Mar 2017 02:47:34 GMT):
而且比如有1w条，那怎么支持做分表呢？ 是否其实应该外部有个类似mysql，然后具体的表部分字段存放到fabric？
xixuejia (Tue, 14 Mar 2017 03:20:31 GMT):
@JasonD 是要做历史追溯吗？ 可以参考1.0的实现，使用KV数据库就可以实现
JasonD (Tue, 14 Mar 2017 03:22:18 GMT):
对的，就是追溯。可是KV数据库的话，那比如我有10w条，我要分页，比如查看 9000至9010的数据，那KV的效率岂不是很差
JasonD (Tue, 14 Mar 2017 03:22:33 GMT):
另外，你说的1.0的实现，具体是哪里？
xixuejia (Tue, 14 Mar 2017 03:23:37 GMT):
你可以自己设置分页
xixuejia (Tue, 14 Mar 2017 03:24:10 GMT):
core/ledger/kvledger/history/historydb/historyleveldb/historyleveldb.go
xixuejia (Tue, 14 Mar 2017 03:24:28 GMT):
在0.6可以在chaincode层面实现
JasonD (Tue, 14 Mar 2017 03:25:37 GMT):
好的，谢谢，我去翻翻
WeiHu (Tue, 14 Mar 2017 05:08:09 GMT):
Has joined the channel.
zhangchao (Tue, 14 Mar 2017 07:25:52 GMT):
上周末的HACKATHON有什么报道吗，好像在哪里都看不到，也没有人讨论
CarlXK (Tue, 14 Mar 2017 07:42:05 GMT):
couchdb可以自己操作嘛，能自己在上面建view还是通过cc的api可以建view？
yahtoo (Tue, 14 Mar 2017 12:43:26 GMT):
Has joined the channel.
hncslwx (Wed, 15 Mar 2017 01:25:01 GMT):
Has joined the channel.
baohua (Wed, 15 Mar 2017 01:43:19 GMT):
Dear all, today's meeting will begin at 10AM, thanks! https://wiki.hyperledger.org/groups/twgc/meeting/2017-03-15
baohua (Wed, 15 Mar 2017 01:43:28 GMT):
@here
baohua (Wed, 15 Mar 2017 01:43:58 GMT):
Phone Number: 800-820-0027 (toll free) and 400-821-0751 (caller paid). Passcode: 71173794
hncslwx (Wed, 15 Mar 2017 01:46:51 GMT):
Ok
Xie.YZ (Wed, 15 Mar 2017 08:13:02 GMT):
Has joined the channel.
ray (Wed, 15 Mar 2017 08:38:45 GMT):
@Kewei_Sun I can't see any project like `hyperledger-fabric-doc-cn` in my zanata.org dashboard. I can't find any via the search bar too. Any idea about it? Could any other guy see the project?
stevenkcolin (Wed, 15 Mar 2017 08:47:02 GMT):
@Kewei_Sun I also did not see any projects, please refer to the screenshot as below
stevenkcolin (Wed, 15 Mar 2017 08:47:29 GMT):
Message Attachments
camelbeck (Wed, 15 Mar 2017 11:04:01 GMT):
Has joined the channel.
Lin-YiTang (Wed, 15 Mar 2017 16:16:17 GMT):
Has joined the channel.
anthonymo (Thu, 16 Mar 2017 09:07:48 GMT):
Has joined the channel.
apspeical (Thu, 16 Mar 2017 16:32:19 GMT):
Has joined the channel.
jimthematrix (Thu, 16 Mar 2017 23:17:24 GMT):
@CarlXK _*peer可以取到加入到的channel下其他方的信息和公钥嘛？*_: Chain.js -> getChannelConfig()
CarlXK (Fri, 17 Mar 2017 01:56:23 GMT):
@jimthematrix 好的，谢谢！
marc_pango (Fri, 17 Mar 2017 03:15:13 GMT):
Has joined the channel.
luodanwg (Fri, 17 Mar 2017 09:29:53 GMT):
Has joined the channel.
dannysun85 (Sun, 19 Mar 2017 00:51:46 GMT):
Has joined the channel.
dannysun85 (Sun, 19 Mar 2017 00:55:03 GMT):
问一个问题
dannysun85 (Sun, 19 Mar 2017 00:59:49 GMT):
Message Attachments
dannysun85 (Sun, 19 Mar 2017 00:59:55 GMT):
make configtxgen的时候提示这个错误
dannysun85 (Sun, 19 Mar 2017 01:22:37 GMT):
mac系统里面怎么装libtool工具啊
xixuejia (Sun, 19 Mar 2017 02:28:24 GMT):
try `brew install libtool`
dannysun85 (Sun, 19 Mar 2017 02:45:00 GMT):
谢谢 现在出现新问题了
dannysun85 (Sun, 19 Mar 2017 02:45:21 GMT):
Message Attachments
dannysun85 (Sun, 19 Mar 2017 02:45:38 GMT):
最后报了这个错误
dannysun85 (Sun, 19 Mar 2017 02:45:44 GMT):
是缺少什么吗?
dannysun85 (Sun, 19 Mar 2017 02:46:26 GMT):
docker images 显示如下
dannysun85 (Sun, 19 Mar 2017 02:46:41 GMT):
Message Attachments
xixuejia (Sun, 19 Mar 2017 03:05:14 GMT):
是否安装了`pip install behave`?
dannysun85 (Sun, 19 Mar 2017 03:35:29 GMT):
在 mac上吗?
dannysun85 (Sun, 19 Mar 2017 03:36:36 GMT):
这个还真没有 我试一下
dannysun85 (Sun, 19 Mar 2017 03:45:32 GMT):
可以了 谢谢兄弟
dannysun85 (Sun, 19 Mar 2017 03:59:51 GMT):
兄弟貌似还是不行, 运行到这里还是报错
dannysun85 (Sun, 19 Mar 2017 03:59:58 GMT):
Message Attachments
dannysun85 (Sun, 19 Mar 2017 04:00:11 GMT):
还是behave的问题
dannysun85 (Sun, 19 Mar 2017 09:02:47 GMT):
brew install protobuf 完了以后在运行 还是报错啊
amath0312 (Mon, 20 Mar 2017 03:48:46 GMT):
Has joined the channel.
ZengLingYou (Mon, 20 Mar 2017 06:16:00 GMT):
I try setup the env, vagrant on win10, but I got a error, who can help me check it, thanks.
ZengLingYou (Mon, 20 Mar 2017 06:16:39 GMT):
Building docker ccenv-image
docker build -t hyperledger/fabric-ccenv build/image/ccenv
Got permission denied while trying to connect to the Docker daemon socket at unix:///var/run/docker.sock: Post http://%2Fvar%2Frun%2Fdocker.sock/v1.25/build?buildargs=%7B%7D&cachefrom=%5B%5D&cgroupparent=&cpuperiod=0&cpuquota=0&cpusetcpus=&cpusetmems=&cpushares=0&dockerfile=Dockerfile&labels=%7B%7D&memory=0&memswap=0&networkmode=default&rm=1&shmsize=0&t=hyperledger%2Ffabric-ccenv&ulimits=null: dial unix /var/run/docker.sock: connect: permission denied
Makefile:226: recipe for target 'build/image/ccenv/.dummy-x86_64-0.7.0-snapshot-7c1934a' failed
make: *** [build/image/ccenv/.dummy-x86_64-0.7.0-snapshot-7c1934a] Error 1
Xiao (Mon, 20 Mar 2017 07:11:02 GMT):
Has joined the channel.
amath0312 (Mon, 20 Mar 2017 07:59:26 GMT):
try sodu
kuangchao (Mon, 20 Mar 2017 08:02:52 GMT):
I have a Facebook Fabirc forum on Facebook, welcome to join
https://www.facebook.com/groups/876837335752599
zlliu (Mon, 20 Mar 2017 12:14:51 GMT):
@baohua https://github.com/hyperledger/blockchain-explorer 区块链浏览器项目怎么没动静了 :sweat_smile:
baohua (Mon, 20 Mar 2017 12:23:41 GMT):
pls contact those maintainers....
moxm (Tue, 21 Mar 2017 02:22:36 GMT):
Has joined the channel.
moxm (Tue, 21 Mar 2017 02:22:52 GMT):
1.0 alpha 有人集成了ca吗
ZengLingYou (Tue, 21 Mar 2017 05:19:52 GMT):
开发环境到底哪里错了，看不出来的。强制给vagrant账号root权限，往下编译继续报错的。
ZengLingYou (Tue, 21 Mar 2017 05:20:07 GMT):
Get https://registry-1.docker.io/v2/: net/http: TLS handshake timeout
Makefile:226: recipe for target 'build/image/ccenv/.dummy-x86_64-0.7.0-snapshot-7c1934a' failed
make: *** [build/image/ccenv/.dummy-x86_64-0.7.0-snapshot-7c1934a] Error 1
ZengLingYou (Tue, 21 Mar 2017 07:35:58 GMT):
好吧，这个好像是墙的原因。
amath0312 (Tue, 21 Mar 2017 09:49:57 GMT):
有谁遇到过：Chaincode handler FSM cannot handle message (INIT) with payload size (22) while in state: established 这个问题。。
amath0312 (Tue, 21 Mar 2017 09:50:04 GMT):
peer2 | 2017-03-21 09:48:33.490 UTC [chaincode] beforeInitState -> DEBU 279 Before state established.. notifying waiter that we are up
peer2 | 2017-03-21 09:48:33.490 UTC [chaincode] notifyDuringStartup -> DEBU 27a Notifying during startup
peer2 | 2017-03-21 09:48:33.490 UTC [chaincode] enterInitState -> DEBU 27b [|�
peer2 | �]Entered state init
peer2 | 2017-03-21 09:48:33.490 UTC [chaincode] processStream -> DEBU 27c [|�
peer2 | �]Received message ERROR from shim
peer2 | 2017-03-21 09:48:33.490 UTC [chaincode] processStream -> ERRO 27d Got error: [|�
peer2 | ��7�x�]Chaincode handler FSM cannot handle message (INIT) with payload size (22) while in state: established
peer2 | 2017-03-21 09:48:33.490 UTC [chaincode] HandleMessage -> DEBU 27e [|�
peer2 | �]Handling ChaincodeMessage of type: ERROR in state init
peer2 | 2017-03-21 09:48:33.490 UTC [chaincode] enterEndState -> DEBU 27f [|�
peer2 | �]Entered state end
peer2 | 2017-03-21 09:48:33.490 UTC [chaincode] notify -> DEBU 280 notifying Txid:|�
peer2 | ��7�x�
peer2 | 2017-03-21 09:48:33.490 UTC [chaincode] deregisterHandler -> DEBU 281 Deregister handler: cc_asset_management:0/myc1
peer2 | 2017-03-21 09:48:33.490 UTC [chaincode] deregisterHandler -> DEBU 282 Deregistered handler with key: cc_asset_management:0/myc1
peer2 | 2017-03-21 09:48:33.490 UTC [chaincode] processStream -> DEBU 283 Received EOF, ending chaincode support stream, EOF
peer2 | 2017-03-21 09:48:33.490 UTC [chaincode] deregisterHandler -> DEBU 284 Deregister handler: cc_asset_management:0/myc1
peer2 | 2017-03-21 09:48:33.490 UTC [chaincode] Launch -> ERRO 285 sending init failed(Error initializing container cc_asset_management:0/myc1: [|�
peer2 | ��7�x�]Chaincode handler FSM cannot handle message (INIT) with payload size (22) while in state: established)
peer2 | 2017-03-21 09:48:33.490 UTC [container] lockContainer -> DEBU 286 waiting for container(peer0-peer2-cc_asset_management-0-c659a47dce16ded8af86b9f91dfc411edac0416e43dff2ced2faac39f7633bbbde2fcc9a65a5d07adaeca3513c970f7b8b9f4125848bea488e5e1cfc85db5ac0) lock
peer2 | 2017-03-21 09:48:33.490 UTC [container] lockContainer -> DEBU 287 got container (peer0-peer2-cc_asset_management-0-c659a47dce16ded8af86b9f91dfc411edac0416e43dff2ced2faac39f7633bbbde2fcc9a65a5d07adaeca3513c970f7b8b9f4125848bea488e5e1cfc85db5ac0) lock
peer2 | 2017-03-21 09:48:33.939 UTC [dockercontroller] stopInternal -> DEBU 288 Stopped container peer0-peer2-cc_asset_management-0-c659a47dce16ded8af86b9f91dfc411edac0416e43dff2ced2faac39f7633bbbde2fcc9a65a5d07adaeca3513c970f7b8b9f4125848bea488e5e1cfc85db5ac0
peer2 | 2017-03-21 09:48:33.939 UTC [dockercontroller] stopInternal -> DEBU 289 Kill container peer0-peer2-cc_asset_management-0-c659a47dce16ded8af86b9f91dfc411edac0416e43dff2ced2faac39f7633bbbde2fcc9a65a5d07adaeca3513c970f7b8b9f4125848bea488e5e1cfc85db5ac0 (API error (500): {"message":"Cannot kill container peer0-peer2-cc_asset_management-0-c659a47dce16ded8af86b9f91dfc411edac0416e43dff2ced2faac39f7633bbbde2fcc9a65a5d07adaeca3513c970f7b8b9f4125848bea488e5e1cfc85db5ac0: Container 9c00f19eea0eeb6f565a5b9c60dad53fe3e5bc498cde7c799f66e5e358eb3425 is not running"}
peer2 | )
peer2 | 2017-03-21 09:48:34.035 UTC [dockercontroller] stopInternal -> DEBU 28a Removed container peer0-peer2-cc_asset_management-0-c659a47dce16ded8af86b9f91dfc411edac0416e43dff2ced2faac39f7633bbbde2fcc9a65a5d07adaeca3513c970f7b8b9f4125848bea488e5e1cfc85db5ac0
peer2 | 2017-03-21 09:48:34.035 UTC [container] unlockContainer -> DEBU 28b container lock deleted(peer0-peer2-cc_asset_management-0-c659a47dce16ded8af86b9f91dfc411edac0416e43dff2ced2faac39f7633bbbde2fcc9a65a5d07adaeca3513c970f7b8b9f4125848bea488e5e1cfc85db5ac0)
peer2 | 2017-03-21 09:48:34.035 UTC [chaincode] Launch -> DEBU 28c sending init completed
peer2 | 2017-03-21 09:48:34.035 UTC [chaincode] Launch -> DEBU 28d LaunchChaincode complete
peer2 | 2017-03-21 09:48:34.035 UTC [lockbasedtxmgr] Done -> DEBU 28e Done query executer/ tx simulator [7fba8cce-54af-4625-8a5f-24d0e6902c10]
apspeical (Tue, 21 Mar 2017 10:48:07 GMT):
有谁遇到过这个问题：在peer 部署时，用 #peer chaincode deploy -u jim -p github.com/hyperledger/fabric/examples/chaincode/go/chaincode_example02 -c '{"Function":"init", "Args": ["a","100", "b", "200"]}' 进行， 正确结果应该返回chaincode ID， 实际返回为空。 查询docker 的 log得到如下错误信息：
apspeical (Tue, 21 Mar 2017 10:48:29 GMT):
10:45:36.423 [chaincode] sendInitOrReady -> DEBU 4e36 handler not found for chaincode
vp0_1 | 10:45:36.423 [chaincode] Launch -> ERRO 4e37 sending init failed(handler not found for chaincode )
vp0_1 | 10:45:36.423 [chaincode] Launch -> ERRO 4e38 stop failed chaincode name not set(Failed to init chaincode(handler not found for chaincode ))
Lin-YiTang (Tue, 21 Mar 2017 17:37:46 GMT):
使用 node sdk
是否一定要搭配 ca ?
及設定 msp , tls ?
jimthematrix (Tue, 21 Mar 2017 23:24:27 GMT):
@Lin-YiTang node sdk 支持标准CA，不用必须是fabric－ca，只要把已经生成的密钥和经过CA签名的证书分别导入到User就可以了，具体操作可以参照test/unit/util.js：
``` // first load the private key and save in the BCCSP's key store
var privKeyPEM = path.join(__dirname, '../fixtures/msp/local/keystore/admin.pem');
var pemData, member;
return readFile(privKeyPEM)
.then((data) => {
pemData = data;
// default crypto suite uses $HOME/.hfc-key-store as key store
var kspath = CryptoSuite.getDefaultKeyStorePath();
var testKey;
return new KeyStore({
path: kspath
});
}).then((store) => {
var rawKey = KEYUTIL.getKey(pemData.toString());
testKey = new ecdsaKey(rawKey);
return store.putKey(testKey);
}).then((value) => {
// next save the certificate in a serialized user enrollment in the state store
var certPEM = path.join(__dirname, '../fixtures/msp/local/signcerts/admin.pem');
return readFile(certPEM);
}).then((data) => {
member = new User(username, client);
return member.setEnrollment(testKey, data.toString(), ORGS[userOrg].mspid);
}).then(() => {
return client.setUserContext(member);
}).then((user) => {
return resolve(user);
}).catch((err) => {
reject(new Error('Failed to load key or certificate and save to local stores. ' + err));
t.end();
});
```
jimthematrix (Tue, 21 Mar 2017 23:24:27 GMT):
@Lin-YiTang node sdk 支持标准CA，不用必须是fabric－ca，只要把已经生成的密钥和经过CA签名的证书分别导入到User就可以了，具体操作可以参照test/unit/util.js：
```// first load the private key and save in the BCCSP's key store
var privKeyPEM = path.join(__dirname, '../fixtures/msp/local/keystore/admin.pem');
var pemData, member;
return readFile(privKeyPEM)
.then((data) => {
pemData = data;
// default crypto suite uses $HOME/.hfc-key-store as key store
var kspath = CryptoSuite.getDefaultKeyStorePath();
var testKey;
return new KeyStore({
path: kspath
});
}).then((store) => {
var rawKey = KEYUTIL.getKey(pemData.toString());
testKey = new ecdsaKey(rawKey);
return store.putKey(testKey);
}).then((value) => {
// next save the certificate in a serialized user enrollment in the state store
var certPEM = path.join(__dirname, '../fixtures/msp/local/signcerts/admin.pem');
return readFile(certPEM);
}).then((data) => {
member = new User(username, client);
return member.setEnrollment(testKey, data.toString(), ORGS[userOrg].mspid);
}).then(() => {
return client.setUserContext(member);
}).then((user) => {
return resolve(user);
}).catch((err) => {
reject(new Error('Failed to load key or certificate and save to local stores. ' + err));
t.end();
});
```
sandroku63 (Wed, 22 Mar 2017 01:32:45 GMT):
Has joined the channel.
ZengLingYou (Wed, 22 Mar 2017 06:36:10 GMT):
打算用CLI本地测试下Fabric chaincode, 输入
peer chaincode deploy -n mycc -c '{"Args": ["init", "a","100", "b", "200"]}'
提示说chaincode不支持deploy这个命令，
谁遇到过，怎么解决的
ZengLingYou (Wed, 22 Mar 2017 07:36:23 GMT):
root@ubuntu:/opt/gopath/src/github.com/hyperledger/fabric# ./build/bin/peer cha
incode install -v 1.0 -n zlycc -p github.com/hyperledger/fabric/examples/chainc
ode/go/chaincode_example02 -c '{"Args": ["init","a","100","b","200"]}'
Error: Error getting broadcast client: Error connecting to 0.0.0.0:7050 due to grpc: timed out when dialing
Usage:
peer chaincode install [flags]
Global Flags:
-C, --chainID string The chain on which this command should be executed (default "testchainid")
-c, --ctor string Constructor message for the chaincode in JSON format (default "{}")
-E, --escc string The name of the endorsement system chaincode to be used for this chaincode
-l, --lang string Language the chaincode is written in (default "golang")
--logging-level string Default logging level and overrides, see core.yaml for full syntax
-n, --name string Name of the chaincode
-p, --path string Path to chaincode
-P, --policy string The endorsement policy associated to this chaincode
--test.coverprofile string Done (default "coverage.cov")
-t, --tid string Name of a custom ID generation algorithm (hashing and decoding) e.g. sha256base64
-u, --username string Username for chaincode operations when security is enabled
-v, --version string Version of the chaincode specified in install/instantiate/upgrade commands
-V, --vscc string The name of the verification system chaincode to be used for this chaincode
Shadow-Hawk (Thu, 23 Mar 2017 01:02:58 GMT):
Has joined the channel.
CarlXK (Thu, 23 Mar 2017 01:57:21 GMT):
有谁遇到过这个问题么，用 MAC跑 nodesdk 测试的时候 报not a server admin
➜ fabric-sdk-node git:(master) node test/integration/couchdb-fabricca-tests.js
info: Returning a new winston logger with default configurations
info: [couchdb-fabricca]: couchdb Key Value Store = fabric-client/lib/impl/CouchDBKeyValueStore.js
info: [couchdb-fabricca]: couch keyValStorePath: http://localhost:5984
TAP version 13
# Use FabricCAServices with a CouchDB KeyValueStore
# Cleanup of existing member_db returned false
# Initilize the CouchDB KeyValueStore
'info: [CouchDBKeyValueStore.js]: No member_db found, creating member_db
error: [couchdb-fabricca]: Error: Failed to create member_db database due to error: Error: You are not a server admin.'
at Request._callback (/Users/CL/Project/hyperledger/fabric-sdk-node/node_modules/nano/lib/nano.js:248:15)
at Request.self.callback (/Users/CL/Project/hyperledger/fabric-sdk-node/node_modules/request/request.js:186:22)
at emitTwo (events.js:106:13)
at Request.emit (events.js:191:7)
at Request.
xujiaming (Thu, 23 Mar 2017 06:52:16 GMT):
Has joined the channel.
jackyqiu (Sat, 25 Mar 2017 02:12:58 GMT):
Has joined the channel.
jackyqiu (Sat, 25 Mar 2017 02:16:45 GMT):
今天打算测试一下
jackyqiu (Sat, 25 Mar 2017 02:16:45 GMT):
今天打算按照https://www.youtube.com/watch?v=SXTAVFM2liU&t=109s在CLI下测试一下instantiate chaincode, 2个peers可以跑起来
jackyqiu (Sat, 25 Mar 2017 02:16:45 GMT):
今天打算按照https://www.youtube.com/watch?v=SXTAVFM2liU&t=109s在CLI下测试一下instantiate chaincode, 2个peers可以跑起来，可是在第二个窗口CLI环境下执行peer channel create -c myc的时候报错：Error: unknown command "channel" for "peer"，我是在GITHUB上pull的最新版本，难道不是1.0的吗？
jackyqiu (Sat, 25 Mar 2017 03:56:09 GMT):
找到原因了
jackyqiu (Sat, 25 Mar 2017 03:56:09 GMT):
找到原因了，重新build了以后就好了
jackyqiu (Sat, 25 Mar 2017 03:56:09 GMT):
找到原因了，重新build docker images了以后就好了
jackyqiu (Sat, 25 Mar 2017 03:56:45 GMT):
不过又出来新的错误 Ordering service endpoint is not valid or missing
jackyqiu (Sat, 25 Mar 2017 15:24:59 GMT):
解决了，要在命令后面加上-o orderer:5005
baohua (Tue, 28 Mar 2017 01:13:50 GMT):
Dear all, we will have meeting this Wendesday morning at 10 AM, pls help update the agenda and the attendee list, thanks! https://wiki.hyperledger.org/groups/twgc/meeting/2017-03-29
baohua (Tue, 28 Mar 2017 01:13:50 GMT):
Dear all, we will have meeting this Wednesday morning at 10 AM, pls help update the agenda and the attendee list, thanks! https://wiki.hyperledger.org/groups/twgc/meeting/2017-03-29
shibo.lin (Tue, 28 Mar 2017 01:32:58 GMT):
what does twg stand for ?
baohua (Tue, 28 Mar 2017 01:34:54 GMT):
Technical Working Group
shibo.lin (Tue, 28 Mar 2017 01:54:30 GMT):
is the meeting tomorrow a internet meeting ?
baohua (Tue, 28 Mar 2017 01:58:47 GMT):
no, it's call meeting. see the link for access info.
shibo.lin (Tue, 28 Mar 2017 08:58:35 GMT):
Thanks for your quick answer. I will join you tomorrow morning.
hydrachain (Tue, 28 Mar 2017 10:12:34 GMT):
建议设置出错问题专区
baohua (Tue, 28 Mar 2017 12:10:17 GMT):
旧金山- 2017年3月22日 - Hyperledger超级账本，跨行业协作推进区块链技术，今天宣布，SAP SE (纽交所: SAP) 加入并成为高级会员。SAP创新中心网络创新工程副总裁Dominik Heere先生，将作为SAP高级会员的代表，代表公司进入Hyperledger超级账本董事会。
jimthematrix (Tue, 28 Mar 2017 16:57:22 GMT):
@baohua where would you say the python sdk is? i know it's been worked on actively, would you feel comfortable declaring it to be part of the v1.0 release? there's no definitive time frame on when v1.0 is going "GA" yet, but there's talk about a beta next month, would love to see python sdk to be part of that, along with Java SDK (only node sdk was part of the fabric v1.0 alpha)
liqilei (Wed, 29 Mar 2017 01:32:41 GMT):
Has joined the channel.
zhangchao (Wed, 29 Mar 2017 01:46:53 GMT):
在fabric channel问的问题，没人回答，还是放在这里问吧
zhangchao (Wed, 29 Mar 2017 01:47:38 GMT):
peer chaincode deploy现在为啥没了，变成了install和instantiate，有啥原因吗
baohua (Wed, 29 Mar 2017 01:48:05 GMT):
@jimthematrix definitely, jim, we wanna follow that release plan. The current plan is to release the alpha first to support MVP, and next month for the beta, too. Thanks!
baohua (Wed, 29 Mar 2017 01:48:53 GMT):
@zhangchao yeap 解耦为安装和启动 不需要都得启动
jimthematrix (Wed, 29 Mar 2017 01:58:57 GMT):
@zhangchao https://jira.hyperledger.org/browse/FAB-1783 (why install and instantiate)
jimthematrix (Wed, 29 Mar 2017 02:01:02 GMT):
@baohua great to hear! do you have a JIRA board that lists remaining work for alpha/beta/GA?
zhangchao (Wed, 29 Mar 2017 02:03:15 GMT):
thanks @jimthematrix @baohua , I will take a look
zerppen (Wed, 29 Mar 2017 02:47:12 GMT):
@baohua 徐正平
yeeyaa (Wed, 29 Mar 2017 11:54:44 GMT):
Has joined the channel.
ccen (Wed, 29 Mar 2017 21:11:07 GMT):
Has joined the channel.
zhangchao (Thu, 30 Mar 2017 05:40:25 GMT):
还是来这里问吧
zhangchao (Thu, 30 Mar 2017 05:40:40 GMT):
I tried to execute java example chaincode github.com/hexamples/chaincode/java/SimpleSample, but failed with the following message:
vagrant@hyperledger-devenv:v0.3.0-3181e78:/opt/gopath/src/github.com/hyperledger/fabric$ peer chaincode instantiate -o 127.0.0.1:7050 -C mychannel -l java -n myccjava -v 1.0 -p github.com/hexamples/chaincode/java/SimpleSample -c '{"Args":["init","a", "100", "b","200"]}'
2017-03-29 09:00:47.730 UTC [chaincodeCmd] checkChaincodeCmdParams -> INFO 001 Using default escc
2017-03-29 09:00:47.730 UTC [chaincodeCmd] checkChaincodeCmdParams -> INFO 002 Using default vscc
Error: Error endorsing chaincode: rpc error: code = 2 desc = Failed to init chaincode(handler not found for chaincode myccjava:1.0)
but I can execute go chaincode successfully, can anyone give some advise on java chaincode execution?
zhangchao (Thu, 30 Mar 2017 05:41:01 GMT):
跑通java的，这个错误谁能给个提示啊
zhangmenghang (Thu, 30 Mar 2017 05:51:58 GMT):
Has joined the channel.
zhangmenghang (Thu, 30 Mar 2017 05:53:56 GMT):
大家好，我最近在用fabric 1.0 alpha版本，在以前的所有环境运行都是完全没问题的，但是最近在新买的阿里云上运行时，peer和peer之间的通讯老是报错：
zhangmenghang (Thu, 30 Mar 2017 05:54:10 GMT):
peer1 | 2017-03-30 03:20:12.223 UTC [gossip/comm#-1] createConnection -> DEBU 160 Entering peer0:7051 []
peer1 | fatal error: unexpected signal during runtime execution
peer1 | [signal SIGSEGV: segmentation violation code=0x1 addr=0x63 pc=0x7f4a117d3259]
peer1 |
peer1 | runtime stack:
peer1 | runtime.throw(0xd2bd11, 0x2a)
peer1 | /opt/go/src/runtime/panic.go:566 +0x95
peer1 | runtime.sigpanic()
peer1 | /opt/go/src/runtime/sigpanic_unix.go:12 +0x2cc
peer1 |
peer1 | goroutine 125 [syscall, locked to thread]:
peer1 | runtime.cgocall(0xa98c50, 0xc420040df8, 0xc400000000)
peer1 | /opt/go/src/runtime/cgocall.go:131 +0x110 fp=0xc420040db0 sp=0xc420040d70
peer1 | net._C2func_getaddrinfo(0x7f4a080008c0, 0x0, 0xc421411cb0, 0xc4200243d0, 0x0, 0x0, 0x0)
peer1 | ??:0 +0x68 fp=0xc420040df8 sp=0xc420040db0
peer1 | net.cgoLookupIPCNAME(0xc42001407b, 0x5, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0)
peer1 | /opt/go/src/net/cgo_unix.go:146 +0x37c fp=0xc420040f18 sp=0xc420040df8
peer1 | net.cgoIPLookup(0xc4213f7b00, 0xc42001407b, 0x5)
peer1 | /opt/go/src/net/cgo_unix.go:198 +0x4d fp=0xc420040fa8 sp=0xc420040f18
peer1 | runtime.goexit()
peer1 | /opt/go/src/runtime/asm_amd64.s:2086 +0x1 fp=0xc420040fb0 sp=0xc420040fa8
peer1 | created by net.cgoLookupIP
peer1 | /opt/go/src/net/cgo_unix.go:208 +0xb4
zhangmenghang (Thu, 30 Mar 2017 05:54:36 GMT):
有人遇到过类似问题吧，感觉适合阿里云环境有关，跑完全一样的流程阿里云就不行
zhangmenghang (Thu, 30 Mar 2017 05:55:42 GMT):
@baohua
baohua (Thu, 30 Mar 2017 05:58:39 GMT):
你都说了是阿里云的问题了 :wink: 国内可以试试腾讯云：https://github.com/yeasy/docker_practice/blob/master/cloud/qcloud.md
zhangmenghang (Thu, 30 Mar 2017 06:09:14 GMT):
换不起了。。刚买的阿里云:sob:
zhangchao (Thu, 30 Mar 2017 06:35:16 GMT):
@baohua 我发的问题给看看呗
baohua (Thu, 30 Mar 2017 06:36:32 GMT):
java sdk 最近在 fix 几个问题 还没有完成
zhangchao (Thu, 30 Mar 2017 06:39:37 GMT):
我这个不是sdk的问题吧，我也没用java sdk
baohua (Thu, 30 Mar 2017 06:42:05 GMT):
哦 说错了 java 的 cc
zhangchao (Thu, 30 Mar 2017 06:46:16 GMT):
哦，我这个问题是cc的bug吗，如果是的话，我就等等patch了
baohua (Fri, 31 Mar 2017 02:58:58 GMT):
https://github.com/ryanhanwu/How-To-Ask-Questions-The-Smart-Way/blob/master/README-zh_CN.md
jackyqiu (Fri, 31 Mar 2017 03:29:19 GMT):
Hi, 我现在尝试照着install_instantiate.rst文件里的步骤部署两个peer，然后发布chaincode 到这两个点上，可是每次我执行join channel命令：CORE_PEER_ADDRESS=peer0:7051 peer channel join -b myc.block -o orderer:5005 的时候，在peer运行端总会显示错误：peer0 | 2017-03-31 03:15:51.030 UTC [deliveryClient] NewDeliverService -> ERRO 030 Cannot dial to 127.0.0.1:7050, because of grpc: timed out when dialing
我在docker-2peer.yml文件里配置的orderer端口是5005，请问5005和7050这两个orderer端口的作用分别是什么？另外如何解决这个错误？我的环境是win10 + vagrant +docker,代码是从Github上clone最新的。多谢了！
shibo.lin (Fri, 31 Mar 2017 04:14:40 GMT):
@jackyqiu I got the same error.
JayXie (Fri, 31 Mar 2017 04:22:23 GMT):
Has joined the channel.
ylsGit (Fri, 31 Mar 2017 04:23:08 GMT):
Has joined the channel.
ZengLingYou (Fri, 31 Mar 2017 06:40:08 GMT):
CORE_PEER_ADDRESS=peer0:7051 CORE_PEER_COMMITTER_LEDGER_ORDERER=orderer:7050 peer chaincode deploy -C myc1 -n mycc -p /usr/local/gopath/src/github.com/hyperledger/fabric/examples/chaincode/go/chaincode_example02/chaincode_example02 -c '{"Args":["init","a","100","b","200"]}'
Error: Error getting chaincode code chaincode: Path to chaincode does not exist: github.com/hyperledger/fabric/examples/chaincode/go/chaincode_example02
ZengLingYou (Fri, 31 Mar 2017 06:40:53 GMT):
What's wrong, how ?
zhangchao (Fri, 31 Mar 2017 08:39:22 GMT):
@ZengLingYou -p 后面不是绝对路径
ZengLingYou (Fri, 31 Mar 2017 08:41:37 GMT):
嗯，这个已经改过来了。
shibo.lin (Fri, 31 Mar 2017 11:21:38 GMT):
@jackyqiu I followed the below instruction. now can join to the specified channel.
https://hyperledger-fabric.readthedocs.io/en/latest/getting_started.html
luomin (Fri, 31 Mar 2017 13:43:51 GMT):
Has joined the channel.
yong (Sat, 01 Apr 2017 02:06:51 GMT):
root@fu-yong:/opt/gopath/src/github.com/hyperledger/fabric-sdk-node# gulp test[10:02:30] Using gulpfile /opt/gopath/src/github.com/hyperledger/fabric-sdk-node/gulpfile.js
[10:02:30] Starting 'lint'...
[10:02:30] Starting 'pre-test'...
[10:02:32] Finished 'pre-test' after 2.23 s
[10:02:33] Finished 'lint' after 2.85 s
[10:02:33] Starting 'test'...
info: Returning a new winston logger with default configurations
events.js:160
throw er; // Unhandled 'error' event
^
Error: Cannot find module 'fabric-ca-client/lib/FabricCAClientImpl.js'
at Function.Module._resolveFilename (module.js:469:15)
at Function.Module._load (module.js:417:25)
at Module.require (module.js:497:17)
at require (internal/module.js:20:19)
at Object.
baohua (Sat, 01 Apr 2017 04:34:49 GMT):
@yong suggest ask in the fabric-sdk-node channel.
baohua (Sat, 01 Apr 2017 04:34:50 GMT):
Dear all
Welcome Wenjie Xie from WuTongShu to join the volunteers of TWG China! As the CTO, he will lead WuTongShu to help contribute on the documentation i18n, and java chaincode and sdk.
欢迎来自梧桐树的谢文杰加入中国技术工作组志愿者队伍，他目前担任梧桐树团队的 CTO 职务，将带领团队在文档国际化和 java 链码、sdk 开发等方面做出贡献。
https://wiki.hyperledger.org/groups/tsc/technical-working-group-china
JasonD (Sat, 01 Apr 2017 04:41:21 GMT):
turns out v1.0.0 is not v1.0...
kuangchao (Sat, 01 Apr 2017 04:54:20 GMT):
目前fabric-sdk-py是不是不支持Fabric v1.0
jackyqiu (Sun, 02 Apr 2017 15:04:31 GMT):
[ ](https://chat.hyperledger.org/channel/twg-china?msg=pJrC9ookektbFo8LR) @shibo.lin what's your environment? I am using win10+vagrant, but has the following issue：
"Error: Error endorsing chaincode: rpc error: code = 2 desc = Illegal file mode detected for file src/github.com/hyperledger/fabric/examples/chaincode/go/chaincode_example02/chaincode_example02.go: 100777" when running "peer chaincode install" command in windows + vagrant environment? I tried chmod 0666 for the file chaincode_example02.go, but file permission will not be changed. Did some research and noticed that in Vagrant cannot change mount folder / file permission. I tried to update vagrantfile mount permission to be:
config.vm.synced_folder "..", "/opt/gopath/src/github.com/hyperledger/fabric", :mount_options => ["dmode=777","fmode=666"]
but it will have issue on execute command file.
jackyqiu (Sun, 02 Apr 2017 16:40:18 GMT):
@shibo.lin never mind, I fixed it
zerppen (Wed, 05 Apr 2017 05:45:28 GMT):
请问一下，是不是iroha主要是做资产管理用的
zerppen (Wed, 05 Apr 2017 05:50:13 GMT):
或者说，它的主要应用场景有哪些
Donald Liu (Wed, 05 Apr 2017 08:59:17 GMT):
应该没有特定场景。
https://www.hyperledger.org/community/projects
可以跟Fabric和Sawtooth Lake一起看。
Donald Liu (Wed, 05 Apr 2017 09:01:34 GMT):
在@iroha也看到：
Iroha is good for managing digital assets and things like identity.
New news out: http://www.coindesk.com/panasonic-hyperledger-iroha-blockchain
zerppen (Wed, 05 Apr 2017 09:21:24 GMT):
嗯 我在国内还没看到具体应用场景
baohua (Mon, 10 Apr 2017 02:14:40 GMT):
@here Dear all, we will have meeting this Wednesday morning, pls help update the agenda before the meeting, thanks! https://wiki.hyperledger.org/groups/twgc/meeting/2017-04-12
ZengLingYou (Mon, 10 Apr 2017 09:22:13 GMT):
While I make peer (v1.0 source code), a error here, who can help check it, thanks.
Step 14/15 : RUN core/chaincode/shim/java/javabuild.sh
---> Running in 8e7e050ec5f2
/root/core/chaincode/shim/java/src/main/java/org/hyperledger/java/shim/ChaincodeBase.java:29: error: cannot find symbol
import org.hyperledger.fabric.protos.peer.ChaincodeSupportGrpc;
^
symbol: class ChaincodeSupportGrpc
location: package org.hyperledger.fabric.protos.peer
/root/core/chaincode/shim/java/src/main/java/org/hyperledger/java/shim/ChaincodeBase.java:30: error: package org.hyperledger.fabric.protos.peer.ChaincodeSupportGrpc does not exist
import org.hyperledger.fabric.protos.peer.ChaincodeSupportGrpc.ChaincodeSupportStub;
^
/root/core/chaincode/shim/java/src/main/java/org/hyperledger/java/shim/ChaincodeBase.java:31: error: package org.hyperledger.fabric.protos.peer.ChaincodeShim does not exist
import org.hyperledger.fabric.protos.peer.ChaincodeShim.ChaincodeMessage;
baohua (Tue, 11 Apr 2017 02:29:25 GMT):
which's code commit?
baohua (Tue, 11 Apr 2017 02:29:25 GMT):
which code commit? latest is a076bbada80cbcda4825c62233f16290edb1d1b1
ZengLingYou (Tue, 11 Apr 2017 03:49:37 GMT):
commit cacb292921553900ea808344599b9914632bf1d3
ZengLingYou (Tue, 11 Apr 2017 03:49:58 GMT):
my env is centos 7
ZengLingYou (Tue, 11 Apr 2017 03:55:17 GMT):
two questions:
ZengLingYou (Tue, 11 Apr 2017 03:56:00 GMT):
a. not found the protos ChaincodeSupportGrpc in source code, which path
ZengLingYou (Tue, 11 Apr 2017 03:56:57 GMT):
b.why still report protos ChaincodeShim not exist
ZengLingYou (Tue, 11 Apr 2017 07:17:45 GMT):
about the second question, suppose already renamed the protos to chaincode_shim.protos, but the java code still import chaincodeshim?it is a issue, or I lost something?
ZengLingYou (Tue, 11 Apr 2017 07:36:57 GMT):
suppose I missed the gradle file, let me correct it and try again.
ZengLingYou (Tue, 11 Apr 2017 08:15:06 GMT):
It's ok now.
ylsGit (Wed, 12 Apr 2017 01:41:56 GMT):
既然是中国工作组，那就发中文呗
baohua (Wed, 12 Apr 2017 02:30:02 GMT):
中文支持！
zerppen (Wed, 12 Apr 2017 02:41:33 GMT):
请问一下 那些人在研究 fabric-sdk-java 的
zerppen (Wed, 12 Apr 2017 02:41:50 GMT):
我这边也有整理了一些资料 希望可以一起讨论讨论
leungjob (Wed, 12 Apr 2017 02:50:36 GMT):
Has joined the channel.
grapebaba (Wed, 12 Apr 2017 03:13:11 GMT):
没有专门研究，做python SDK有时会参考下
zerppen (Wed, 12 Apr 2017 03:44:30 GMT):
那现在只有node比较好了
zerppen (Wed, 12 Apr 2017 03:44:54 GMT):
java 有时参考node
baohua (Wed, 12 Apr 2017 03:51:12 GMT):
这个问题可以去 maillist 问问或搜索 记得有人问过好像
zerppen (Wed, 12 Apr 2017 03:54:57 GMT):
我之前电话上问过 我主要是想找个可以说中文的问问
zerppen (Wed, 12 Apr 2017 03:55:34 GMT):
刚刚电话会议问的
grapebaba (Wed, 12 Apr 2017 06:36:27 GMT):
具体什么问题
zerppen (Wed, 12 Apr 2017 06:54:03 GMT):
比较疑惑fabric-sdk-java-1.0-SNAPSHOT.jar里面的.class文件是怎么生成的。
zerppen (Wed, 12 Apr 2017 06:55:32 GMT):
我看这个包下面的.proto文件内容和.class文件并不对应
zerppen (Wed, 12 Apr 2017 06:58:17 GMT):
完善代码需要直接调用这个jar包里的方法
zhangchao (Wed, 12 Apr 2017 08:35:08 GMT):
请教一下，6月份北京的hackfest怎么参加，有介绍吗
yong (Wed, 12 Apr 2017 08:37:12 GMT):
请教一下大家，我想使用hyperledger模拟银行开户。首先使用fabric-ca中的fabric-ca-client register命令注册两个user类型的帐号，同时我使用openssl 生成了2对ecc公私钥对。我的问题是我怎么把这两对公私钥对和帐号绑定起来以便进行交易？
yp (Wed, 12 Apr 2017 09:55:59 GMT):
@yong 你如果使用了fabric-ca，就不需要再自己去生成公私钥对，register后，当你enroll的时候，ca server会帮你创建私钥和x509证书
yp (Wed, 12 Apr 2017 09:57:24 GMT):
默认会download到ca-clinet 环境变量中，如果没有设置，会download到$HOME/.fabric-ca-client
yp (Wed, 12 Apr 2017 09:58:55 GMT):
这里要注意，cacert是隐藏的～～～没有前缀，文件名就是.pem
yp (Wed, 12 Apr 2017 10:05:45 GMT):
目前为止的fabric-ca，是个坑，不建议你跳。。。
yong (Wed, 12 Apr 2017 10:07:07 GMT):
@yp 谢谢，我目前想做这样一件事情。我想模拟银行开2个账户，然后用这两笔账户进行转帐。不晓得怎么实现？
yong (Wed, 12 Apr 2017 10:07:53 GMT):
@yp 有微信联系方式吗？
JasonD (Wed, 12 Apr 2017 10:42:15 GMT):
@yp ca目前有哪些坑
yp (Wed, 12 Apr 2017 11:58:57 GMT):
@yong @JasonD 坑1: 说明文档请参考fabric下面的ca-setup，不要看fabric-ca的文档
yp (Wed, 12 Apr 2017 12:02:02 GMT):
坑2:除非对整个1.0的架构有所了解，否则不建议使用分层CA，比如root／sub CA，使用默认配置即可。打个比方，如果要建立orderCA和nodeCA，那么其继承，从属关系，以及证书chain如何传递。。目前在这个坑里，不知道能不能爬出来。。。
yp (Wed, 12 Apr 2017 12:05:05 GMT):
@yong 如果你要模拟账户，用单CA，然后申请type是user，详细查看hf.Registrar.Roles。 如果要忽悠客户，就用ldap，将用户认证丢到ldap去，ca这边只管证书
yp (Wed, 12 Apr 2017 12:11:31 GMT):
不过话说回来，如果要搭一个全功能的fabric1.0。就势必要先理清channel，org（ep组，e-policy）sp，sdk，因为要先创建channel.tx和order.block，在创建这两个的时候，又需要ca来弄证书
yp (Wed, 12 Apr 2017 12:12:48 GMT):
目前提供的e2e_example，只是跑了下ep和ep-policy～～倒是NODE SDK那边提供的sample更详细一点
yp (Wed, 12 Apr 2017 12:20:36 GMT):
创建channel.tx orderer.block需要弄configtx.yaml， configtx.yaml又需要和CA的org分配以及证书保持一致。。。索性就跳先CA的坑了。。。不知道我的方向是否正确，或者有大神及时指正，早日脱坑～～
yp (Wed, 12 Apr 2017 12:22:23 GMT):
@baohua configtx.yaml的org和CA的id.affiliation ，attr需保持一致，理解是否正确？
yp (Thu, 13 Apr 2017 01:36:21 GMT):
继续补充 fabric坑3 ：如果用分级CA，记得设置intermediatecerts～
Ying (Thu, 13 Apr 2017 02:57:24 GMT):
[ ](https://chat.hyperledger.org/channel/twg-china?msg=87Fhzu3JRpyzbtiWw) @yp 学习了。赞
baohua (Thu, 13 Apr 2017 03:16:07 GMT):
@yp 总结的不错 不过有些地方其实不是坑 比如分级这本来就是 pki 的常见做法；configtx 本来就是需要配置的。fabric ca 的很多设计并不是自己原创的，是遵循一些现成的做法。从 ca 着手是可以的，建议的路线可以是 pki-->cfssl --> fabric-ca，这样更能理清楚来龙去脉。:grinning:
baohua (Thu, 13 Apr 2017 03:16:07 GMT):
@yp 总结的不错 不过有些地方其实不是fabric 的坑 比如分级这本来就是 pki 的常见做法；configtx 本来就是需要配置的。另外，fabric ca 的很多设计并不是自己原创的，是遵循一些现成的做法。从 ca 着手是可以的，这块建议的路线可以是 pki-->cfssl --> fabric-ca，这样更能理清楚来龙去脉。:grinning:
baohua (Thu, 13 Apr 2017 03:17:04 GMT):
https://github.com/yeasy/blockchain_guide/blob/master/SUMMARY.md 看下密码学相关这一章 有些背景最好先了解。
yp (Thu, 13 Apr 2017 03:33:50 GMT):
@baohua pki-->cfssl --> fabric-ca 多谢！其实【坑】这个词只是对于个人而言，自己不明白的也叫坑。。。就随口说说，不具备其他意义:smile:
yp (Thu, 13 Apr 2017 10:33:55 GMT):
ca坑4:[ ](https://chat.hyperledger.org/channel/fabric-ca?msg=jvrXAXzLN68E3mmmx)
MikeMayori (Thu, 13 Apr 2017 20:24:47 GMT):
Inglish por favor
MikeMayori (Thu, 13 Apr 2017 20:24:47 GMT):
English por favor
cbf (Thu, 13 Apr 2017 22:13:48 GMT):
@MikeMayori the TWG-china is the Technical Working Group for China
cbf (Thu, 13 Apr 2017 22:14:44 GMT):
we created specifically so that they could communicate what's going on generally (with the projects, with the TSC, etc) in Chinese with their colleagues in China
cbf (Thu, 13 Apr 2017 22:15:35 GMT):
this is a global project and we try our best to accommodate all
MikeMayori (Thu, 13 Apr 2017 22:22:18 GMT):
Well , you have great minds in china and any update will be cool too
baohua (Fri, 14 Apr 2017 02:07:31 GMT):
@MikeMayori Understand ur question, while we welcome both english and chinese in this channel, to accommodate various developers as our best. And i guess it should be OK to post english here, many people in the channel can use that :)
baohua (Fri, 14 Apr 2017 02:07:31 GMT):
@MikeMayori Understand ur question, while we welcome both english and chinese in this channel, to accommodate various developers as our best. Certainly it should be OK to post english here, many people in the channel can use that :)
zerppen (Fri, 14 Apr 2017 02:41:13 GMT):
hi Jim @jimthematrix fabric-sdk-java-1.0-SNAPSHOT.jar里的.class文件是通过grpc协议自动生成的还是开发人员写的
如果是协议自动生成，那么协议文件在哪，这个jar包里没看到对应的协议文件。
如果是开发人员编写的，那能不能给设计文档
zerppen (Fri, 14 Apr 2017 03:01:50 GMT):
Language is used for communication.Chinese is more effective when discusser are Chinese in consideration of poor English.But if we need discuss with all members here,English will be more effective.
ylsGit (Fri, 14 Apr 2017 03:03:49 GMT):
执行 e2e_cli peer chaincode instantiate时，报错“Failed to deserialize creator identity, err MSP Org0MSP is unknown”，咋回事呢？
yp (Fri, 14 Apr 2017 03:15:19 GMT):
@ylsGit instantiate的时候，channel.tx已经被作为创世交易（个人叫法）导入到channel里了，channel里已经包含了org信息（从属，证书，你可以文本文件打开channel.tx查看一下），你这个问题，应该是channel.tx里面没有Org0MSP信息，或者Org0MSP信息没有被正确生成。
ylsGit (Fri, 14 Apr 2017 03:15:58 GMT):
好，我重新走一遍试试
yp (Fri, 14 Apr 2017 03:20:00 GMT):
我记得e2e_cli例子里面，instantiate是在peer2上执行的，peer2属于Org1啊，应该是Org0MSP才对
yp (Fri, 14 Apr 2017 03:20:17 GMT):
应该是Org1MSP才对
zhangchao (Fri, 14 Apr 2017 03:31:29 GMT):
@ylsGit 能将你的deserialize creator identity代码贴上来看看吗
zhangchao (Fri, 14 Apr 2017 03:31:51 GMT):
我正打算写这个功能
zhangchao (Fri, 14 Apr 2017 03:32:02 GMT):
学习一下
ylsGit (Fri, 14 Apr 2017 03:39:59 GMT):
好了
ylsGit (Fri, 14 Apr 2017 03:40:40 GMT):
不过instantiate后，只在peer0上启动了个Chaincode，其他节点上没有呢。
yp (Fri, 14 Apr 2017 04:12:18 GMT):
@ylsGit 个节点需要单独install，1.0中 cc不广播
LIANSHE (Fri, 14 Apr 2017 11:48:34 GMT):
Has joined the channel.
jimthematrix (Sat, 15 Apr 2017 03:06:21 GMT):
@zerppen jar 里面既包括protobuf编译器根据proto文件生成的代码（org.hyperledger.fabric.protos包里面的）也有手写的（org.hyperledger.fabric.sdk包)。目前SDK的设计文档在https://docs.google.com/document/d/1R5RtIBMW9fZpli37E5Li5_Q9ve3BnQ4q3gWmGZj6Sv4/edit但一部分内容需要更新
lignyxg (Sat, 15 Apr 2017 07:50:45 GMT):
[ ](https://chat.hyperledger.org/channel/twg-china?msg=87Fhzu3JRpyzbtiWw) @yp 使用分级CA应该从哪设置intermediatecerts？我用intermediate ca生成的证书，在peer启动时验证失败，直接使用root ca就可以
Lin-YiTang (Sat, 15 Apr 2017 11:04:06 GMT):
Message Attachments
Lin-YiTang (Sat, 15 Apr 2017 11:04:35 GMT):
有人曉得這怎麼排除嗎？
我都無法 make
zerppen (Sat, 15 Apr 2017 11:19:02 GMT):
@jimthematrix 我也是认为这个jar包手写的接口居多。fabric SDK的文档我在去年已经看过，最近更新的也比较少，和我们javaSDK的接口对比，参考性又会下降很多。为了能让javaSDK能够追上fabric的进度（目前只支持fabric到3月31的代码），我司从下周开始可以投入两个人来专门研究javaSDK（处理需求及解决bug），我希望有一份jar包接口设计文档，这样肯定也会事半功倍
zerppen (Sat, 15 Apr 2017 11:19:02 GMT):
@jimthematrix 就是说jar里面org.hyperledger.fabric.protos里所有代码都是自动生成的吗？因为我之前一直以为这块并不是完全自动生成，而且我认为大多数接口是手写的。fabric SDK的文档我在去年已经看过，最近更新的也比较少，和我们javaSDK的接口对比，参考性又会下降很多。为了能让javaSDK能够追上fabric的进度（目前只支持fabric到3月31的代码），我司从下周开始可以投入两个人来专门研究javaSDK（处理需求及解决bug），我希望有一份jar包接口设计文档，这样肯定也会事半功倍
zerppen (Sat, 15 Apr 2017 13:51:24 GMT):
@Lin-YiTang 试一下 sudo make
Lin-YiTang (Sat, 15 Apr 2017 13:53:55 GMT):
@zerppen 沒用
zerppen (Sat, 15 Apr 2017 15:00:18 GMT):
看一下是不是git clone下来的文件有被你无意改动
jimthematrix (Sat, 15 Apr 2017 17:28:21 GMT):
@zerppen 请问贵公司是哪一家？很欢迎加入javaSDK开发。设计文档一时半会还出不来，最好的办法就是研究代码，尤其是从integration tests入手可以基本了解接口设计原则
zerppen (Sun, 16 Apr 2017 02:09:13 GMT):
@jimthematrix 你好,我们是梧桐树。多谢你给的建议。 javaSDK我有做过调研,各模块的功能等有相应整理，里面确实不少地方会直接调用jar里面的方法。如果有好的方式推荐，当然我更希望的是直接调用jar里的内容来写javaSDK。我看sanchezl提交到gerrit上关于chaincode event代码就import了新的org.hyperledger.fabric.protos下的包，不管这是他自己定义proto文件生成还是他自己手写的，我觉得我的团队如果要完成protos下的代码挑战性比较大
leoleo (Mon, 17 Apr 2017 00:59:12 GMT):
Has joined the channel.
grapebaba (Mon, 17 Apr 2017 02:49:14 GMT):
@zerppen 这个代码肯定是自动生成的啊
grapebaba (Mon, 17 Apr 2017 02:55:08 GMT):
javaSDK我看了一下，目前进度跟node应该差不多
grapebaba (Mon, 17 Apr 2017 02:55:17 GMT):
直接用就可以了
zerppen (Mon, 17 Apr 2017 03:00:38 GMT):
@grapebaba 我是在想是不是我们在写SDK的时候需要我们人为定义proto，比如这个https://gerrit.hyperledger.org/r/#/c/8033/
grapebaba (Mon, 17 Apr 2017 03:02:21 GMT):
没懂
grapebaba (Mon, 17 Apr 2017 03:03:00 GMT):
你是用SDK来做应用还是要做SDK？
zerppen (Mon, 17 Apr 2017 03:03:21 GMT):
@jimthematrix 做SDK
zerppen (Mon, 17 Apr 2017 03:03:21 GMT):
做SDK
zerppen (Mon, 17 Apr 2017 03:03:54 GMT):
就是直接和javaSDK项目组一起做
grapebaba (Mon, 17 Apr 2017 03:04:30 GMT):
ok，那直接提交patch就好了吧
zerppen (Mon, 17 Apr 2017 03:04:47 GMT):
之前给客户演示的是用的fabric app
zerppen (Mon, 17 Apr 2017 03:06:08 GMT):
我的意思是 现在jar里面还缺少内容 如果让我们来弄这个就有点困难
zerppen (Mon, 17 Apr 2017 03:06:51 GMT):
简单的说 就是希望项目组那边能先把底层classes文件都完善了
zerppen (Mon, 17 Apr 2017 03:08:11 GMT):
我在上面给的那个链接里，就是底层的那个包没有实现，所以在0.6的时候也没法用，现在还在测试
grapebaba (Mon, 17 Apr 2017 03:11:58 GMT):
这个patch实现你要的功能了吗？
zerppen (Mon, 17 Apr 2017 03:23:49 GMT):
你说的是我链接里的那个 还是？ 我不太明白
zerppen (Mon, 17 Apr 2017 03:26:41 GMT):
我这边在整理jira上关于javaSDK这块还没有实现，但是我们应该可以实现的任务号。我们也希望 @jimthematrix 可以直接assign 给我，这样我也就不用一个一个去查看，然后评估是不是能做了
grapebaba (Mon, 17 Apr 2017 03:29:50 GMT):
这块是这样的，没有assign的，你觉得可以实现的，你们在comment里面写一下，自己可以assign的
zerppen (Mon, 17 Apr 2017 03:36:15 GMT):
@grapebaba 哈哈 那还是我自己整理的
zerppen (Mon, 17 Apr 2017 03:36:15 GMT):
@grapebaba 哈哈 那还是我自己整理吧
jimthematrix (Mon, 17 Apr 2017 03:37:21 GMT):
@zerppen https://jira.hyperledger.org/secure/RapidBoard.jspa?rapidView=99&view=planning 所有javaSDK v1.0目前仍需完成的内容都在这里了
zerppen (Mon, 17 Apr 2017 03:37:44 GMT):
好的 多谢了 @jimthematrix
jimthematrix (Mon, 17 Apr 2017 03:37:53 GMT):
注意v1.0.0标签（FixInVersion)
zerppen (Mon, 17 Apr 2017 03:38:06 GMT):
好的
jimthematrix (Mon, 17 Apr 2017 03:40:30 GMT):
很多JIRA可能没有很详细的说明，要是有问题随时在这里或者#fabric-sdk-java群里问
zerppen (Mon, 17 Apr 2017 03:40:54 GMT):
是的 我看到有的甚至没有说明
zerppen (Mon, 17 Apr 2017 03:41:11 GMT):
我看之前大家在完善的时候有参考node
yp (Mon, 17 Apr 2017 06:41:56 GMT):
@jimthematrix 咨询下。现在fabric中的Organizations该怎么理解，一个org包括了一套自己的sdk，user，orderer，e／c-peer ，？ 还是说sdk/user属于一个个单独的org，而节点role（orderer，peer）是整个系统公用的？
yong (Mon, 17 Apr 2017 09:01:54 GMT):
请教一个问题，怎么配置能够使fabric和fabric-ca能够联动起来，比如做一些基于帐号的交易等？
yp (Mon, 17 Apr 2017 10:14:11 GMT):
@yong fabric只需要证书，ca只发行证书，fabric运行不需要ca，止需要证书，不管你证书是从哪里的ca发行的
yong (Mon, 17 Apr 2017 10:20:52 GMT):
可能是我表达错误。能这样理解吗？在V1.0里面membership成员管理模块也就是fabric-ca模块。
yong (Mon, 17 Apr 2017 10:21:42 GMT):
@yp
yong (Mon, 17 Apr 2017 10:23:38 GMT):
@yp 如果fabri-ca模块具有成员管理功能，在整个fabric系统运行的过程中，
yong (Mon, 17 Apr 2017 10:25:01 GMT):
比如进行帐号转帐，fabric是需要通过fabric-ca获取有效的帐号
yp (Mon, 17 Apr 2017 10:33:59 GMT):
@yong 如果ca具有成员管理功能，那么成员的管理应该是在client sdk中操作，授权是由chaincode来实现
yp (Mon, 17 Apr 2017 10:37:19 GMT):
fabric，分布式账簿，它应该只管正确安全的记账，不应该背负太多职责。
yong (Mon, 17 Apr 2017 10:39:56 GMT):
@yp 能具体说下“授权是由chaincode来实现”的吗？
yp (Mon, 17 Apr 2017 10:42:37 GMT):
# The registry section controls how the fabric-ca-server does two things:
# 1) authenticates enrollment requests which contain a username and password
# (also known as an enrollment ID and secret).
# 2) once authenticated, retrieves the identity's attribute names and
# values which the fabric-ca-server optionally puts into TCerts
# which it issues for transacting on the Hyperledger Fabric blockchain.
# These attributes are useful for making access control decisions in
# chaincode.
yp (Mon, 17 Apr 2017 10:42:58 GMT):
这个是fabric-ca-server的配置文件中的描述，你看一下
yong (Mon, 17 Apr 2017 10:44:01 GMT):
@yp 要得。感谢，还有个问题，和fabric-ca交互，是fabric-sdk-node/java/xxx来负责的吗？那fabric-ca-client主要做什么？
yp (Mon, 17 Apr 2017 10:45:32 GMT):
你得先enroll，拿到rootca，或者是上层证书链才能注册呀。
yp (Mon, 17 Apr 2017 10:47:32 GMT):
比如说，peer节点的证书，需要ca-client来enroll对应的id，生成证书啊，还要拉去与其通信的个节点的公钥证书
yp (Mon, 17 Apr 2017 10:47:47 GMT):
当然～～你用u盘copy也成啊～～～
yp (Mon, 17 Apr 2017 10:49:06 GMT):
https://github.com/hyperledger/fabric/blob/master/docs/source/images/fabric-ca.png
jimthematrix (Mon, 17 Apr 2017 13:21:44 GMT):
@yp 关于Organizations最重要的是MSP（Member Service Provider），囊括了颁发身份证书的权利（每个Org的CA颁发的证书可以被fabric认可，因为CA自己已经在fabric报备过了），以及对交易进行公证和背书的义务。每个Org主要的体现在于有自己的peers，一般也会有自己的app（sdk），但不一定有自己的orderer。
yp (Mon, 17 Apr 2017 14:29:02 GMT):
@jimthematrix 多谢回复。也就是说当有新的org加入时，应当同时提供你自己的peer和app，向ca申请并使用证书用于接入fabric网络？我原来认为当新的org加入时可以不提供peer，只需将app/user向ca报备，然后在原有网络中新建一条channel用于自己业务合约的使用。
yp (Mon, 17 Apr 2017 14:33:36 GMT):
另外一方面，由于除了orderer之外，还有endorse peer和app通信，如果有新org加入，使用自己的endorse peer，submit peer，vp。那么这个org就是相对独立的一个系统（除了orderer），那么他为什么不自己做一套系统，而来加入你的fabric系统呢？
zhangchao (Mon, 17 Apr 2017 14:36:52 GMT):
自己做一套系统的话，用数据库就完事了，还考虑什么fabric?
yp (Mon, 17 Apr 2017 14:41:12 GMT):
假如你的peer群是所有member共享的，只是沟通的channel各自不同，那我当然乐于申请接入，但是要我自己这个org带着ep，vp来，那我再带个orderer就可以自己再组一个fabric了啊。现在看起来org几乎是相对独立的啊
yp (Mon, 17 Apr 2017 14:47:50 GMT):
实际的业务场景中也存在类似的诉求，在供应链中，下游公司要加入系统，我可以提供若干peer，但是我跑的数据就在我自己提供的peer上跑，那我确实弄个数据库就够了。
yp (Mon, 17 Apr 2017 15:05:24 GMT):
@zhangchao 我没有表示清楚，如果我自己的peer都去ca报备，接入系统，使得我的ep可以和其他ep通信，这样就说的通了
yp (Mon, 17 Apr 2017 15:06:11 GMT):
只是现在我在组分级ca时，org到底处于一个什么样的地位，还不是很清楚
zhangchao (Mon, 17 Apr 2017 15:06:30 GMT):
别人的peer由你来提供，就好像说别人的比特币钱包由你提供一样，很难让人信服
zhangchao (Mon, 17 Apr 2017 15:07:25 GMT):
ca是松散组织，根ca也可以有好多
yp (Mon, 17 Apr 2017 15:07:33 GMT):
也就是说不存在跨org的endorse policy的说法？
zhangchao (Mon, 17 Apr 2017 15:08:20 GMT):
ca我感觉仅仅管理csr请求和证书颁发，其他都不管了
yp (Mon, 17 Apr 2017 15:11:03 GMT):
对的，但是ep之间，ep，sp之间应该有相同的ca报备，相同的ca公钥证书，才能互相可信链接的
yp (Mon, 17 Apr 2017 15:11:24 GMT):
不知道理解对不
zhangchao (Mon, 17 Apr 2017 15:12:23 GMT):
他们不都是根ca或者中级ca颁发的吗，只要是这些ca发的，都会互信
zhangchao (Mon, 17 Apr 2017 15:13:26 GMT):
不同ca发的证书不影响对主体的信任问题
yp (Mon, 17 Apr 2017 15:14:31 GMT):
嗯，对的，之前看回答，以为org是完全独立的，org下面的peer也是独立的...才有此疑问
zhangchao (Mon, 17 Apr 2017 15:18:08 GMT):
理论上同一个org内的ca应该是同一个，但是也不一定，不是一个ca也不影响
yp (Mon, 17 Apr 2017 15:19:46 GMT):
那存在两个不同org，各自有自己的rootca的情况么？
zhangchao (Mon, 17 Apr 2017 15:20:03 GMT):
会的
zhangchao (Mon, 17 Apr 2017 15:20:16 GMT):
ca的证书都在truststore里面存放
zhangchao (Mon, 17 Apr 2017 15:20:54 GMT):
用的时候会使用里面的某个ca证书来验证对方的证书
yp (Mon, 17 Apr 2017 15:24:02 GMT):
这下明白了！哈哈！多谢:grinning:
jimthematrix (Mon, 17 Apr 2017 17:31:27 GMT):
@yp 每个org加入时，首先要确定自己的CA，可以用fabric-ca或者任何已有的标准CA，然后将CA的root cert提交到联盟管理员那里以便向fabric报备（就是加到orderer维护的系统channel的设置区块里），这是第一步，然后这个org就是正式成员了。接下来一般会开启peer节点（每个peer需要有CA签名的身份证书设置在“local MSP”里），然后就是加入channel或者开始新的channel。注意channel的目的是和其他的org一起参加合约的执行和背书，所以channel肯定是多于一个org的。如果peer不加入任何channel，那它什么都做不了，也就失去用区块链的意义了
jimthematrix (Mon, 17 Apr 2017 17:39:05 GMT):
@yp 你的org和ca之间的关系的疑问不知道上面和 @zhangchao 的讨论中是否都解决了，关键在于org之间的互信是建立在上面说的“第一步”，每个org基本都会用自己的CA，但是所有org的CA都在orderer那里报备了（这是一个由联盟系统管理员进行的操作，并且根据在创世块里规定的条约需要其他现有成员批准并提供签名背书），所以org之间的互信是由orderer维护的系统channel提供的
jimthematrix (Mon, 17 Apr 2017 17:40:27 GMT):
“由orderer维护的系统channel” - 也就是 @zhangchao 上面说的truststore
baohua (Tue, 18 Apr 2017 03:13:54 GMT):
orderer和如何配置这块文档比较少 确实很多人都碰到一些问题。https://wiki.hyperledger.org/community/fabric-design-docs
yp (Tue, 18 Apr 2017 03:33:13 GMT):
@jimthematrix 非常感谢您的回复，我的疑问都解决了。 之前我一直以为fabric系统中只允许有一个root cert的存在，所以在ca-server和configtx配置中存在好多模糊不清的东西。现在就非常清晰了。@zhangchao 那边我了解到了truststore的存在，使得多root cert可以并存与fabric，从你这边了解到了多root cert该如何通过orderer，以及channel来组网，收获颇丰。
lignyxg (Tue, 18 Apr 2017 03:34:03 GMT):
@yp 应该怎么使用intermediate CA？是不是要在哪里配置一下，我之前看你说需要设置intermediatecerts，但没找到在哪
yp (Tue, 18 Apr 2017 03:34:22 GMT):
@jimthematrix @zhangchao 再艾特一遍，多谢多谢～！
lignyxg (Tue, 18 Apr 2017 03:39:32 GMT):
@yp 是在ca 的config文件中？还是在configtx.yaml中，都没看到
yp (Tue, 18 Apr 2017 03:43:15 GMT):
@lignyxg 如果你在init／start ca server时使用了-u 参数来连接其他ca的话，你的server会有一个ca-chain.pem的证书，这个文件中有两个证书，第一个是你连接的ca的证书，第二个是你的server的证书，这个时候需要设置intermediatecerts目录，来存放你的server的证书，copy出来就可以
yp (Tue, 18 Apr 2017 03:44:43 GMT):
├── Org1peer1
│ ├── admincerts
│ │ └── app.pem
│ ├── cacerts
│ │ └── app.pem
│ ├── intermediatecerts
│ │ └── sub.pem
│ ├── keystore
│ │ └── key.pem
│ └── signcerts
│ └── cert.pem
yp (Tue, 18 Apr 2017 03:44:57 GMT):
这个目录结构你可以参考一下
yp (Tue, 18 Apr 2017 03:46:05 GMT):
其中sub.pem就是app.pem文件中的第二个证书
yp (Tue, 18 Apr 2017 03:47:25 GMT):
如果不设置intermediatecerts的话，create channel的时候报错的。。当然，你如果不用-u 参数来启动ca server的话，就不需要这么麻烦了
yp (Tue, 18 Apr 2017 03:51:14 GMT):
我是在create channel报错的时候，去source里面找到，文档么，目前没有发现那里有写。
jimthematrix (Tue, 18 Apr 2017 04:31:56 GMT):
[ ](https://chat.hyperledger.org/channel/twg-china?msg=TdAufnQE79Z8sKfuc) @baohua 基本上目前有用的文档还比较少，所有组件都有这个问题:wink:
lignyxg (Tue, 18 Apr 2017 04:40:14 GMT):
@yp 谢谢您的解答。
lignyxg (Tue, 18 Apr 2017 06:22:59 GMT):
[ ](https://chat.hyperledger.org/channel/twg-china?msg=BzukmBXeJK46fDhX3) 我理解您这里提到的第一步，在实际操作中是通过configtxgen生成的genesis.block来进行配置的，orderer通过它创建了系统channel，不知道是否理解正确？但我在config.yaml中没有看到设置ca，有关于Organizations的设置，请问*将CA的root cert提交到联盟管理员那里以便向fabric报备*是怎样设置的呢？
lignyxg (Tue, 18 Apr 2017 06:25:41 GMT):
@jimthematrix
zerppen (Tue, 18 Apr 2017 09:06:23 GMT):
我直接从github上clone下来的代码，本地测试后准备提交 请前辈指点一下
zerppen (Tue, 18 Apr 2017 09:06:23 GMT):
我直接从github上clone下来的代码，jira上assign了一个任务后，完成本地测试准备提交 请前辈指点一下
zerppen (Tue, 18 Apr 2017 09:23:50 GMT):
@rickr Hi rick,I have done FAB-3211 and finished local test.But I am a freshman to use git push code to gerrit review,i need learn how to use it.
rickr (Tue, 18 Apr 2017 09:23:51 GMT):
Has joined the channel.
zerppen (Tue, 18 Apr 2017 10:36:19 GMT):
1) git remote gerrit rename ssh://zerppen@gerrit.hyperledger.org:29418/fabric-sdk-java
zerppen (Tue, 18 Apr 2017 10:36:19 GMT):
1) git remote gerrit rename ssh://zerppen@gerrit.hyperledger.org:29418/fabric-sdk-java
zerppen (Tue, 18 Apr 2017 10:36:19 GMT):
1) git remote add gerrit ssh://zerppen@gerrit.hyperledger.org:29418/fabric-sdk-java
zerppen (Tue, 18 Apr 2017 10:37:55 GMT):
2) git review 得到：remote: Processing changes: refs: 1, done
To ssh://gerrit.hyperledger.org:29418/fabric-sdk-java
! [remote rejected] HEAD -> refs/publish/master/FAB-3211 (not Signed-off-by author/committer/uploader in commit message footer)
error: failed to push some refs to 'ssh://zerppen@gerrit.hyperledger.org:29418/fabric-sdk-java'
zerppen (Tue, 18 Apr 2017 10:37:55 GMT):
'
zerppen (Tue, 18 Apr 2017 10:38:51 GMT):
git commit -a -s 的时候添加了signed-off-by author 及相关文件说明
zerppen (Tue, 18 Apr 2017 10:39:31 GMT):
请帮忙给看看
jimthematrix (Tue, 18 Apr 2017 13:12:32 GMT):
@lignyxg config.yaml 里针对每个org都需要相应的MSPDir，这个目录里必须包含caroots子目录，里面放的就是CA certs
lignyxg (Tue, 18 Apr 2017 13:21:34 GMT):
@jimthematrix 我在examples/e2e_cli的例子中找到了localMspConfig目录，下面分别有 admincerts, cacerts, keystore, signcerts，没有找到您说的caroots子目录。随后我使用fabric-ca注册了peer，使用得到的证书按照e2e的格式设置了目录结构，也可以完成组网。所以才有上面的疑问，因为没有按照您说的设置ca报备给fabric
lignyxg (Tue, 18 Apr 2017 13:44:17 GMT):
@jimthematrix 我对比了一下，发现原来cacerts子目录包含的就是CA certs:grin:
jimthematrix (Tue, 18 Apr 2017 13:52:47 GMT):
ah ok sorry, yeah it's "cacerts" not "caroots" ;-)
zerppen (Tue, 18 Apr 2017 13:54:41 GMT):
@jimthematrix 请问你这边有没有对burrow项目一些详细的资料。我看了github的项目，看不太明白
jimthematrix (Tue, 18 Apr 2017 14:04:51 GMT):
还没来得及仔细关心
lignyxg (Tue, 18 Apr 2017 14:19:38 GMT):
@jimthematrix 如果有新的org想要加入到现有的网络中，应该怎么办，需要通过自己的configtxgen向orderer提供 block吗？您之前说“根据创世块里规定的条约需要现有成员的批准并提供签名”，但没看到在哪里设置这种策略，另外现有成员是否批准的标准又是什么？谢谢您
jimthematrix (Tue, 18 Apr 2017 17:38:17 GMT):
向现有网络加入新org正在做，是会通过channel config更新来实现。在跟新时向orderer提交的config proto必须有相应条约规定的成员签名才允许通过，而收集签名是app需要做的，基本想法是先通过SDK或者configtxgen来生成新的config proto，然后分别发给成员，收集签名然后整合到config proto envelope里再提交给orderer
zerppen (Tue, 18 Apr 2017 23:57:54 GMT):
@jimthematrix 麻烦review一下 FAB-3211,这里我用的slf4j,因为它1）即可以选择用log4j也可以选择原来JDK内置日志管理，2）在配置maven的时候也更省事，3）rick说v1.1再用slf4j，我觉得如果v1.0用上没有跟其他地方冲突的话那不是更好吗？当然v1.1我也可以继续维护
lignyxg (Wed, 19 Apr 2017 01:47:47 GMT):
@jimthematrix 明白了，感谢您的解答
yahtoo (Wed, 19 Apr 2017 02:07:44 GMT):
@baohua 今天开会嘛？
baohua (Wed, 19 Apr 2017 02:08:08 GMT):
今天不开 下周开哦
yahtoo (Wed, 19 Apr 2017 02:09:02 GMT):
@baohua 下周三？
baohua (Wed, 19 Apr 2017 02:37:55 GMT):
对的 btw 你是？之前参加过会吗 没对上号 :wink:
jimthematrix (Wed, 19 Apr 2017 02:39:44 GMT):
@zerppen I added a comment to the JIRA
zerppen (Wed, 19 Apr 2017 07:25:58 GMT):
@jimthematrix thx,I think it will be published in v1.1.But we will use for our application
cophey (Wed, 19 Apr 2017 08:17:12 GMT):
Has joined the channel.
zhangmenghang (Thu, 20 Apr 2017 01:24:50 GMT):
有人遇到过这个问题吗，我再用java sdk连接fabric-alpha的过程中，一开始都是好好的，运行几天后java sdk突然报了找不到channel的404错误，但是我在cli里面执行invoke还是可以插入数据的，我在其他机器上用java sdk连接也报找不到channel的错误，重新部署fabric网络之后sdk就成功连上了。
baohua (Thu, 20 Apr 2017 01:48:13 GMT):
找不到 channel 的具体错误能贴一下吗
zhangmenghang (Thu, 20 Apr 2017 01:56:11 GMT):
Message Attachments
zhangmenghang (Thu, 20 Apr 2017 01:57:36 GMT):
fabric network的container都是好好的，处理也可以成功invoke，sdk之前也是好好的，突然重启一下就不行了，重新部署fabric network可以解决这个问题
zhangmenghang (Thu, 20 Apr 2017 01:57:51 GMT):
cli也可以成功invoke
baohua (Thu, 20 Apr 2017 01:58:05 GMT):
嗯 重启是重启的 fabric 吧
zhangmenghang (Thu, 20 Apr 2017 01:58:20 GMT):
重启的是sdk
zhangmenghang (Thu, 20 Apr 2017 01:58:43 GMT):
重启完就报这个错误，以前重启过无数次都没这个问题，也是偶尔才出现的
baohua (Thu, 20 Apr 2017 01:59:07 GMT):
哦 那可以在 #fabric-sdk-java channel 问问看 看起来是 sdk 的问题
zhangmenghang (Thu, 20 Apr 2017 01:59:50 GMT):
但是重新部署fabric network就好了，sdk那边什么都没改
zhangmenghang (Thu, 20 Apr 2017 02:00:24 GMT):
感觉像是orderer找不到channel了，但是cli里面invoke又可以。。好奇怪
ylsGit (Thu, 20 Apr 2017 03:58:02 GMT):
有没有人用goSDK是出错： KeyImport return error: Failed storing ECDSA key [Cannot store key. This is a dummy read-only KeyStore]
yp (Thu, 20 Apr 2017 05:16:20 GMT):
现在没有submit节点的概念了么？
baohua (Thu, 20 Apr 2017 05:21:38 GMT):
暂时没有剥离出 submit
yp (Thu, 20 Apr 2017 05:37:44 GMT):
那也就是说现在peer的角色只有endorse？
zhangchao (Thu, 20 Apr 2017 06:02:22 GMT):
每个peer既可以是submitter, endorser, committer吧
cophey (Thu, 20 Apr 2017 06:05:11 GMT):
peer cli只要endorse功能，peer节点应该都有submitter、endorser、committer功能的，只是需要sdk来调用吧
cophey (Thu, 20 Apr 2017 06:05:11 GMT):
peer cli只有endorse功能，peer节点应该都有submitter、endorser、committer功能的，只是需要sdk来调用吧
zhangchao (Thu, 20 Apr 2017 06:07:22 GMT):
endorser和committer应该是被动的吧
cophey (Thu, 20 Apr 2017 06:23:03 GMT):
应该是客户端收集endorser执行情况，然后根据情况去提交order吧，验证通过，order广播给committer，committer是被动的，endorser要主动请求才可以吧
yp (Thu, 20 Apr 2017 06:23:32 GMT):
第一，我在代码里没有找到那里使用了endorse.enable的开关读取，我怀疑目前的最新的代码里，peer只有一种，而且是全角色运行
yp (Thu, 20 Apr 2017 06:23:50 GMT):
第二，后续应该会剥离ep，sp，nvp的开关出来
yp (Thu, 20 Apr 2017 06:25:20 GMT):
第三，以后的节点分类应该是 endorse peer， commit peer（以前的vp），和NVP
yp (Thu, 20 Apr 2017 06:28:55 GMT):
submit peer这个概念只有在github的next文档里有提到，在jira的fab37问题中也没有提及，所以我觉得submit peer是否就是committer peer
cophey (Thu, 20 Apr 2017 06:29:18 GMT):
nvp应该不用了吧，指定了endorser，自然剩余的就是nvp。后面会剥离出sp，sp
cophey (Thu, 20 Apr 2017 06:29:18 GMT):
nvp应该不用了吧，指定了endorser，自然剩余的就是nvp。我觉得后面会剥离出sp，sp来收集ep执行结果，决定是否提交至order
yp (Thu, 20 Apr 2017 06:30:54 GMT):
不一定吧，因为我看到了txvalidator的开关， 也就是说，committer节点上，txvalidator为ture就是vp，为false就是nvp
yp (Thu, 20 Apr 2017 06:32:27 GMT):
目前也不做过多猜测了，过一个月再来研究研究:grimacing:
ylsGit (Thu, 20 Apr 2017 06:32:37 GMT):
有没有人用goSDK时出错： KeyImport return error: Failed storing ECDSA key [Cannot store key. This is a dummy read-only KeyStore]
yp (Thu, 20 Apr 2017 06:32:48 GMT):
目前保证一个月研究一遍，差不多能catchup上他的发展
yp (Thu, 20 Apr 2017 06:41:21 GMT):
@ylsGit 如果你是root权限出这个问题，试试用privileged=true来启动容器
yp (Thu, 20 Apr 2017 06:42:00 GMT):
没看清，，你是sdk。。没用容器。。
yp (Thu, 20 Apr 2017 06:42:05 GMT):
忽略～
ylsGit (Thu, 20 Apr 2017 06:42:09 GMT):
嗯
ylsGit (Thu, 20 Apr 2017 06:43:01 GMT):
我将调用sdk的代码写在fabric-sdk-go项目里就没问题，单独写一个项目引用fabric-sdk-go包就出那个错
zhangchao (Thu, 20 Apr 2017 07:03:07 GMT):
endorser难道不是等待peer给他发proposal吗
zhoupeiwen (Thu, 20 Apr 2017 08:55:35 GMT):
Has joined the channel.
yong (Thu, 20 Apr 2017 11:07:17 GMT):
CORE_PEER_LOCALMSPID等这些配置参数是在什么时候起作用的？代码里面也没有定义和使用？命令里面也没有使用？
yong (Thu, 20 Apr 2017 11:07:17 GMT):
CORE_PEER_LOCALMSPID等这些配置参数是在什么时候起作用的？代码里面也没见定义和使用。
yong (Thu, 20 Apr 2017 11:13:19 GMT):
[ ](https://chat.hyperledger.org/channel/twg-china?msg=LnWH83ai4qFSjDf8S) @yong
yong (Thu, 20 Apr 2017 11:14:51 GMT):
CORE_PEER_MSPCONFIGPATH=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peer/peer0/localMspConfig CORE_PEER_ADDRESS=peer0:7051 CORE_PEER_LOCALMSPID="Org0MSP" peer channel create -o orderer:7050 -c mychannel -f crypto/orderer/channel.tx
yong (Thu, 20 Apr 2017 11:15:29 GMT):
这里的peer命令怎么去获取CORE_PEER_LOCALMSPID的配置参数？
yp (Thu, 20 Apr 2017 11:26:08 GMT):
@yong https://github.com/hyperledger/fabric/blob/master/peer/main.go#L111
yp (Thu, 20 Apr 2017 11:26:33 GMT):
看下viper怎么用就知道了
baohua (Fri, 21 Apr 2017 02:39:34 GMT):
@here Dear all, we will have meeting this Wednesday morning(10AM), pls help update the agenda before the meeting, thanks! https://wiki.hyperledger.org/groups/twgc/meeting/2017-04-26
ylsGit (Fri, 21 Apr 2017 02:39:56 GMT):
ok
jimthematrix (Fri, 21 Apr 2017 16:48:12 GMT):
@yong local MSP 是决定peer自己的身份，用来对背书进行签名，还有针对一些非channel的请求进行权限认证，比如join channel，install chaincode，这些请求都需要peer用自己的local MSP确认权限（基本上就是看请求方是否属于同一个organization）
hurf (Sat, 22 Apr 2017 08:37:04 GMT):
Has joined the channel.
yahtoo (Sat, 22 Apr 2017 08:44:47 GMT):
@jimthematrix 如何把1.0部署到局域网多台机器上？
yahtoo (Sat, 22 Apr 2017 08:49:23 GMT):
examples/e2e_cli tls的例子部署到多台机器上，应该如何设置呢？
leungjob (Mon, 24 Apr 2017 03:17:28 GMT):
fabric-ca 怎么应用到peer验证？
leungjob (Mon, 24 Apr 2017 03:20:55 GMT):
fabric-ca怎么应用到各个peer,yaml文件应该怎么配置？
baohua (Mon, 24 Apr 2017 03:34:27 GMT):
@here we're collecting the user cases of hyperledger technologies, pls feel free to help add more, thanks! https://wiki.hyperledger.org/groups/twgc/team_cs
jimthematrix (Mon, 24 Apr 2017 09:33:30 GMT):
@yahtoo 这个一两句话很难说清楚，基本上每个docker instance都可以放在不同的host上，但设置起来会比较复杂，还要注意部署次序
jimthematrix (Mon, 24 Apr 2017 09:39:55 GMT):
比如在生成orderer的创世块时，需要知道每个org的anchor peer，用于对gossip的设置
yp (Mon, 24 Apr 2017 09:41:08 GMT):
@jimthematrix 你好，咨询个问题。orderer上用channel.tx创建的channel.block，只能物理copy到peer上，peer才能join进去？
jimthematrix (Mon, 24 Apr 2017 09:42:10 GMT):
不需要，peer上有join的API，sdk都支持的
jimthematrix (Mon, 24 Apr 2017 09:42:33 GMT):
@yp ^^^
jimthematrix (Mon, 24 Apr 2017 09:44:08 GMT):
@leungjob 这个可以参考node SDK的docker-compose.yaml
yp (Mon, 24 Apr 2017 09:44:29 GMT):
我也觉得不应该这样，应该有orderer来统一分发，但是我手动join的时候，-b, --blockpath string，这个参数指定了就能join进去，不指定就不行
yp (Mon, 24 Apr 2017 09:45:39 GMT):
是不是指定一下-o 就可以了
jimthematrix (Mon, 24 Apr 2017 09:46:06 GMT):
这个是peer cli的一些设计特点，如果用sdk的话，只要指定oederer的地址就行了
jimthematrix (Mon, 24 Apr 2017 09:46:57 GMT):
sdk会先从orderer找到channel的设置块，再转发给peer
jimthematrix (Mon, 24 Apr 2017 09:48:42 GMT):
建议你开一个jira bug，让peer cli也能同样工作，省略blockpath。
jimthematrix (Mon, 24 Apr 2017 09:49:41 GMT):
或者干脆自己提交一个更新;-)
yp (Mon, 24 Apr 2017 09:54:53 GMT):
@jimthematrix 哦，这样啊。。多谢多谢。回头去jira上起个bug
yong (Mon, 24 Apr 2017 12:42:31 GMT):
@jimthematrix 在example/e2e_cli的configtx.yaml实例中，按照http://hyperledger-fabric.readthedocs.io/en/latest/getting_started.html?highlight=configtx.yaml的说法，存在Org1和Org2两个org。想请教几个问题：
1、configtx.yaml中的OrdererOrg算是一个org吗？
2、configtx.yaml中指定了peer0属于Org1，peer2属于Org2。但文档中描述PEER0 and PEER1 belong to Org0; PEER2 and PEER3 belong to Org1？
3、怎么理解hyperledger里面的org，org之间需要通信吗？如果要，是基于AnchorPeer吗？
yong (Mon, 24 Apr 2017 12:45:25 GMT):
4、能不能把orderer和peer纳入一个org？
jimthematrix (Mon, 24 Apr 2017 17:50:17 GMT):
@yong:
- OrdererOrg is a separate org yes
- configtx.yaml only defines "AnchorPeers" which are used for gossip purposes. Anchor peers are subset of peers inside an organization. so: peer0/1 belong to org1, but only peer0 is an anchor peer, and peer2/3 belong to org2, but only peer 2 is anchor peer
- org is also called "member" or "participant", which represent a counterparty in a business transaction (or other entities like auditors and regulators). there are communications among orgs in the form of gossip (for disseminating blocks). for that to happen each org need to designate an anchor peer
jimthematrix (Mon, 24 Apr 2017 17:51:02 GMT):
抱歉回复比较长所以用英文方便一些 ;-)
baohua (Tue, 25 Apr 2017 01:12:02 GMT):
这里需要理解 anchorpeer的作用，作为一个 channel/org 的代表，从 orderer 获取信息，并组内广播给其它的 peer。其它 peer 可以不直接跟 orderer 打交道了。
grapebaba (Tue, 25 Apr 2017 01:21:05 GMT):
这里有个问题，如果指定的anchorpeers失败了，是否能动态的重新设置，如果不行，相当于anchor hostname是写死了；还有其他一些hostname的配置。我觉得这些在p2p这种架构里应该是支持的
baohua (Tue, 25 Apr 2017 01:29:23 GMT):
嗯 目前是在配置里的 可以指定一组多个
baohua (Tue, 25 Apr 2017 01:29:52 GMT):
常见 p2p 网络的做法 也是 提前给定+探测
zhangchao (Tue, 25 Apr 2017 01:34:46 GMT):
bluemix上的blockchain是最新的fabric吗
yp (Tue, 25 Apr 2017 02:04:41 GMT):
@jimthematrix node sdk 支持6.10.2版本么？还是只支持6.9.x？
baohua (Tue, 25 Apr 2017 03:00:07 GMT):
bmx 上目前仅支持 fabric v0.6 版本
jimthematrix (Tue, 25 Apr 2017 03:30:24 GMT):
@yp 还没有测试过，估计应该可以的
yp (Tue, 25 Apr 2017 03:34:29 GMT):
嗯，我正在测试，现在6.X上的最新版是6.10了
jimthematrix (Tue, 25 Apr 2017 03:34:35 GMT):
@baohua anchor peer和org leader是两个不同角色，但很容易混淆（`- CORE_PEER_GOSSIP_ORGLEADER=true`），org leader直接跟orderer获取block，anchor peer作为org的代表负责跟其他org通讯。
jimthematrix (Tue, 25 Apr 2017 03:35:33 GMT):
两个角色可以同时设置在一个peer上，也可以放在不同peer上
yp (Tue, 25 Apr 2017 03:38:29 GMT):
CORE_PEER_GOSSIP_ORGLEADER一般不建议使用的吧，要使用CORE_PEER_GOSSIP_USELEADERELECTION的
yp (Tue, 25 Apr 2017 03:38:57 GMT):
刚去看了下代码，peer目录中的core.yaml去哪了。。。
baohua (Tue, 25 Apr 2017 03:53:41 GMT):
@jimthematrix :thumbsup: org 之间的通讯是哪些场景 我理解一般情况下 一个 org 会分一个 channel。
baohua (Tue, 25 Apr 2017 03:55:07 GMT):
@yp sampleconfig/core.yaml
xixuejia (Tue, 25 Apr 2017 05:02:15 GMT):
新的org加入到已有的网络中同步block应该是从其他org的anchor peer上同步对吧?
xixuejia (Tue, 25 Apr 2017 05:03:40 GMT):
还是说orderer会保留所有的历史block呢?这样也可以通过orderer同步
zhangchao (Tue, 25 Apr 2017 05:34:27 GMT):
应该是anchor peer，这样最能保证数据的公正性
zzying (Tue, 25 Apr 2017 06:19:41 GMT):
Has joined the channel.
yp (Tue, 25 Apr 2017 08:00:18 GMT):
@jimthematrix 如何打开node sdk的logger lever ，比如debug
yp (Tue, 25 Apr 2017 08:06:49 GMT):
找到了～～HFC_LOGGING='{"debug": "console"}'
yong (Tue, 25 Apr 2017 08:31:10 GMT):
@jimthematrix 谢谢.
yong (Tue, 25 Apr 2017 08:34:27 GMT):
现在hyperledger ECDSA算法是不是只能支持ecdsa-256，不能支持ecdsa-384/512等？在fabric-ca-server-config.yaml中增加 algo：ecdsa size: 384。不起作用
yong (Tue, 25 Apr 2017 08:55:50 GMT):
文档上说是支持的
jimthematrix (Tue, 25 Apr 2017 11:55:52 GMT):
@yong 这是在BCCSP层设置的，peer上的见core.yaml->peer/BCCSP，orderer上的见orderer.yaml->general/BCCSP
jimthematrix (Tue, 25 Apr 2017 11:57:35 GMT):
fabric-ca的设置是独立的，用不同算法签名的数字证书都可以在peer和orderer中应用
jimthematrix (Tue, 25 Apr 2017 11:59:28 GMT):
node SDK也支持不同的ECDSA算法设置（暂时不支持RSA），Client.js->setConfigSetting(): crypto-keysize, crypto-hash-algo
jimthematrix (Tue, 25 Apr 2017 12:00:25 GMT):
注意hash设置要跟security strength对应
baohua (Wed, 26 Apr 2017 01:56:02 GMT):
Meeting will begin in 5 mins https://wiki.hyperledger.org/groups/twgc/meeting/2017-04-26 [微笑]
zerppen (Wed, 26 Apr 2017 02:39:38 GMT):
@liqilei 在吗
yahtoo (Wed, 26 Apr 2017 02:51:43 GMT):
@baohua 你好，工作组微信群是多少？
leungjob (Wed, 26 Apr 2017 03:49:10 GMT):
请问微信公众号是什么？谢谢！
baohua (Wed, 26 Apr 2017 04:02:12 GMT):
@scott-long
baohua (Wed, 26 Apr 2017 04:02:28 GMT):
scott 帮忙贴下公众号 thanks
CarlXK (Wed, 26 Apr 2017 07:27:06 GMT):
Message Attachments
CarlXK (Wed, 26 Apr 2017 07:29:22 GMT):
@here 这里私密保护 用SDK来实现的时候, Ca注册的User 私钥和公钥是SDK本地生成的, 每次enroll后enrollment里面的publickey和privatekey会变, 如果重新enroll就会发生变化, 那以前加密了的数据就解不开了
CarlXK (Wed, 26 Apr 2017 07:29:39 GMT):
这里应该怎么解决?
zerppen (Wed, 26 Apr 2017 07:30:17 GMT):
同一个user enroll后就已经记录了
zerppen (Wed, 26 Apr 2017 07:30:29 GMT):
会直接取
yp (Wed, 26 Apr 2017 07:32:22 GMT):
不是sdk本地生成的，是ca生成，记录在数据库的，enroll的时候直接从数据库拉回sdk
yp (Wed, 26 Apr 2017 07:33:25 GMT):
你这个图。。。貌似和现在的ca，fabric1.0 不太吻合。。
zerppen (Wed, 26 Apr 2017 07:34:11 GMT):
这个是0.6的吧 当时是用本地KV文件存储已经enroll的用户
CarlXK (Wed, 26 Apr 2017 07:34:35 GMT):
我看了javasdk代码, enroll的时候sdk生成的keypair
yp (Wed, 26 Apr 2017 07:34:43 GMT):
哦，0.6 明确说了e cert是one time password
CarlXK (Wed, 26 Apr 2017 07:35:14 GMT):
这个是http://v.youku.com/v_show/id_XMjcwNzY1ODgyNA==.html?from=s1.8-1-1.2&spm=a2h0k.8191407.0.0
CarlXK (Wed, 26 Apr 2017 07:35:21 GMT):
ibm刚开的讲座里面讲的
CarlXK (Wed, 26 Apr 2017 07:35:56 GMT):
我们也在实现, 跟这个方式类似, 但公私钥对是自己生成的, 想着要是能用ca用户的不就更好嘛, 也方便接入监管
yp (Wed, 26 Apr 2017 07:36:45 GMT):
现在的ca支持多root ca的，你们自己生成也可以的
CarlXK (Wed, 26 Apr 2017 07:37:09 GMT):
自己生成的其实没哈问题, 但是不好接入监管
CarlXK (Wed, 26 Apr 2017 07:37:25 GMT):
ca 生成的是可以方便接入监管的
CarlXK (Wed, 26 Apr 2017 07:39:24 GMT):
我看的是javasdk的代码, 我在看看node的吧
grapebaba (Wed, 26 Apr 2017 07:40:56 GMT):
这个是做数字签名的，不是加密
CarlXK (Wed, 26 Apr 2017 07:41:50 GMT):
那做加密的应该是ca生成的, 没返回给客户端?
grapebaba (Wed, 26 Apr 2017 07:42:38 GMT):
没看到ca有加密
grapebaba (Wed, 26 Apr 2017 07:42:48 GMT):
但是正常会开启TLS
CarlXK (Wed, 26 Apr 2017 07:43:06 GMT):
不是说有两对密钥对, 一对是签名的一对是加密的么
CarlXK (Wed, 26 Apr 2017 07:43:35 GMT):
TLS是传输层, 跟这个还没关系
grapebaba (Wed, 26 Apr 2017 07:44:19 GMT):
原来好像是有两对，现在没有看到
CarlXK (Wed, 26 Apr 2017 07:45:09 GMT):
public interface Enrollment {
/**
* Key is the user's private key
* @return private key.
*/
public PrivateKey getKey();
/**
* Certificate is the users signed certificate.
* @return
*/
public String getCert();
/**
* The users public key.
* @return
*/
public String getPublicKey();
}
CarlXK (Wed, 26 Apr 2017 07:45:30 GMT):
privatekey和public应该是加密的, cert是签名的吧
CarlXK (Wed, 26 Apr 2017 07:46:29 GMT):
可是每次enroll或者reenroll后这个privatekey 和publickey都在变, 这就蛋疼了啊
grapebaba (Wed, 26 Apr 2017 07:47:45 GMT):
public key发给CA，就变成了cert
grapebaba (Wed, 26 Apr 2017 07:48:29 GMT):
有了cert你还enroll干什么
CarlXK (Wed, 26 Apr 2017 07:49:53 GMT):
假如丢了呢
CarlXK (Wed, 26 Apr 2017 07:50:35 GMT):
还有这玩意是有有效期的
yp (Wed, 26 Apr 2017 08:02:58 GMT):
1. client和ca server会建立tls安全通道来传输私钥和证书
yp (Wed, 26 Apr 2017 08:03:26 GMT):
2. 第一次enroll后，再次enroll，私钥和证书都不会变的
CarlXK (Wed, 26 Apr 2017 08:07:01 GMT):
我试了, 会变... alpha版本
CarlXK (Wed, 26 Apr 2017 08:07:01 GMT):
我也觉得不会, 但是无论看代码还是急于sdk的实验都是会变的
CarlXK (Wed, 26 Apr 2017 08:14:36 GMT):
@jimthematrix 现在每次enroll后publickey privatekey 都会变, 这个后面会改么 还是说fabric就是这么设计(基于什么考虑)
zerppen (Wed, 26 Apr 2017 08:18:43 GMT):
@yp 翻了一下javaSDK 0.6,你的程序跑的过程中会记录你所有注册的用户，有kv 文件记录（可选），如果再次enroll就直接拿证书了。
yp (Wed, 26 Apr 2017 08:19:59 GMT):
@CarlXK 我刚看了下，key和cert确实会变
zerppen (Wed, 26 Apr 2017 08:20:16 GMT):
不过文档说了 是一次性的
yp (Wed, 26 Apr 2017 08:24:39 GMT):
@CarlXK @zerppen authority_key_identifier是不会变的
yp (Wed, 26 Apr 2017 08:25:26 GMT):
也就是说你的key变了，但是你的身份信息没变
zerppen (Wed, 26 Apr 2017 08:26:41 GMT):
你的意思是user可以有多个名字？
CarlXK (Wed, 26 Apr 2017 08:27:08 GMT):
authority_key_identifier 这个是在哪里的, 我没找到
CarlXK (Wed, 26 Apr 2017 08:27:22 GMT):
难道是CA里面的
yp (Wed, 26 Apr 2017 08:30:15 GMT):
Message Attachments
CarlXK (Wed, 26 Apr 2017 08:38:56 GMT):
ca的数据库里面的么
yp (Wed, 26 Apr 2017 08:58:53 GMT):
ca服务器确实不维护用户key，确实会变
zhangchao (Wed, 26 Apr 2017 09:31:24 GMT):
修改了chaincode里面的invoke接口后，怎么更改proto？这个proto在哪里存放
yp (Wed, 26 Apr 2017 09:35:26 GMT):
make protos
zhangchao (Wed, 26 Apr 2017 09:41:14 GMT):
源文件存在哪里
yp (Wed, 26 Apr 2017 09:50:18 GMT):
现在的ca里面好像是没有加密的密钥对
yong (Wed, 26 Apr 2017 11:09:20 GMT):
@jimthematrix 能这样理解吗？假如我要整个系统都使用ecdsa-384算法，我需要对peer上的见core.yaml->peer/BCCSP，orderer上的见orderer.yaml->general/BCCSP。还要让fabric-ca生成ecdsa-384的证书，需要对fabric-ca-server-config.yaml和fabric-ca-client-config.yaml中的csr增加key.algo = ecdsa key.size=384和hash=384。是吗？ 但我修改了fabric-ca-server-config.yaml和fabric-ca-client-config.yaml，打印输出依然为ecdsa-256。
baohua (Wed, 26 Apr 2017 11:15:00 GMT):
tcert 现在没有实现
yong (Wed, 26 Apr 2017 11:16:40 GMT):
另外，我通过fabric-ca生成orderer的证书，但是fabric-ca好像不支持orderer类型的用户注册。我有个疑问，orderer如果仅仅做共识，交易排序，是否需要有证书？但orderer镜像中有相应的orderer证书和私钥？
yong (Wed, 26 Apr 2017 11:17:04 GMT):
@baohua 谢谢
yong (Wed, 26 Apr 2017 11:17:58 GMT):
我怎么注册一个orderer用户（当然是否需要注册orderer）?
jimthematrix (Wed, 26 Apr 2017 12:18:30 GMT):
@CarlXK fabric 1.0不提供加密，fabric-ca的责任是身份认证，针对用户自己生成的公钥进行签名，每个用户的公钥对主要是为了代表身份，如果用来加密会比较麻烦，必须要考虑很多因素，通常加密是用对称密钥，然后再用公钥对对称密钥进行加密，所以当公钥快过期了，就要对数据重新加密，可是这对ledger上的数据不适用。所以blockchain上的加密最好的办法就是在存储层（比如文件系统），在应用层加密是很难实现的
jimthematrix (Wed, 26 Apr 2017 12:18:30 GMT):
@CarlXK fabric 1.0不提供加密，fabric-ca的责任是身份认证，针对用户自己生成的公钥进行签名，每个用户的公钥对主要是为了代表身份，如果用来加密会比较麻烦，必须要考虑很多因素，通常加密是用对称密钥，然后再用公钥对对称密钥进行加密，所以当公钥快过期了，就要对数据重新加密，可是这对ledger上的数据不适用。所以blockchain上的加密最好的办法就是在存储层（比如文件系统），在应用层加密是很难实现的。特别是v1.0通过channel把数据完全隔离开，某个成员如果不在channel里就完全没有这个数据，所以应用层的加密也基本没有必要了
jimthematrix (Wed, 26 Apr 2017 12:19:18 GMT):
@zerppen @yp @grapebaba ^^^
CarlXK (Wed, 26 Apr 2017 12:29:35 GMT):
@jimthematrix 谢谢解答 :joy: 现在就是有场景需要用到账本内加密, 我们自己生成了公私钥对 没有用ca 用户的
jimthematrix (Wed, 26 Apr 2017 12:38:50 GMT):
@CarlXK 公钥本身并不过期，只是数字证书会过期，对账本加密，要么只用对称加密，要么公钥加密+对称加密（公钥加密密钥），需要保存公钥私钥密钥
xixuejia (Wed, 26 Apr 2017 13:03:32 GMT):
@jimthematrix Hi Jim, 现在是SDK生成公私钥然后把公钥发给fabric-ca签名吗? tcert也会是这种方式生成吗? fabric-ca如何做到同一个用户的多个tcert之间的关联性用于审计呢?
CarlXK (Wed, 26 Apr 2017 13:04:37 GMT):
@jimthematrix 如果重新enroll或者reenroll的时候不带有原来的Enrollment信息就会生成新的keypair, 如果这个enrollment丢了就会很麻烦
jimthematrix (Wed, 26 Apr 2017 13:24:03 GMT):
@CarlXK 对的，所以我上面的意思是不要把用于加密的公钥对绑定在用针对身份的enrollment上，两个公钥对分开就可以了，用于加密的公钥对自己生成（CryptoSuite-》generateKey（）），不需要fabric-ca签名
jimthematrix (Wed, 26 Apr 2017 13:24:03 GMT):
@CarlXK 对的，所以我上面的意思是不要把用于加密的公钥对绑定在用针对身份的enrollment上，两个公钥对分开就可以了，用于加密的公钥对自己分开生成（openssl或者CryptoSuite-》generateKey（）），不需要fabric-ca签名
jimthematrix (Wed, 26 Apr 2017 13:24:03 GMT):
@CarlXK 对的，所以我上面的意思是不要把用于加密的公钥对绑定在用针对身份的enrollment上，两个公钥对分开就可以了，用于加密的公钥对自己分开生成（openssl或者CryptoSuite -> generateKey()），不需要fabric-ca签名
yp (Thu, 27 Apr 2017 01:02:29 GMT):
@yong 注册ca里面的role type是字符串，你可以自己添加一个orderer的
yp (Thu, 27 Apr 2017 01:04:05 GMT):
@yong [ ](https://chat.hyperledger.org/channel/fabric-ca?msg=Tjok7fgn3SJXBZ9mt)
yong (Thu, 27 Apr 2017 01:18:19 GMT):
@yp 谢谢，试过了。可以生成orderer用户
CarlXK (Thu, 27 Apr 2017 01:37:34 GMT):
@jimthematrix 明白了, 已经是这么做的了, 谢谢!
yp (Thu, 27 Apr 2017 01:46:25 GMT):
@jimthematrix @CarlXK 关于加密的时机和处所有个疑问：加密的密钥对应该是在智能合约里对交易数据加密，然后存储。这样理解有问题么
CarlXK (Thu, 27 Apr 2017 01:48:48 GMT):
是的, 密钥对生成是在sdk层(生成用户的时候就给这个用户发一个密钥对), 加密是在合约代码中, 拿到有权限各方的公钥 加密数据 和对称密钥, 然后在存储 加密数据和钥匙的列表
CarlXK (Thu, 27 Apr 2017 01:48:57 GMT):
@yp
yp (Thu, 27 Apr 2017 01:49:52 GMT):
嗯，想了下，也只有在chaincode这一个地方才能对存储加密了
CarlXK (Thu, 27 Apr 2017 01:52:03 GMT):
最好还是用账本隔离来分离数据权限, 我们这个是没有办法, 初始的时候可能是n方, 后续可能有别的方加入, 加入方还要看到部分跟他有关联的数据
CarlXK (Thu, 27 Apr 2017 01:53:26 GMT):
sdk层也可以进行加密然后传给cc存储, 但是这样不太好, 离开了sdk就不能用cli来进行调用了
zhangchao (Thu, 27 Apr 2017 03:31:44 GMT):
@CarlXK 你说的是什么场景下，需要对加密存储？
CarlXK (Thu, 27 Apr 2017 03:35:21 GMT):
A B C三方建立了一个链, 发生交易(1....n) , 后续银行(D E)会加入, 银行D E 会各自跟现有的交易(D--1...m E--m+1....n)发生关系, 不能让银行D看到 E--m+1...n 的交易
CarlXK (Thu, 27 Apr 2017 03:36:28 GMT):
就是这样的场景, 银行作为超强势方要加入到链并看到原始交易记录
zhangchao (Thu, 27 Apr 2017 03:39:01 GMT):
这个应该是靠以后的TCERT来解决的吧
zhangchao (Thu, 27 Apr 2017 03:39:18 GMT):
我感觉上层应用来做比较费劲
CarlXK (Thu, 27 Apr 2017 03:39:21 GMT):
tcert不能解决这个问题
CarlXK (Thu, 27 Apr 2017 03:39:33 GMT):
tcert也不是干这个事情的
zhangchao (Thu, 27 Apr 2017 03:39:56 GMT):
tcert可以保证privacy的
CarlXK (Thu, 27 Apr 2017 03:40:58 GMT):
那是保证交易方的隐私, 并不能保证数据的隐私, 我的数据里面会带有真实交易方的信息
zhangchao (Thu, 27 Apr 2017 03:41:06 GMT):
能解决个unlinkable，完全加密做不到
CarlXK (Thu, 27 Apr 2017 03:41:45 GMT):
对, 只要在链上的各方都完全拥有这些数据
zhangchao (Thu, 27 Apr 2017 03:41:56 GMT):
加密了得话，感觉不太适合用开放账本来实现
CarlXK (Thu, 27 Apr 2017 03:42:55 GMT):
没什么适合不适合吧
zhangchao (Thu, 27 Apr 2017 03:47:45 GMT):
transaction是在账本中记录的，你的密钥会作为参数传进chaincode，密钥的维护成本很高啊
CarlXK (Thu, 27 Apr 2017 03:49:41 GMT):
现在我对跨链的调用比较疑惑
CarlXK (Thu, 27 Apr 2017 03:51:57 GMT):
@jimthematrix
InvokeChaincode(chaincodeName string, args [][]byte, channel string) pb.Response
关于跨账本跨CC的调用, 栗子如下:
ABC各有一个Peer, 在Ledger1上使用CC1, DE各有一个Peer,在Ledger2上使用CC2
如果要在Peer(D) 跨链调用CC2(Ledger2) -> CC1(Ledger1), 可是Peer(D)上并没有安装CC1(可以安装)以及并没有Ledger1, 调用不了
如果Peer(D)加入了Ledger1, 那就不能起到账本数据隔离的目的了
这么理解有问题么?
zerppen (Thu, 27 Apr 2017 04:07:54 GMT):
挺疑惑的 生产环境都用的sdk cli就用来快速测试一下
zerppen (Thu, 27 Apr 2017 04:08:02 GMT):
@CarlXK
CarlXK (Thu, 27 Apr 2017 04:10:25 GMT):
如果要提供出去, 最好还是无论sdk和cli都能调用
CarlXK (Thu, 27 Apr 2017 04:10:37 GMT):
给第三方的时候
ansonlau3 (Thu, 27 Apr 2017 06:42:58 GMT):
Has joined the channel.
jimthematrix (Thu, 27 Apr 2017 13:54:57 GMT):
@CarlXK 跨链调用的前提是被调用的CC也处在调用方参与的链上，所以你上面的例子Peer(D)没有权限调用CC
jimthematrix (Thu, 27 Apr 2017 13:54:57 GMT):
@CarlXK 跨链调用的前提是被调用的CC也处在调用方参与的链上，所以你上面的例子Peer(D)没有权限调用CC1
Herbert.Soon (Fri, 28 Apr 2017 01:35:59 GMT):
Has joined the channel.
CarlXK (Fri, 28 Apr 2017 01:57:45 GMT):
@jimthematrix 那就是如果Peer(D) 也加入了ledger1, 就有权限调用了对么
jimthematrix (Fri, 28 Apr 2017 02:14:44 GMT):
对的
grapebaba (Fri, 28 Apr 2017 02:34:44 GMT):
@jimthematrix install chaincode的proposal里面channel header是不是不包含channel id
CarlXK (Fri, 28 Apr 2017 02:37:16 GMT):
@jimthematrix 好的, 谢谢!
jimthematrix (Fri, 28 Apr 2017 02:37:39 GMT):
@grapebaba it's set to an empty string
CarlXK (Fri, 28 Apr 2017 02:38:19 GMT):
其实链内(外)交易授权查看这个需求场景应该挺多的, 现在的fabric是根本就没考虑
grapebaba (Fri, 28 Apr 2017 02:40:16 GMT):
我把这个发给orderer的时候，orderer报错 2017-04-28 02:27:17.069 UTC [orderer/common/broadcast] Handle -> WARN 008 Rejecting broadcast because channel was not found
grapebaba (Fri, 28 Apr 2017 02:41:56 GMT):
node SDK这个是怎么处理的？
grapebaba (Fri, 28 Apr 2017 02:44:06 GMT):
还是说install不用写乐得个人
grapebaba (Fri, 28 Apr 2017 02:44:06 GMT):
还是说install不用写ledger
grapebaba (Fri, 28 Apr 2017 02:48:24 GMT):
看起来是不需要，没有channel就等于没有账本
jimthematrix (Fri, 28 Apr 2017 02:54:04 GMT):
@grapebaba that's right. install only targets the peers, it's not a transaction so it doesn't need to get sent to the orderer or recorded in the ledger
grapebaba (Fri, 28 Apr 2017 02:59:04 GMT):
:ok_hand:
wsh_bob (Fri, 28 Apr 2017 07:59:06 GMT):
Has joined the channel.
little51 (Fri, 28 Apr 2017 08:40:03 GMT):
Has joined the channel.
jimthematrix (Fri, 28 Apr 2017 13:57:32 GMT):
@CarlXK _其实链内(外)交易授权查看_ - 能具体描述一下场景和相关的需求吗？如果链A里的CC1需要调用链B的CC2，而这个交易的提交者却不在链B，是什么样的场景需要这样的调用呢？
jimthematrix (Fri, 28 Apr 2017 13:57:32 GMT):
@CarlXK _*“其实链内(外)交易授权查看”*_ - 能具体描述一下场景和相关的需求吗？如果链A里的CC1需要调用链B的CC2，而这个交易的提交者却不在链B，是什么样的场景需要这样的调用呢？
yp (Tue, 02 May 2017 07:38:15 GMT):
fabric加了撤销列表crl？
yong (Tue, 02 May 2017 08:17:42 GMT):
执行peer channel create -o orderer0:7050 -c $CHANNEL_NAME -f /etc/hyperledger/orderer/channel.tx
出现Error: Got unexpected status: BAD_REQUEST错误。在orderer节点出现
orderer0 | 2017-05-02 08:16:04.635 UTC [orderer/common/broadcast] Handle -> WARN 179 Rejecting broadcast message because of filter error: Rejected by rule: *sigfilter.sigFilter
orderer0 | 2017-05-02 08:16:04.637 UTC [orderer/common/deliver] Handle -> WARN 17a Error reading from stream: stream error: code = 1 desc = "context canceled"。
yong (Tue, 02 May 2017 08:17:49 GMT):
大家知道是什么原因吗？
zerppen (Tue, 02 May 2017 08:18:15 GMT):
@jimthematrix 准备测试一下 javaCC，发现maven中心仓库没有shim-client.jar
zerppen (Tue, 02 May 2017 08:19:33 GMT):
是仓库地址改了吗？ 我在这看的 '''
zerppen (Tue, 02 May 2017 08:19:38 GMT):
https://repo1.maven.org/maven2/org/hyperledger/
zerppen (Tue, 02 May 2017 08:19:38 GMT):
'https://repo1.maven.org/maven2/org/hyperledger/'
yong (Tue, 02 May 2017 08:32:03 GMT):
@yp 遇到过 WARN 179 Rejecting broadcast message because of filter error: Rejected by rule: *sigfilter.sigFilter 之类的错误没有？
yp (Tue, 02 May 2017 08:32:49 GMT):
你用了分层ca么？
yong (Tue, 02 May 2017 08:40:12 GMT):
没有啊
yong (Tue, 02 May 2017 08:40:56 GMT):
你说的分层CA是指多级CA吗？
yp (Tue, 02 May 2017 08:53:05 GMT):
嗯
yp (Tue, 02 May 2017 08:56:00 GMT):
我之前没设置intermediatecerts的时候，碰到过sigfilter的错误，设置了就好了，没有细追
yong (Tue, 02 May 2017 10:12:10 GMT):
@yp 是我使用fabric-ca生成的证书导致。使用fabric/e2e_cli的证书就可以。
yong (Tue, 02 May 2017 10:13:35 GMT):
@jimthematrix 我使用fabric-ca生成的证书和私钥，在进行执行peer channel create -o orderer0:7050 -c $CHANNEL_NAME -f /etc/hyperledger/orderer/channel.tx
出现Error: Got unexpected status: BAD_REQUEST错误。在orderer节点出现
orderer0 | 2017-05-02 08:16:04.635 UTC [orderer/common/broadcast] Handle -> WARN 179 Rejecting broadcast message because of filter error: Rejected by rule: *sigfilter.sigFilter
orderer0 | 2017-05-02 08:16:04.637 UTC [orderer/common/deliver] Handle -> WARN 17a Error reading from stream: stream error: code = 1 desc = "context canceled"。
yong (Tue, 02 May 2017 10:13:52 GMT):
怎么解决啦？
yong (Wed, 03 May 2017 01:56:12 GMT):
@yp 你是用的是fabric-ca生成的证书还是原来fabric自带的证书？
yp (Wed, 03 May 2017 01:57:27 GMT):
@yong 自己用ca做的证书。
yong (Wed, 03 May 2017 01:57:59 GMT):
是自己的ca还是fabric-ca？
yp (Wed, 03 May 2017 01:58:26 GMT):
你那个问题我碰到过，就是加了intermediatecerts后就没有报错过了。。但由于报错后改了很多东西，我也不确定是否就只是因为intermediatecerts的原因
yp (Wed, 03 May 2017 01:58:30 GMT):
fabric-ca
yong (Wed, 03 May 2017 01:59:21 GMT):
之前一直怀疑是证书的问题，我把intermediatecerts加上试试。
JasonD (Wed, 03 May 2017 02:12:03 GMT):
有个疑惑，leveldb数据是KV保存的，那么跟block的联系在哪里呢？是把KV的变更就放在block里保存，实际的getstate putstate都是通过KV，不交互到block？
zerppen (Wed, 03 May 2017 02:14:26 GMT):
@jimthematrix 你好，张。昨晚测试javaCC的时候发现现有的配置有些问题（找依赖很困难），跟sanchezl讨论后，他说chaincode还会变，我看到gerrit上他提交过的代码了，和现有的相比改动还挺大的。我的问题是，fabric的chaincode接口是不是也会改动？如果改动，改动会不会比较大？
zerppen (Wed, 03 May 2017 02:14:26 GMT):
@jimthematrix 你好，张。昨晚测试javaCC的时候发现现有的配置有些问题（找依赖很困难），跟sanchezl讨论后，他说chaincode还会变，我看到他改动后的chaincode代码了，和现有的相比改动还挺大的。我的问题是，fabric的chaincode接口是不是也会改动？如果改动，改动会不会比较大？
jimthematrix (Wed, 03 May 2017 02:19:45 GMT):
@zerppen 1.0 java SDK 还没有发布到maven
zerppen (Wed, 03 May 2017 02:21:32 GMT):
shim-client 也没有吧
zerppen (Wed, 03 May 2017 02:21:39 GMT):
java的
zerppen (Wed, 03 May 2017 02:24:17 GMT):
或者说现在的example02的 gradle配置文件有问题，它默认去maven仓库找依赖
jimthematrix (Wed, 03 May 2017 02:24:35 GMT):
@JasonD state的原始数据都在block的writeset里，KV数据库只是个帮助chaincode读写以及支持query的cache
jimthematrix (Wed, 03 May 2017 02:26:21 GMT):
@zerppen sanchezl的java shim上的改动只是让接口跟fabric chaincode匹配，fabric chaincode shim本身不会怎么变了
zerppen (Wed, 03 May 2017 02:27:33 GMT):
好的。那帮忙看看他的提交，让最新的能够java shim能够早点merge出来吧
jimthematrix (Wed, 03 May 2017 02:28:05 GMT):
今天merge了四个:slight_smile:
yong (Wed, 03 May 2017 02:29:07 GMT):
@yp 能回忆下改了那些地方吗？
JasonD (Wed, 03 May 2017 02:41:38 GMT):
@jimthematrix 所以，state都是存在block里，KV是cache，get history 也是从KV取的？
jimthematrix (Wed, 03 May 2017 02:56:16 GMT):
@JasonD https://jira.hyperledger.org/secure/attachment/10689/HL-Fabric-Deep-Dive-20170424.pdf， 第六页，history是在另外一个“history db”里面维护的，目前只有leveldb的实现
jimthematrix (Wed, 03 May 2017 02:57:13 GMT):
“state db”可以是leveldb或者couchdb
JasonD (Wed, 03 May 2017 03:20:18 GMT):
@jimthematrix thanks
yp (Wed, 03 May 2017 05:43:09 GMT):
@jimthematrix sdk中install cc需要Admin权限的user，这个user该如何向ca申请？还是将普通用户的cert放到admincerts文件夹中，该用户就具有admin权限了？
JasonD (Wed, 03 May 2017 06:36:53 GMT):
数据保存在block，KV里是加密过的吗？如果是，怎么加密的？因为该channel可能有多个member，又会有新增的member，加密机制是怎么样的？
zhangchao (Wed, 03 May 2017 06:42:01 GMT):
应该不会加密
CarlXK (Wed, 03 May 2017 06:44:31 GMT):
[ ](https://chat.hyperledger.org/channel/twg-china?msg=WXq4aZfnG5hTkLdq2) @jimthematrix 如果链A里的CC1需要调用链B的CC2
链A CC1, 参与方 企业1 企业2 供应商1 供应商2, 交叉发生了n笔交易
链B CC2, 参与方为 供应商1 银行1 用途为供应商使用应收账款向银行发起融资申请
1. 供应商1 需要向 银行1 发起融资申请
2.银行想要看到供应商1与企业之间的交易明细(直接跨链方式), 但是银行1不能参与到链A中, 因为链A上只有一些交易跟银行1相关
所以在这种情况下, 希望供应商1可以通过链外授权的方式把这些交易查看权限授权给银行1, 可以通过跨链授权调用完成
当前的解决方案是, 都在同一个链内, 链内交易数据加密, 银行加入后可以看到哪些通过链内加密授权
zerppen (Wed, 03 May 2017 06:53:23 GMT):
因为实际生产中，比如我举个交易所的例子，产生的数据基本都是关系型的。在0.6中，因为chaincode提供了table的形式，虽然不支持SQL，而且查询的时候也比较麻烦，但至少我存数据的时候挺方便的。但是目前的chaincode的来看，存的时候会比较麻烦，当然也可能是我存的方式不对。有什么好的方法推荐吗？ @here
zhangchao (Wed, 03 May 2017 06:55:33 GMT):
不是有couchdb可以用吗
zerppen (Wed, 03 May 2017 06:59:57 GMT):
比如我交易所操作里面有 创建币/分发/账户等，这都是根据业务场景来分类的 chaincode只存kv，我现在的实现是将k作为特定操作
zerppen (Wed, 03 May 2017 07:00:10 GMT):
v存的是一大串数据
zerppen (Wed, 03 May 2017 07:00:33 GMT):
@zhangchao 你具体怎样用的呢
CarlXK (Wed, 03 May 2017 07:03:57 GMT):
key, 比如User:001, 这样吧
zerppen (Wed, 03 May 2017 07:04:13 GMT):
不是啊
zerppen (Wed, 03 May 2017 07:04:25 GMT):
这样的逻辑根本不存在于生产环境
CarlXK (Wed, 03 May 2017 07:05:19 GMT):
以前是有表名 id, 现在是表名加id 作为key存储呗
zerppen (Wed, 03 May 2017 07:05:31 GMT):
我是这样实现的
CarlXK (Wed, 03 May 2017 07:05:32 GMT):
为什么不存在
zerppen (Wed, 03 May 2017 07:06:51 GMT):
但是我总感觉有更好的方法 因为这样实现起来的时候，比如我要做一笔交易 a跟b互换一次，需要删除掉这个k再put一次
CarlXK (Wed, 03 May 2017 07:07:26 GMT):
删除key? 为什么要删除
zerppen (Wed, 03 May 2017 07:07:36 GMT):
0.6里面有insert和replace
CarlXK (Wed, 03 May 2017 07:07:57 GMT):
couchdb是直接带有数据的版本号的, put后就是一个新的数据版本
zerppen (Wed, 03 May 2017 07:08:16 GMT):
就是说，可以直接put进去吧
CarlXK (Wed, 03 May 2017 07:08:21 GMT):
是
zerppen (Wed, 03 May 2017 07:08:26 GMT):
虽然前面有了这个k了
zerppen (Wed, 03 May 2017 07:08:28 GMT):
好的
zhangchao (Wed, 03 May 2017 07:08:57 GMT):
有history记录，put进去后历史数据依然可以取到
zhangchao (Wed, 03 May 2017 07:09:30 GMT):
复杂点的记录就用compositeKey来存储
zerppen (Wed, 03 May 2017 07:09:32 GMT):
这个我知道，
zerppen (Wed, 03 May 2017 07:10:03 GMT):
javaCC的这个实现还在review阶段
CarlXK (Wed, 03 May 2017 07:10:23 GMT):
用go cc吧, 其实写起来也简单
CarlXK (Wed, 03 May 2017 07:10:35 GMT):
照着抄就是了, 不算麻烦
zerppen (Wed, 03 May 2017 07:10:50 GMT):
我们go和java都写
zerppen (Wed, 03 May 2017 07:11:08 GMT):
我只负责java
CarlXK (Wed, 03 May 2017 07:11:19 GMT):
javacc还是先别玩吧, java sdk没问题了
zhangchao (Wed, 03 May 2017 07:11:23 GMT):
还是用go吧，java cc还没做好
CarlXK (Wed, 03 May 2017 07:12:30 GMT):
配置channel的configtx工具这个有谁理解的比较清楚, 可以给讲讲不 @here
zerppen (Wed, 03 May 2017 07:13:06 GMT):
javaSDK现在和javaCC分离了
zerppen (Wed, 03 May 2017 07:13:46 GMT):
上月刚分离的
zhangchao (Wed, 03 May 2017 07:15:04 GMT):
sanchezl有没有说java cc何时ready
zerppen (Wed, 03 May 2017 07:15:26 GMT):
等fabric ready了吧
zerppen (Wed, 03 May 2017 07:15:44 GMT):
他现在写的差不多跟fabric CC一样了
zhangchao (Wed, 03 May 2017 07:16:05 GMT):
那就到GA了，不能等到那个时候了，就用GO搞吧
zerppen (Wed, 03 May 2017 07:16:09 GMT):
只是还在审核中，我看他写的几个例子也都有改动
zerppen (Wed, 03 May 2017 07:17:17 GMT):
等审核出来了，我再改一下我的CC试试，希望能够用上吧
zerppen (Wed, 03 May 2017 07:18:17 GMT):
只是现在javaSDK不能用，只支持go CC
zhangchao (Wed, 03 May 2017 07:20:20 GMT):
javasdk不能用？
zerppen (Wed, 03 May 2017 07:25:16 GMT):
不能跑javaCC
zerppen (Wed, 03 May 2017 07:25:44 GMT):
0.6可以 现在的版本不支持
zerppen (Wed, 03 May 2017 07:26:40 GMT):
之前我有看过，它引用的一个class文件里写死了，chaincode_languge = GO
zerppen (Wed, 03 May 2017 07:28:20 GMT):
compositeKey也不能满足需求啊，还不如直接 kv，v做出jsonArray或者hashmap，里面当做个小型数据库
zerppen (Wed, 03 May 2017 07:30:46 GMT):
比如我账户信息，里面有多个账户id吧，有总额（发行时的）/余额/时间戳/创建者等一系列信息。这都是对应起来的典型关系型数据
zhangchao (Wed, 03 May 2017 07:31:34 GMT):
用rich query也不行？
zerppen (Wed, 03 May 2017 07:33:20 GMT):
不太懂 rich query
zerppen (Wed, 03 May 2017 07:34:00 GMT):
对了，如果已经有了一个 kv，我再put 相同的k，我get的时候默认是get到最新的k对应的v吧
zhangchao (Wed, 03 May 2017 07:36:19 GMT):
有点类似于sql的查询
zhangchao (Wed, 03 May 2017 07:36:31 GMT):
基本满足应用的需要了
zerppen (Wed, 03 May 2017 07:37:22 GMT):
我现在的实现已经满足需要了，只是因为感觉业务一多，会影响效率
zerppen (Wed, 03 May 2017 07:39:02 GMT):
就像0.6一样，虽然给的是table，但其里面的实现也是用的kv。而我现在是自己去包这一层
zerppen (Wed, 03 May 2017 08:00:44 GMT):
@CarlXK http://wutongtree.github.io/translations/getting_started 我司整理的一些原创文档，希望你那边能打开
baohua (Wed, 03 May 2017 08:05:51 GMT):
@zerppen welcome to help share here: https://wiki.hyperledger.org/groups/twgc/team_ie
zerppen (Wed, 03 May 2017 08:09:13 GMT):
我们的整理的，基本都已经放上去了。@baohua
zerppen (Wed, 03 May 2017 08:12:28 GMT):
@CarlXK 国际化做的翻译都在这里 https://wiki.hyperledger.org/groups/twgc/team_ie
baohua (Wed, 03 May 2017 08:16:29 GMT):
thanks! :sunflower:
zerppen (Wed, 03 May 2017 08:18:50 GMT):
u r welcome :wink:
CarlXK (Wed, 03 May 2017 08:22:15 GMT):
@zerppen 多谢啦, 梧桐树高手众多啊!!!
zerppen (Wed, 03 May 2017 08:23:51 GMT):
一般化吧，我们已经叫智链了
zhangchao (Wed, 03 May 2017 09:07:02 GMT):
你们智链都在做什么领域呢
zerppen (Wed, 03 May 2017 09:11:06 GMT):
交易所已经落地接近两年、供应链正在落地，25号新闻上的那个全球首个区块链农场就是我司签的
CarlXK (Wed, 03 May 2017 09:45:43 GMT):
666
baohua (Wed, 03 May 2017 09:58:32 GMT):
@zerppen 有没有案例介绍 请添加到 https://wiki.hyperledger.org/groups/twgc/team_cs
zerppen (Wed, 03 May 2017 10:00:24 GMT):
基于fabric的正在实施中，等7月份交过项目后介绍吧
baohua (Wed, 03 May 2017 12:23:26 GMT):
👌
zerppen (Thu, 04 May 2017 01:37:55 GMT):
请问一下 例如现在的
zerppen (Thu, 04 May 2017 01:47:57 GMT):
@jimthematrix 请问一下，现在sdk要创建一个链的话，直接用的.tx文件进行配置channel，但是这个.tx不可读。有什么好的方法可以自定义这个文件吗
zerppen (Thu, 04 May 2017 02:41:26 GMT):
因为我看到sdk里面已经有getConfigBlock函数了，相应的，在未来应该有setConfigBlock函数来替代现在这种以.tx文件作为配置的方法吧？
CarlXK (Thu, 04 May 2017 02:43:29 GMT):
setconfigblock, 也要先生成tx文件, 生成时候用的配置文件中东西挺多的, 还不太好改成命令行参数, 看起来挺麻烦
zerppen (Thu, 04 May 2017 02:44:03 GMT):
现在已经实现tx文件了，但是没法读啊
CarlXK (Thu, 04 May 2017 02:44:27 GMT):
现在这个方式生成channel就是比较麻烦
zerppen (Thu, 04 May 2017 02:44:32 GMT):
这个是怎么生成的
CarlXK (Thu, 04 May 2017 02:44:44 GMT):
为什么没法读
zerppen (Thu, 04 May 2017 02:50:07 GMT):
@CarlXK 能分享一下你是怎么读的吗
zerppen (Thu, 04 May 2017 03:04:41 GMT):
看到configtx.yaml 了
sandroku63 (Thu, 04 May 2017 04:15:37 GMT):
想請教大家有關fabric-ca的問題，我修改fabric-ca-server-config.yaml 檔案，想啟用LDAP認證，但執行fabric-ca-server start 指令後都有錯誤，不知有沒有這方面的資訊可提供參考，感謝~
sandroku63 (Thu, 04 May 2017 04:16:08 GMT):
sy2admin@ubuntu:~/fabric-ca/server$ fabric-ca-server start
2017/05/03 19:27:10 [INFO] Configuration file location: /home/sy2admin/fabric-ca/server/fabric-ca-server-config.yaml
2017/05/03 19:27:10 [INFO] Starting server in home directory: /home/sy2admin/fabric-ca/server
2017/05/03 19:27:10 [INFO] CA Home Directory: /home/sy2admin/fabric-ca/server
2017/05/03 19:27:10 [INFO] The CA key and certificate already exist
2017/05/03 19:27:10 [INFO] The key is stored by BCCSP provider 'SW'
2017/05/03 19:27:10 [INFO] The certificate is at: /home/sy2admin/fabric-ca/server/ca-cert.pem
Error: Failed to insert identity 'admin': Not supported
sandroku63 (Thu, 04 May 2017 04:18:07 GMT):
Message Attachments
jimthematrix (Thu, 04 May 2017 18:15:32 GMT):
[ ](https://chat.hyperledger.org/channel/twg-china?msg=pcDrp7RtRyFQrsxam) @yp 任何用户的cert放到admincerts里就成admin了:slight_smile:
jimthematrix (Thu, 04 May 2017 18:17:38 GMT):
[ ](https://chat.hyperledger.org/channel/twg-china?msg=L6dxzgH8LEpnyjbL6) @JasonD fabric本身不提供加密，加密需要应用层自行负责
jimthematrix (Thu, 04 May 2017 18:47:57 GMT):
[ ](https://chat.hyperledger.org/channel/twg-china?msg=DXEqDEGcxbcfzBAWv) @CarlXK 明白了，确实是个挺典型的场景，不过很可惜用跨链调用没办法实现，因为银行1在对供应商1发起的融资申请交易进行背书时，他的peer里面没有CC1也没有链A的账本，根本不能调用CC1来找到供应商跟企业之间相关的交易。这样的场景需要靠供应商1的应用层来把相关内容从链A的账本里查询出来（包括企业对交易的签名背书），通过chaincode argument作为proposal的一部分提交给CC2.
jimthematrix (Thu, 04 May 2017 19:05:21 GMT):
@zerppen 看一下test/integration/e2e/create-channel.js，已经开始支持用JSON表达的channel config来创建channel，不过目前还只能支持一部分的设置
jimthematrix (Thu, 04 May 2017 19:10:20 GMT):
下一个超级账本hackfest将在北京举行，日程刚刚公布：https://www.hyperledger.org/event/hyperledger-hackfest-june-2017
CarlXK (Fri, 05 May 2017 01:43:27 GMT):
@jimthematrix 谢谢哈, 我们也想过通过应用层中转的方式, 最后考虑到信任度可能不够的问题否定了这种方案
看到Burrow是permissioned blockchain, 不知道支持不支持
jimthematrix (Fri, 05 May 2017 01:54:21 GMT):
@CarlXK 信用度应该是基于数据本身是被企业签过名不能伪造，有什么问题吗？
CarlXK (Fri, 05 May 2017 01:58:31 GMT):
意思是把签名后的数据中转给别的链, 这个没想到, 我们是想着直接把裸数据转过去
CarlXK (Fri, 05 May 2017 01:58:45 GMT):
@jimthematrix 这样应该没问题
zhangchao (Fri, 05 May 2017 02:01:45 GMT):
应该是参与方各个企业的多重签名吧，也听复杂的
jimthematrix (Fri, 05 May 2017 02:01:57 GMT):
在链A里可以通过查询交易的方式把交易调出来，里面含有对手方的签名（供应商1和企业），然后提交给链B的银行做审核
jimthematrix (Fri, 05 May 2017 02:02:51 GMT):
不是多重签名，只是正常的endorsement signature，在所有链A里的交易都有的
zhangchao (Fri, 05 May 2017 02:08:00 GMT):
账本的transactioninfo里面有这个signature吧
zhangchao (Fri, 05 May 2017 02:26:07 GMT):
不过这种方式貌似也有个问题，供应商可以选择性的提供交易，报喜不报忧
kuangchao (Fri, 05 May 2017 02:29:15 GMT):
Message Attachments
zerppen (Fri, 05 May 2017 02:33:09 GMT):
@jimthematrix 目前只有nodeSDK实现了吧，反正java是没看到实现。另外问一下 `mspId` 的含义，因为看到代码里，及共识策略里都有这个
jimthematrix (Fri, 05 May 2017 02:38:25 GMT):
@zerppen java sdk 在1.0版不会有这个支持，需要在外面用configtxgen或者其他方法比如基于nodeSDK的应用先生成channel config
zerppen (Fri, 05 May 2017 02:40:34 GMT):
嗯 这个也只是在搭建环境的时候需要用。先有实现方法就行 ，能理解
jimthematrix (Fri, 05 May 2017 02:41:24 GMT):
关于MSP，这个设计文档看过了没？https://docs.google.com/document/d/1Qg7ZEccOIsrShSHSNl4kBHOFvLYRhQ3903srJ6c_AZE/edit
jimthematrix (Fri, 05 May 2017 02:42:27 GMT):
@kuangchao 需要具体一点的log
zerppen (Fri, 05 May 2017 02:43:45 GMT):
好的 我看看。因为我看术语表里面的关于MSP的介绍，那就表示共识策略文件里面就不涉及共识节点的指定了。 在创建链的时候就一次性指定了，我的理解有误吗？ @jimthematrix
zhangchao (Fri, 05 May 2017 02:47:47 GMT):
你们有没有什么办法在本地调试cc？
zerppen (Fri, 05 May 2017 03:04:18 GMT):
@zhangchao 0.6的时候有，目前javaSDK还在实现这块
jimthematrix (Fri, 05 May 2017 03:04:46 GMT):
@zerppen 共识节点的指定是在创世块里，如果要更改需要向系统链提交设置交易（config transaction）。具体操作还是向#fabric-consensus询问一下吧
zerppen (Fri, 05 May 2017 03:06:21 GMT):
@jimthematrix 创世区块可以指定。但是后续在构造链的时候也得对应放入 :wink:
zerppen (Fri, 05 May 2017 03:08:18 GMT):
我是看着javaSDK里面的实现来理解的。可能具体细节等会不一样
jimthematrix (Fri, 05 May 2017 03:08:44 GMT):
如果说的是`OrdererAddresses`，就不需要在链构造设置里再重提了。
zerppen (Fri, 05 May 2017 03:09:17 GMT):
构造的时候只要添加order对象就行了
jimthematrix (Fri, 05 May 2017 03:09:25 GMT):
如果说的是`Orderer Org MSP`那还是需要的，尤其涉及到policy的定义
zerppen (Fri, 05 May 2017 03:13:02 GMT):
是的 我看sdk里面还会对构造chain时指定的order跟genesisBlock取出来进行校验
zerppen (Fri, 05 May 2017 03:13:02 GMT):
是的 我看sdk里面还会对构造chain时指定的order跟取出来的genesisBlock进行校验
zhangchao (Fri, 05 May 2017 03:38:49 GMT):
@zerppen 你们怎么调试GO CC的
zerppen (Fri, 05 May 2017 03:42:54 GMT):
go我不太了解。你可以看看sdk里面是不是有个 设定开发模式的方法
zhangchao (Fri, 05 May 2017 03:47:10 GMT):
java cc呢
zhangchao (Fri, 05 May 2017 03:47:17 GMT):
你们怎么调试
chunhui (Fri, 05 May 2017 05:16:47 GMT):
Has joined the channel.
chunhui (Fri, 05 May 2017 05:23:33 GMT):
大家好。 我是IBM新加坡的工程师。。
chunhui (Fri, 05 May 2017 05:26:34 GMT):
我在用上个星期五的fabric commit
baohua (Fri, 05 May 2017 05:26:59 GMT):
欢迎 chunhui
chunhui (Fri, 05 May 2017 05:27:34 GMT):
用`e2e_cli` `deploy` 的时候有一些问题
chunhui (Fri, 05 May 2017 05:28:37 GMT):
Message Attachments
baohua (Fri, 05 May 2017 05:29:45 GMT):
用的是 1.0:alpha 镜像吗
chunhui (Fri, 05 May 2017 06:13:10 GMT):
是的
chunhui (Fri, 05 May 2017 06:13:32 GMT):
1.0alpha 以后
chunhui (Fri, 05 May 2017 06:13:44 GMT):
1acb65f2465b7fb504cfd2c8f297dee372c707c5
CarlXK (Fri, 05 May 2017 07:00:26 GMT):
@jimthematrix cryptogen 这个改过后现在怎么使用, 跟原来不一样了啊
CarlXK (Fri, 05 May 2017 07:00:26 GMT):
@jimthematrix /go/src/github.com/hyperledger/fabric/examples/dchackfest/samples, 这个例子里面讲的是cryptogen和configtxgen工具的使用
1. 如果对一个组织新增peer后重新生成启动块和相关证书, 原有交易会受到影响么(现在重新生成后的所有证书都是重新生成的)?
2. 一个peer同时属于两个组织可以么?
zhangchao (Fri, 05 May 2017 07:01:54 GMT):
go cc的print信息在哪里查看
zhangchao (Fri, 05 May 2017 07:02:10 GMT):
@CarlXK @zerppen
CarlXK (Fri, 05 May 2017 07:02:28 GMT):
知道现在的cryptogen工具怎么使用不 @here
CarlXK (Fri, 05 May 2017 07:02:57 GMT):
在容器日志里面 docker logs container_name
baohua (Fri, 05 May 2017 07:03:16 GMT):
@chunhui 可以看看正在修改的 e2e 文档：https://gerrit.hyperledger.org/r/#/c/8981/1/examples/e2e_cli/end-to-end.rst
chunhui (Fri, 05 May 2017 07:12:24 GMT):
好的 :smile:
zhangchao (Fri, 05 May 2017 07:16:25 GMT):
是container下面哪个文件呢
CarlXK (Fri, 05 May 2017 07:19:47 GMT):
我也不知道容器的日志放哪个文件的....抱歉
zhangchao (Fri, 05 May 2017 07:20:13 GMT):
就用命令看吧，多谢
hekinami (Sun, 07 May 2017 15:51:04 GMT):
Has joined the channel.
baohua (Mon, 08 May 2017 01:44:56 GMT):
大家好，工作中本周例会取消，目前工作 todo issue在这里：https://wiki.hyperledger.org/groups/twgc/meeting/2017-04-26。有问题请在线沟通。 @here
yong (Mon, 08 May 2017 03:16:45 GMT):
我看一些fabric的使用案例，1个fabric-ca是为一个org服务的，但我在fabric-ca-server-config.yaml中见到
#############################################################################
# Affiliation section
#############################################################################
affiliations:
org1:
- department1
- department2
org2:
- department1
感觉一个fabric-ca能够为多个org提供服务，到底配置CA怎么用比较好？
yp (Mon, 08 May 2017 03:27:52 GMT):
@yong for application nodes / for sdk user
yp (Mon, 08 May 2017 03:28:31 GMT):
就俩，层次用途清晰简单～
yong (Mon, 08 May 2017 03:35:07 GMT):
@yp 比如我现在给org1和org2发证书，我是创建1个fabri-ca同时为org1和org2服务好啦，还是我创建2个fabric-ca，一个为org1服务，一个为org2服务。
yp (Mon, 08 May 2017 03:37:12 GMT):
这要看实际需求啊，假如你开发测试，一个就成。
yp (Mon, 08 May 2017 03:38:32 GMT):
如果实际场景中，org1和org2都有自己的ca中心，或者没有，需要你帮忙做。
yp (Mon, 08 May 2017 03:41:30 GMT):
你纠结的不是设立几个ca，而是org到底是什么东西的集合，这个参考一下jim的回答
yp (Mon, 08 May 2017 03:41:34 GMT):
https://chat.hyperledger.org/channel/twg-china?msg=Yg73qW3pHXQR55gRy
yong (Mon, 08 May 2017 06:01:49 GMT):
@yp （每个Org的CA颁发的证书可以被fabric认可，因为CA自己已经在fabric报备过了）@jimthematrix说的CA在fabric报备了，是怎么配置的？
zerppen (Mon, 08 May 2017 08:29:38 GMT):
有在玩最新的javaSDK的同学吗
zerppen (Mon, 08 May 2017 08:29:53 GMT):
能不能帮我看看这个问题 :relaxed: https://jira.hyperledger.org/browse/FAB-3713
jchenibm (Tue, 09 May 2017 03:19:39 GMT):
Has joined the channel.
jchenibm (Tue, 09 May 2017 03:21:04 GMT):
twg-china, 我来了！😁 @here 大家好！
zhangchao (Tue, 09 May 2017 06:31:26 GMT):
@zerppen 我make peer没问题
ylsGit (Tue, 09 May 2017 07:26:49 GMT):
1.0 使用GetStateByPartialCompositeKey 查询时，遇到过Failed to decode query results [unexpected EOF]。。。。咋回事呢？
ylsGit (Tue, 09 May 2017 07:38:49 GMT):
1.0 使用GetStateByPartialCompositeKey 查询时，遇到过Failed to decode query results [unexpected EOF]。。。。何解? @here
zhouhuangjing (Tue, 09 May 2017 10:01:55 GMT):
Has joined the channel.
zhouhuangjing (Tue, 09 May 2017 10:11:50 GMT):
大家好, 请问cc在需要多个endorser背书的时候是怎样收集好足够的背书, 然后再发给orderer的, 我看了下ChaincodeInvokeOrQuery 貌似收到proposal的返回后就直接发给orderer了
baohua (Tue, 09 May 2017 12:07:39 GMT):
@jchenibm welcome~~ and also welcome self-intro here
baohua (Tue, 09 May 2017 12:09:08 GMT):
@zhouhuangjing the cli does not do the collection now, suggest use sdk to finish more complicated endorsement.
zhouhuangjing (Tue, 09 May 2017 14:07:48 GMT):
@baohua thanks!
CarlXK (Wed, 10 May 2017 10:08:00 GMT):
@here 有谁遇到过这个错误么
```
017-05-10 09:56:16.386 UTC [gossip/comm#-1] Probe -> DEBU 2bf Entering, endpoint: 127.0.0.1:7051 PKIID: []
fatal error: unexpected signal during runtime execution
[signal SIGSEGV: segmentation violation code=0x1 addr=0x63 pc=0x7fc8d3df1259]
```
CarlXK (Wed, 10 May 2017 10:08:00 GMT):
@here 有谁遇到过这个错误么
```
017-05-10 09:56:16.386 UTC [gossip/comm#-1] Probe -> DEBU 2bf Entering, endpoint: 127.0.0.1:7051 PKIID: []
fatal error: unexpected signal during runtime execution
[signal SIGSEGV: segmentation violation code=0x1 addr=0x63 pc=0x7fc8d3df1259]
```
CentOS7.3 使用getting_started.rst , 启动Peer一直报这个错
CarlXK (Wed, 10 May 2017 10:10:23 GMT):
@jimthematrix , 能帮忙看看么
jimthematrix (Wed, 10 May 2017 17:19:38 GMT):
@CarlXK 没有碰到过，还是去#fabric-peer-endorser-committer里面问一下，记得tag @yacov and @C0rWin
jimthematrix (Wed, 10 May 2017 17:19:38 GMT):
@CarlXK 没有碰到过，建议去#fabric-peer-endorser-committer里面问一下，记得tag @yacov and @C0rWin
C0rWin (Wed, 10 May 2017 17:19:38 GMT):
Has joined the channel.
CarlXK (Thu, 11 May 2017 02:00:25 GMT):
@jimthematrix 好的, 谢谢
baohua (Thu, 11 May 2017 06:52:53 GMT):
hi, all, zhou xing is helping organize some warm-up meetup/seminar events for the June hackathon. We will have a call 10AM tmr morning, welcome everyone to join.
Dial-in Number(s):
800-820-0027 400-821-0751
Participant Code:
13497071
marryton007 (Thu, 11 May 2017 07:23:53 GMT):
Has joined the channel.
FenglianXu (Thu, 11 May 2017 20:03:01 GMT):
Has joined the channel.
zerppen (Fri, 12 May 2017 10:55:13 GMT):
遇到一个非常奇怪的问题！机器上跑的e2e测试，已经测试玩chaincode里面的函数。忽然机器挂了，重启后，再次docker-compse进去，发现可以执行chaincode里的query，但是执行不了invoke @here @jimthematrix
zerppen (Fri, 12 May 2017 10:57:03 GMT):
执行 invoke，报的异常信息为 `Error: Error sending transaction invoke: Got unexpected status: NOT_FOUND
zerppen (Fri, 12 May 2017 11:00:50 GMT):
Message Attachments
jimthematrix (Fri, 12 May 2017 15:38:20 GMT):
@zerppen 从上面的log看，query是针对channel -C 00001，但是invoke是 -C mychannel
jimthematrix (Fri, 12 May 2017 15:39:38 GMT):
基本可以推测mychannel设置里面没有Org0MSP（org1）参与
zerppen (Sun, 14 May 2017 15:00:32 GMT):
Message Attachments
zerppen (Sun, 14 May 2017 15:01:05 GMT):
抱歉上一张图我截的有问题，这是真正的问题
zerppen (Sun, 14 May 2017 15:01:08 GMT):
@jimthematrix
jimthematrix (Mon, 15 May 2017 02:58:08 GMT):
@zerppen `Args`里的第一个元素`invoke`应该对应的是负责转账的函数（example_cc里叫“move”）
zerppen (Mon, 15 May 2017 03:05:05 GMT):
我用的e2e `https://github.com/hyperledger/fabric/tree/master/examples/dchackfest/samples/e2e`
zerppen (Mon, 15 May 2017 03:05:39 GMT):
查询到的50是通过调用invoke交易后的
zerppen (Mon, 15 May 2017 03:05:54 GMT):
我在想是不是因为我用的master分支造成的这个原因
zerppen (Mon, 15 May 2017 03:08:07 GMT):
Message Attachments
zerppen (Mon, 15 May 2017 03:08:18 GMT):
e2e里没有move这个函数
jimthematrix (Mon, 15 May 2017 03:19:58 GMT):
哦那看来NOT_FOUND是从orderer返回的，基于前面针对同一个channel的query没问题，这个channel在peer上有，但是在orderer上没有。
jimthematrix (Mon, 15 May 2017 03:20:57 GMT):
会不会orderer宕掉过，存在system ledger里的信息丢了
jimthematrix (Mon, 15 May 2017 03:24:54 GMT):
orderer曾经用ramledger作为默认类型（内存），如果想要用file ledger，需要设置`ORDERER_LEDGER_TYPE=file`
jimthematrix (Mon, 15 May 2017 03:24:54 GMT):
orderer曾经用ramledger作为默认类型（内存），如果想要用file ledger，需要设置`ORDERER_LEDGER_TYPE=file`
CarlXK (Mon, 15 May 2017 04:03:27 GMT):
@zerppen , 你用sdk访问的么, 用这个例子创建channel/ 加入peer/cli调用example 都成功, 但是用sdk访问channel就报403
zerppen (Mon, 15 May 2017 04:05:56 GMT):
@jimthematrix 我研究一下代码看看。初步估计是因为endorsment 节点保存了chaincode name/path。但是丢失了chaincode文件
zerppen (Mon, 15 May 2017 04:06:29 GMT):
@CarlXK 现在javaSDK能跑javaChaincode了吗
zerppen (Mon, 15 May 2017 04:10:40 GMT):
你创建了channel，有join channel吗
zerppen (Mon, 15 May 2017 04:13:31 GMT):
或者你直接用sdk跑那个e2e，代码里有各个细节，你可以自己打个log看看
zerppen (Mon, 15 May 2017 04:13:34 GMT):
@CarlXK
CarlXK (Mon, 15 May 2017 04:14:32 GMT):
我用javasdk 跑的go cc, 连接channel都不行, 我也不知道啥原因
zerppen (Mon, 15 May 2017 04:15:25 GMT):
你先跑javaSDK里面的e2e，或者你直接看它代码怎么连接channel
zerppen (Mon, 15 May 2017 04:15:44 GMT):
如果你e2
zerppen (Mon, 15 May 2017 04:15:44 GMT):
如果你e2e 不成功，就是最近的代码有bug
CarlXK (Mon, 15 May 2017 11:01:22 GMT):
最新javaSDK代码匹配的是alpha2的镜像, 而fabric/docs/source/getting_started.rst 里面的工具匹配的是alpha的版本, 我看看找下新的工具
zhouhuangjing (Mon, 15 May 2017 13:04:17 GMT):
请教下大家一个读写集的问题, 不确定是不是我的理解是不是有误,
我的理解是如果账本的写入要依赖于readset没有发生修改, 这个要求是不是太苛刻了? 如果有一定的并发量怎么办? 会不会造成大量的交易失败?
而且我觉得很多情况, 用户不关心某个数据是不是在交易过程中改变了, 只要系统保证好同步就行了, 比如说我只是希望A加100
交易期间有谁更改过这个数据我并不关心, 只要保证我在最新的结果上操作就好了
tongli (Mon, 15 May 2017 14:28:01 GMT):
Has joined the channel.
leungjob (Tue, 16 May 2017 03:22:02 GMT):
刚刚更新了x86_64-1.0.0-alpha2，并部署到服务器中，执行 fabric-ca-client enroll -u http://admin:adminpw@ca0:7054 后，服务端发生 http: TLS handshake error from 172.20.0.6:38868: tls: oversized record received with length 21536 错误，请问怎么解决？谢谢！
leungjob (Tue, 16 May 2017 03:22:02 GMT):
刚刚更新了x86_64-1.0.0-alpha2版本，并部署到服务器中，执行 fabric-ca-client enroll -u http://admin:adminpw@ca0:7054 后，服务端发生 http: TLS handshake error from 172.20.0.6:38868: tls: oversized record received with length 21536 错误，请问怎么解决？谢谢！
baohua (Tue, 16 May 2017 03:30:56 GMT):
@zhouhuangjing 目前是对 A+100 后的结果进行确认，并不是 A+100 这个操作。因此，会对 readset 有要求。
zhouhuangjing (Tue, 16 May 2017 03:35:07 GMT):
@baohua 非常感谢, 看来我理解有误, 我再深入看看
zhouhuangjing (Tue, 16 May 2017 08:40:46 GMT):
Message Attachments
zhouhuangjing (Tue, 16 May 2017 08:41:10 GMT):
@baohua https://wiki.hyperledger.org/groups/twgc/fabric-doc/read-write-set.md
可能我没有说清楚, 感觉这块确实有疑问, Linsheng Yu 在翻译的时候也提出了相同的疑问
请问hyperledger有性能报告吗, 在交易比较频繁的时候
tongli (Tue, 16 May 2017 14:36:14 GMT):
guys, this is Tong Li from IBM.
tongli (Tue, 16 May 2017 14:36:45 GMT):
just started working on hyperledger. was assigned to work on the CI just yesterday.
tongli (Tue, 16 May 2017 14:37:13 GMT):
in terms of the performance report, I think we probably can add some plugins to the CI to generate something.
tongli (Tue, 16 May 2017 14:37:44 GMT):
I joined this channel because I am a native Chinese and can speak Chinese.
tongli (Tue, 16 May 2017 14:38:11 GMT):
the only problem I have is that it is a bit too slow for me to input Chinese.
tongli (Tue, 16 May 2017 14:43:10 GMT):
happy to meet everybody in this channel.
shibo.lin (Tue, 16 May 2017 23:51:23 GMT):
welcome
baohua (Wed, 17 May 2017 02:20:17 GMT):
welcome, @tongli from my side, an urgent requirement is to let ci trigger some notifications in rocketchat, like new patchset submission, ci checking pass/fails, etc. This will help improve the work efficiency indeed.
jimthematrix (Wed, 17 May 2017 02:33:33 GMT):
@tongli welcome, are you 李彤 from the openstack team?
jimthematrix (Wed, 17 May 2017 02:35:15 GMT):
Ramesh would definitely appreciate help on the CI side, that guy has been working day and night for a long time
jimthematrix (Wed, 17 May 2017 02:37:55 GMT):
@zhouhuangjing 你上面提到的A+100这样的交易，只要chaincode里面没有调用stub.GetState()，readset就是空的，不会出现交易被拒的情况
jimthematrix (Wed, 17 May 2017 02:38:24 GMT):
至于上面的T1，T2的例子，确实这是app需要考虑的
zhouhuangjing (Wed, 17 May 2017 02:38:53 GMT):
@jimthematrix 谢谢, 这个我了解, 我说的就是同时有get 和put的情况, 感觉这个是很常见的场景
jimthematrix (Wed, 17 May 2017 02:39:52 GMT):
这是目前Fabric的设计特点，由于不是UTXO，必须考虑交易对初始状态的要求，表达在readset里面
zhouhuangjing (Wed, 17 May 2017 02:40:35 GMT):
嗯, 尽量在应用层去保证吧
jimthematrix (Wed, 17 May 2017 02:40:41 GMT):
是的
jimthematrix (Wed, 17 May 2017 02:42:03 GMT):
需要用transaction event listener跟交易提交串行起来
tongli (Wed, 17 May 2017 03:05:01 GMT):
@jimthematrix jim, it is me. Just switch to Hyperledger.
baohua (Wed, 17 May 2017 05:47:41 GMT):
@zhouhuangjing 目前没有性能报告 社区已经开始探讨一些性能相关的问题和评测 可以多关注
baohua (Wed, 17 May 2017 05:49:32 GMT):
@jimthematrix rwset 的设计比较严格 把问题抛给了 app 层 有时候可以放松一些限制。比如r set 和w set 中可以标记哪些有关联。允许部分提交，这对 app 是更简单易用。不过这对平台设计和实现上就更复杂了。
icodezjb (Thu, 18 May 2017 05:48:06 GMT):
Has joined the channel.
zhangchao (Thu, 18 May 2017 07:27:37 GMT):
read-write-set的这种version方式不是跟数据库里面的乐观锁一致吗，乐观锁都是需要在应用层做处理的，所以fabric的这种处理方式也是一样的。有个很大的不同是，数据库交易处理打开和关闭是很快的，fabric需要由orderer打包block交给committer提交，交易时间拉长了，冲突的概率会更大一些
CarlXK (Thu, 18 May 2017 08:57:02 GMT):
这个并发量大的时候就太蛋疼了
tolak (Thu, 18 May 2017 16:15:47 GMT):
Has joined the channel.
tolak (Thu, 18 May 2017 16:16:47 GMT):
还有没睡的吗？
tolak (Thu, 18 May 2017 16:17:14 GMT):
我用官方的脚步get-docker-images.sh下载fabric的docker image好慢，各位有好的法子吗？
tolak (Thu, 18 May 2017 16:17:14 GMT):
我用官方的脚本get-docker-images.sh下载fabric的docker image好慢，各位有好的法子吗？
icodezjb (Fri, 19 May 2017 00:28:10 GMT):
[ ](https://chat.hyperledger.org/channel/twg-china?msg=rjeipAkmEfyXSs4mt) @tolak 被墙了，要学会科学上网~
yahtoo (Fri, 19 May 2017 07:06:31 GMT):
@jimthematrix 你好，解决一个问题本地可以commit多次吗？
yahtoo (Fri, 19 May 2017 07:07:57 GMT):
@tolak 可以用国内镜像加速 $ sudo echo "DOCKER_OPTS=\"--registry-mirror=http://hub-mirror.c.163.com\"" >> /etc/default/docker
$ service docker restart
grapebaba (Fri, 19 May 2017 07:32:05 GMT):
@yahtoo 一般是commit --amend
yahtoo (Fri, 19 May 2017 07:34:07 GMT):
ok 这样是不是存在调试时很难回退的问题
grapebaba (Fri, 19 May 2017 07:36:11 GMT):
先测试好
grapebaba (Fri, 19 May 2017 07:36:29 GMT):
gerrit这个好像一般都是单个commit review
tolak (Fri, 19 May 2017 10:54:16 GMT):
@icodezjb 我是有挂了vpn咯，可是还是很慢，老挂掉
tolak (Fri, 19 May 2017 10:55:18 GMT):
@yahtoo 谢谢，我试试
tolak (Fri, 19 May 2017 11:00:19 GMT):
@yahtoo 没试过同一个commit多次patch然后回退调试的情况，不知道cherry-pick是否可以拉到指定patch
baohua (Mon, 22 May 2017 01:34:39 GMT):
@here Dear all, we will have group meeting at 10AM this Wednesday morning, pls help update the agenda at https://wiki.hyperledger.org/groups/twgc/meeting/2017-05-24, thanks!
Calvin_Heo (Mon, 22 May 2017 02:54:02 GMT):
Has joined the channel.
aaronzheng (Mon, 22 May 2017 05:37:10 GMT):
Has joined the channel.
baohua (Tue, 23 May 2017 02:37:41 GMT):
@chenxuan here
chenxuan (Tue, 23 May 2017 02:37:41 GMT):
Has joined the channel.
chenxuan (Tue, 23 May 2017 02:42:22 GMT):
我使用的饿
chenxuan (Tue, 23 May 2017 02:43:07 GMT):
我使用的是e2e_cli的例子 docker_compose.yaml设置了很多的证书
chenxuan (Tue, 23 May 2017 02:43:25 GMT):
但是我发起了一笔交易并没有签名
chenxuan (Tue, 23 May 2017 02:43:30 GMT):
是怎么回事
baohua (Tue, 23 May 2017 02:44:38 GMT):
用的 cli 还是 sdk 发起的交易
chenxuan (Tue, 23 May 2017 02:44:46 GMT):
cli
baohua (Tue, 23 May 2017 02:44:58 GMT):
交易已经 endorse 过了？
chenxuan (Tue, 23 May 2017 02:45:07 GMT):
恩
baohua (Tue, 23 May 2017 02:45:25 GMT):
怎么查看的认为它没有签名呢？
chenxuan (Tue, 23 May 2017 02:46:01 GMT):
我的整个过程是这样了
chenxuan (Tue, 23 May 2017 02:46:17 GMT):
注释了network_setup.sh里面的
chenxuan (Tue, 23 May 2017 02:46:23 GMT):
很多函数的调用
chenxuan (Tue, 23 May 2017 02:47:54 GMT):
注释掉了script/script.sh的 instantiateChaincode 之后的所有的操作
chenxuan (Tue, 23 May 2017 02:47:59 GMT):
然后自己进去到cli
chenxuan (Tue, 23 May 2017 02:48:20 GMT):
调用命令来instantiate，invoke query
chenxuan (Tue, 23 May 2017 02:48:22 GMT):
的
chenxuan (Tue, 23 May 2017 02:48:48 GMT):
整个过程我没有看到做签名的动作
chenxuan (Tue, 23 May 2017 02:48:51 GMT):
我很奇怪
chenxuan (Tue, 23 May 2017 02:49:38 GMT):
整个过程都是没有问题的
chenxuan (Tue, 23 May 2017 02:49:49 GMT):
我只是很奇怪签名怎么做的
baohua (Tue, 23 May 2017 02:50:09 GMT):
你说的签名是指？这个过程是默认有签名的。
chenxuan (Tue, 23 May 2017 02:51:07 GMT):
cli帮着做了？
baohua (Tue, 23 May 2017 02:51:23 GMT):
对
baohua (Tue, 23 May 2017 02:52:27 GMT):
可以看下：peer/chaincode/install.go
baohua (Tue, 23 May 2017 02:52:33 GMT):
GetSignedProposal
baohua (Tue, 23 May 2017 02:52:50 GMT):
这个是对提案进行自身签名，然后 endorser 那边会加上背书签名。
chenxuan (Tue, 23 May 2017 02:54:14 GMT):
哦
chenxuan (Tue, 23 May 2017 02:54:29 GMT):
peer chaincode instantiate -o orderer.example.com:7050 --tls $CORE_PEER_TLS_ENABLED --cafile $ORDERER_CA -C $CHANNEL_NAME -n mycc -v 1.0 -c '{"Args":["init"]}' -P "OR ('Org1MSP.member','Or
g2MSP.member')"
chenxuan (Tue, 23 May 2017 02:55:04 GMT):
这个instantiate 设定了背书策略 但是为什么还有设置 -o orderer.example.com:7050 --tls $CORE_PEER_TLS_ENABLED --cafile $ORDERER_CA 呢？
chenxuan (Tue, 23 May 2017 02:55:45 GMT):
那是不是意味这一笔交易发到order 然后根据背书的策略来发送到背书节点
baohua (Tue, 23 May 2017 03:06:26 GMT):
aha initiate 是个系统链码的 deploy 交易。是先发提案给 endorse，背书后，构造交易（envelope） 给 orderer。所有的合法交易都得发给 orderer。
chenxuan (Tue, 23 May 2017 03:11:49 GMT):
那如何是知道一个节点是endorse？
baohua (Tue, 23 May 2017 03:13:51 GMT):
得先知道 目前没法自动探测
chenxuan (Tue, 23 May 2017 03:16:21 GMT):
e2e的例子当中没有提前设置啊 只是设置了背书的策略而已
baohua (Tue, 23 May 2017 03:17:13 GMT):
默认是本地节点
chenxuan (Tue, 23 May 2017 06:03:11 GMT):
fabric-ca fabirc-client-ca 的区别是
chenxuan (Tue, 23 May 2017 06:03:12 GMT):
？
chenxuan (Tue, 23 May 2017 10:52:41 GMT):
Cannot find module '/home/tinkpad/jsprojects/fabric-sdk-node/examples/balance-transfer/node_modules/grpc/src/node/extension_binary/grpc_node.node'
chenxuan (Tue, 23 May 2017 10:52:59 GMT):
@jimthematrix
chenxuan (Tue, 23 May 2017 10:53:24 GMT):
我运行runApp.sh的时候
chenxuan (Tue, 23 May 2017 12:11:57 GMT):
有人用过fabric-sdk-node
chenxuan (Tue, 23 May 2017 12:11:57 GMT):
好的@jimthematrix
jimthematrix (Tue, 23 May 2017 14:58:08 GMT):
@chenxuan 我建议如果想比较透彻地了解还是看fabric-sdk-node的end2end（fabric-sdk-node/test/integration/e2e/*.js)，e2CLI
jimthematrix (Tue, 23 May 2017 14:58:08 GMT):
@chenxuan 我建议如果想比较透彻地了解还是看fabric-sdk-node的end2end（fabric-sdk-node/test/integration/e2e/*.js)，e2e CLI是走了很多捷径的，或用系统默认值（比如身份如何设定，根本就是用的peer local MSP的身份，而不是应用层用户身份），并不适于了解系统组件之间的关系
chenxuan (Wed, 24 May 2017 00:39:53 GMT):
好的 @jimthematrix 遇到不懂我问你
tedljw (Wed, 24 May 2017 02:16:25 GMT):
Has joined the channel.
luomin (Wed, 24 May 2017 02:42:44 GMT):
大家好 刚才旁听了这周的例会 感谢各位贡献 并且也想在中国工作组中贡献力量。 例如刚才提到 文档审阅这块。 不知是否直接edit文档网页，填写自己想审阅译文就行？ 另外 请指教如何能成为本社区的Volunteers/Members 谢谢！
baohua (Wed, 24 May 2017 02:45:59 GMT):
@luomin 谢谢关注！是的，直接编写 wiki 即可 https://wiki.hyperledger.org/groups/twgc/team_ie，有不确定的地方可以跟大家讨论交流。社区是开放的，任何人都欢迎参加或组织相关的活动 ：）
baohua (Wed, 24 May 2017 02:46:25 GMT):
btw 欢迎做自我介绍 结识更多的小伙伴:grinning:
luomin (Wed, 24 May 2017 02:51:00 GMT):
@baohua 谢谢baohua迅速的回复 试着修改了一下 没有问题。 另外有一点想确认 我工作地点在日本 就职NTT 目前也非常有兴趣参与到fabric中 是否可以在中国工作组贡献力量 （以个人名义 也没问题）
zhangchao (Wed, 24 May 2017 02:55:25 GMT):
@luomin ，我们是日立研究院，如果贵公司有区块链课题和项目，可以一起合作哈
luomin (Wed, 24 May 2017 02:56:13 GMT):
@zhangchao :grinning:太好了 你们是在东京这边的么
zhangchao (Wed, 24 May 2017 02:56:37 GMT):
我们在北京，东京也有
luomin (Wed, 24 May 2017 02:56:57 GMT):
是 fabric这块 你们和fujitsu走在前头
luomin (Wed, 24 May 2017 02:57:23 GMT):
@zhangchao 以后请多多指教！
baohua (Wed, 24 May 2017 02:57:34 GMT):
欢迎几位，hyperledger 社区是十分开放和活跃的社区，任何形式的贡献（包括代码开发、参加组织活动、培训，应用等）都是欢迎的。这里可以找到现在工作组在做的一些工作，欢迎大家积极参与：https://wiki.hyperledger.org/groups/tsc/technical-working-group-china
luomin (Wed, 24 May 2017 02:57:52 GMT):
:thumbsup:
zhangchao (Wed, 24 May 2017 02:58:02 GMT):
互相探讨
luomin (Wed, 24 May 2017 02:58:33 GMT):
@baohua 另外 您刚才提到一个微信群 可以共享一下么
baohua (Wed, 24 May 2017 02:58:36 GMT):
工作组本月的情况汇总，欢迎大家帮忙 review：https://wiki.hyperledger.org/groups/twgc/report/2017-05
zhangchao (Wed, 24 May 2017 02:58:37 GMT):
@baohua ，未来可能希望在解决方案上给社区提供一些帮助
baohua (Wed, 24 May 2017 02:59:27 GMT):
@luomin 文档组和案例组都有微信群，可以找 @ylsGit
baohua (Wed, 24 May 2017 03:00:04 GMT):
@zhangchao 如果已有应用案例的 欢迎添加到 https://wiki.hyperledger.org/groups/twgc/team_cs 进行分享
zhangchao (Wed, 24 May 2017 03:02:18 GMT):
好像里面没啥东西
baohua (Wed, 24 May 2017 03:03:46 GMT):
正在征集中 已经占了一些坑了
zhangchao (Wed, 24 May 2017 03:05:11 GMT):
OK，我也去占一个
baohua (Wed, 24 May 2017 03:08:30 GMT):
中英文均可
luomin (Wed, 24 May 2017 03:12:45 GMT):
@baohua 还想请问下月北京大会 有几场bc相关的speach 看看能否给公司申请去：）
CarlXK (Wed, 24 May 2017 03:15:03 GMT):
@baohua 官方有没有在做blockchain-explorer 1.0?
CarlXK (Wed, 24 May 2017 03:15:03 GMT):
@baohua @jimthematrix 官方有没有在做blockchain-explorer 1.0?
baohua (Wed, 24 May 2017 03:49:33 GMT):
@luomin 对 有不少区块链相关的主题 欢迎参加
baohua (Wed, 24 May 2017 03:49:53 GMT):
@CarlXK 最近 be 进展略慢 感兴趣的欢迎加入项目 :(
luomin (Wed, 24 May 2017 03:50:07 GMT):
是 19号 每个session都有报告 20号没看到
luomin (Wed, 24 May 2017 03:50:16 GMT):
请问有些什么安排么
baohua (Wed, 24 May 2017 03:51:00 GMT):
这里有比较新的 agenda：https://www.lfasiallc.com/linuxcon-containercon-cloudopen-china
luomin (Wed, 24 May 2017 03:55:16 GMT):
谢谢@baohua 另外21号handson 需要额外费用么
baohua (Wed, 24 May 2017 04:00:22 GMT):
21？ hackfest 是19-20两天
luomin (Wed, 24 May 2017 04:08:12 GMT):
@baohua 不好意思 hackfest 是19-20日 另外 网上登记好像无须费用https://www.regonline.com/hyperledgerhackfestjune2017 但是 参加 https://www.lfasiallc.com/linuxcon-containercon-cloudopen-china/about/schedule需要注册费 250刀左右 请问有什么区别 是同一个活动么
luomin (Wed, 24 May 2017 04:22:43 GMT):
@baohua 谢谢 弄明白了 请问 hackfest活动是否会和linxucon冲突？您共享的最新agenda上 20号和hyperledger相关的报告不多 是否 hackfest这边有什么安排
shibo.lin (Wed, 24 May 2017 05:10:16 GMT):
@luomin 我也在东京。
luomin (Wed, 24 May 2017 05:10:58 GMT):
@shibo.lin 你好啊
luomin (Wed, 24 May 2017 05:12:37 GMT):
看member list 名片时区 @Hangyu 好像也是日本？ @shibo.lin 你在那里啊
shibo.lin (Wed, 24 May 2017 05:14:22 GMT):
@luomin 六本木那边。上班要经过丰洲的。
luomin (Wed, 24 May 2017 05:16:08 GMT):
@shibo.lin 我不在data(丰洲) 我在武蔵野 NTT研究所那边 ：）
luomin (Wed, 24 May 2017 05:16:43 GMT):
你有微信之类么 多联系
chenxuan (Wed, 24 May 2017 05:17:39 GMT):
fabric block生成的条件是什么？
xixuejia (Wed, 24 May 2017 10:55:12 GMT):
@chenxuan 在genesis里定义的BatchTimeout和BatchSize
xixuejia (Wed, 24 May 2017 10:56:04 GMT):
@baohua 现在社区还招人嘛？希望能够加入为社区做贡献:grin:
baohua (Wed, 24 May 2017 12:54:46 GMT):
招！欢迎加入，现在有四个方面的活动：https://wiki.hyperledger.org/groups/tsc/technical-working-group-china
baohua (Wed, 24 May 2017 12:54:46 GMT):
招！欢迎加入，现在有四个方面的工作可以参加：https://wiki.hyperledger.org/groups/tsc/technical-working-group-china
baohua (Wed, 24 May 2017 13:10:31 GMT):
@chenxuan 超时或达到一定量的 tx，都会触发生成 block。
baohua (Wed, 24 May 2017 13:11:12 GMT):
@luomin linuxcon 是收费的，内容十分广泛。hackfest 是 hyperledger 社区搞的。两者时间都是19、20两天，注意是不同地点。
xixuejia (Wed, 24 May 2017 13:24:49 GMT):
@baohua 多谢Baohua, 对第一个group比较感兴趣。具体参与方式是怎样的呢
baohua (Wed, 24 May 2017 13:45:01 GMT):
这个？https://wiki.hyperledger.org/groups/twgc/team_di
xixuejia (Wed, 24 May 2017 13:45:17 GMT):
yes
baohua (Wed, 24 May 2017 13:50:06 GMT):
aha, currently we focus on developing and also collect the contributions from local. Feel free to help submit patchset and update the wiki.
tolak (Wed, 24 May 2017 14:35:32 GMT):
我这边从fabric gerrit拉源码为什么好慢，平均5~10kb/s，使不使用代理都这样。难道是我网本身太慢了吗？:joy:
chenxuan (Thu, 25 May 2017 01:34:04 GMT):
谁能说一下org和channel的区别吗？
JasonD (Thu, 25 May 2017 01:44:21 GMT):
目前哪个SDK完成度较高的？ 我使用的是nodejs的sdk，然而channel里看到很多问题没人解答，bug很多
tolak (Thu, 25 May 2017 01:59:03 GMT):
会不会是go？
zhangchao (Thu, 25 May 2017 02:00:17 GMT):
我们在用java，没啥大问题
JasonD (Thu, 25 May 2017 02:06:26 GMT):
忧伤，偏偏当时选了nodejs
JasonD (Thu, 25 May 2017 02:08:33 GMT):
有个机制的问题，如果ca orderer等，包括chaincode container都挂掉。重启了ca orderer peer之后，chaincode应该如何重启？理论上，channel 已经有了，chaincode也已经install在 peer里了，那么只需要instantiate chaincode?
zhangchao (Thu, 25 May 2017 02:34:38 GMT):
invoke就可以
chenxuan (Thu, 25 May 2017 02:41:15 GMT):
不可以＠zhangchao
JasonD (Thu, 25 May 2017 02:41:51 GMT):
不可以的 这个时候没有cc 的 container
zhangchao (Thu, 25 May 2017 02:42:11 GMT):
我再java可以啊
zhangchao (Thu, 25 May 2017 02:43:04 GMT):
没有chaincode的话，需要先install
JasonD (Thu, 25 May 2017 02:43:09 GMT):
没有cc container，你invoke最终调用到哪去了？java sdk会自动检测，然后instantiate contaienr ？
JasonD (Thu, 25 May 2017 02:43:18 GMT):
install和instantiate不是一回事
zhangchao (Thu, 25 May 2017 02:43:19 GMT):
不用再instantiate了
JasonD (Thu, 25 May 2017 02:43:41 GMT):
这个时候docker ps 是没有cc container的
zhangchao (Thu, 25 May 2017 02:43:42 GMT):
instantiate调一次就够了，设置初始变量
zhangchao (Thu, 25 May 2017 02:44:00 GMT):
我在java就可以
JasonD (Thu, 25 May 2017 02:44:32 GMT):
你可能没理解清楚，我的问题前提是：ca peer orderer等都down了，包括cc container。然后前几个都启动了，cc container应该如何启动？
zhangchao (Thu, 25 May 2017 02:45:32 GMT):
如果invoke时候不能自动启动的话，就是bug了
xixuejia (Thu, 25 May 2017 02:45:51 GMT):
理论上invoke的时候如果cc container不存在应该可以自动启动，如果Install了的话
zhangchao (Thu, 25 May 2017 02:46:07 GMT):
不需要再走一遍install，instaniate
JasonD (Thu, 25 May 2017 02:46:13 GMT):
== 我试试
JasonD (Thu, 25 May 2017 02:46:22 GMT):
我一直想的是得先有 cc container
JasonD (Thu, 25 May 2017 02:46:27 GMT):
才能invoke
xixuejia (Thu, 25 May 2017 02:46:47 GMT):
cc是在channel的level instantiate的
zhangchao (Thu, 25 May 2017 02:49:15 GMT):
我们现在做的是，在一个节点install->instantiate，然后在别的节点install就够了，调用invoke就会启动一个新的container。前提这些节点都在一台机器上，如果不在一台机器没试过
JasonD (Thu, 25 May 2017 03:06:36 GMT):
测试通过！原来不需要instantiate了，invoke即可
JasonD (Thu, 25 May 2017 03:10:06 GMT):
那剩下的就是nodejs的bug了，我去channel问问。目前的状况是重启第二次就不行
chenxuan (Thu, 25 May 2017 03:13:13 GMT):
var test_input = {
channel : {
name : channel_name,
consortium : 'SampleConsortium',
settings : {
'batch-size' : {'max-message-count' : 10, 'absolute-max-bytes' : '99m', 'preferred-max-bytes' : '512k'},
'batch-timeout' : '10s',
'hashing-algorithm' : 'SHA256',
'consensus-type' : 'solo'
},
policies : {
Readers : {threshold : 'ANY'},
Writers : {threshold : 'ANY'},
Admins : {threshold : 'ANY'},
AcceptAllPolicy : {signature : ACCEPT_ALL}
},
orderers : {
organizations : [{
mspid : 'OrdererMSP',
policies : {
Readers : {signature : ACCEPT_ALL},
Writers : {signature : ACCEPT_ALL},
Admins : {signature : ACCEPT_ALL}
},
'end-points' : ['orderer0:7050']
}],
policies : {
Readers : {threshold : 'ANY'},
Writers : {threshold : 'ANY'},
Admins : {threshold : 'ANY'},
AcceptAllPolicy : {signature : ACCEPT_ALL},
BlockValidation : {threshold : 'ANY' , sub_policy : 'Writers'}
}
},
peers : {
organizations : [{
id : 'Org1MSP',
'anchor-peers' : ['peer0:7051'],
policies : {
Readers : {signature : ACCEPT_ALL},
Writers : {signature : ACCEPT_ALL},
Admins : {signature : ACCEPT_ALL}
}
},{
id : 'Org2MSP',
'anchor-peers' : ['peer2:8051'],
policies : {
Readers : {signature : ACCEPT_ALL},
Writers : {signature : ACCEPT_ALL},
Admins : {signature : ACCEPT_ALL}
}
}],
policies : {
Readers : {threshold : 'ANY'},
Writers : {threshold : 'ANY'},
Admins : {threshold : 'ANY'}
},
}
}
};
chenxuan (Thu, 25 May 2017 03:13:27 GMT):
麻烦哪位那个这个给解释一下
chenxuan (Thu, 25 May 2017 03:13:38 GMT):
使用ｎｏｄｅ 创建ｃｈａｎｎｅｌ的时候
chenxuan (Thu, 25 May 2017 03:13:44 GMT):
的配置信息
yahtoo (Thu, 25 May 2017 07:27:32 GMT):
@here 使用kafka共识如何启动多个orderer？
yahtoo (Thu, 25 May 2017 07:27:59 GMT):
有人知道一下吗
tolak (Thu, 25 May 2017 07:49:47 GMT):
你们有谁从gerrit上clone过fabric的源码吗？有没有很慢？我到目前为止还没成功clone过。。。
chenxuan (Thu, 25 May 2017 07:55:11 GMT):
如何修改记账类型
icodezjb (Thu, 25 May 2017 08:05:39 GMT):
[ ](https://chat.hyperledger.org/channel/twg-china?msg=DduSzuk6dAQR6zad5) @yahtoo 需要科学上网。直接从github下载源码也可以
aaronzheng (Thu, 25 May 2017 08:17:52 GMT):
想问一下，affiliation 是在哪里生成设置的啊？我现在用sdk自己写了enroll一个member，但是affiliation 只能指定是之前e2e的那个，那么我要自定义的话 是在哪一步做的啊。
chenxuan (Thu, 25 May 2017 10:39:32 GMT):
如何修改记账类型 @baohua
tolak (Thu, 25 May 2017 13:20:19 GMT):
@baohua 按照您博客地址http://blog.csdn.net/yeasy/article/details/54928343#comments ，运行docker-compose up，出现错误信息 “[nodeCmd] serve -> ERRO 234 create default chain [testchainid] failed with Cannot create ledger from genesis block, due to LedgerID already exists”。由于先前有执行过这个example了，只是中间出错没有做完，请问有什么方法可以将先前的workspace清理干净吗？
baohua (Fri, 26 May 2017 01:12:45 GMT):
记账类型？你说账本类型么 配置文件有选项
baohua (Fri, 26 May 2017 01:13:14 GMT):
@tolak aha 版本改了 看看这里有比较新的步骤：https://github.com/yeasy/docker-compose-files/blob/master/hyperledger/1.0/
tolak (Fri, 26 May 2017 01:17:25 GMT):
@baohua 好的，谢谢！
jimthematrix (Fri, 26 May 2017 02:35:34 GMT):
@chenxuan 用JSON配置channel在SDK已经不支持了，最新workflow请参见https://jira.hyperledger.org/browse/FAB-1678
jimthematrix (Fri, 26 May 2017 02:40:04 GMT):
记账类型只有file了，状态数据库（leveldb，couchdb）可以在core。yaml里设置
jimthematrix (Fri, 26 May 2017 02:40:04 GMT):
记账类型（ledger）只有file了，状态数据库（leveldb，couchdb）可以在core。yaml里设置
chenxuan (Fri, 26 May 2017 02:42:08 GMT):
但是我没有ｂｌｏｃｋ文件在ｐｅｅｒ节点 @jimthematrix
jimthematrix (Fri, 26 May 2017 02:44:56 GMT):
```
root@ece5e733170f:/var/hyperledger/production/ledgersData/chains/chains/mychannel# ls -l
total 68
-rw-r----- 1 root root 61733 May 25 23:12 blockfile_000000
jimthematrix (Fri, 26 May 2017 02:48:39 GMT):
@aaronzheng affiliation在1.0里基本没什么用，因为还没有支持TCert，fabric-ca里用户的属性完全用不上。不过想设affiliation的话必须从fabric-ca-server-config.yaml里面先把affiliation设好，在运行时是不能添加或更改的，每个用户只能注册跟他同一个affiliation的新用户
aaronzheng (Fri, 26 May 2017 03:19:09 GMT):
@jimthematrix 感谢解释，非常完整！ 问多一个相关问题，为什么在发起install chaincode proposal的时候，不需要添加chaincode的endorsement policy，而是在instantiate proposal 的时候才添加。
jimthematrix (Fri, 26 May 2017 03:23:00 GMT):
endorsement policy是跟交易验证有关的，所以是从属于某个channel范围里面的，而install只是简单把chaincode上传到peer里，跟channel没有关系，必须等到instantiate（也是具体到channel）时才设置
tongli (Fri, 26 May 2017 03:32:43 GMT):
@jimthematrix good evening. want to throw an idea out there. wonder if it is all possible to take chaincode out of the fabric repository. seems to me that chaincode should be independent from fabric. or I miss something big.
jimthematrix (Fri, 26 May 2017 03:42:50 GMT):
@tongli this was discussed and it does make sense, just some work that requires a lot of work (severing inter-dependencies) that didn't get done
jimthematrix (Fri, 26 May 2017 03:43:09 GMT):
you should bring this up in #fabric-peer-endorser-committer channel
zhangchao (Fri, 26 May 2017 05:53:57 GMT):
有一点疑问，我们在java sdk里面获得某个块的data hash，跟下一个块的pre hash不一致，这个是怎么回事
tolak (Fri, 26 May 2017 06:26:12 GMT):
pre hash 好像是指上一区块区块头的hash，应该和它的data hash不一样。（我只是猜测，还得让大牛给确切回答:grimacing:）
cophey (Fri, 26 May 2017 06:39:59 GMT):
@baohua Update anchor peers这块是做什么的？之前就没看到生成的Org1MSPanchors.tx有什么用，在你这里看到了，不过还是没明白Update anchor peers的作用
cophey (Fri, 26 May 2017 06:40:05 GMT):
Message Attachments
baohua (Fri, 26 May 2017 06:47:11 GMT):
anchor 节点负责在两个组织之间进行 gossip 这里配置他们 让两个组织都可以彼此 gossip。
cophey (Fri, 26 May 2017 06:51:24 GMT):
我按照官网Getting Started上说明的，手动命令，也没有配置anchor，好像也没什么问题？
baohua (Fri, 26 May 2017 06:57:06 GMT):
如果不同组织之间不需要 gossip。则不受影响。
zhangchao (Fri, 26 May 2017 06:57:18 GMT):
难道data hash是另外的数据哈希吗
cophey (Fri, 26 May 2017 06:58:20 GMT):
@baohua 明白了，3Q~
chenxuan (Fri, 26 May 2017 07:14:36 GMT):
github.com/hyperledger/fabric-ca/vendor/github.com/mattn/go-sqlite3(.data.rel): unexpected R_X86_64_64 relocation for dynamic symbol close
chenxuan (Fri, 26 May 2017 07:14:39 GMT):
@baohua
chenxuan (Fri, 26 May 2017 07:14:55 GMT):
测试启动fabric-ca的时候
baohua (Fri, 26 May 2017 09:09:57 GMT):
我猜测是用的镜像有问题
grapebaba (Fri, 26 May 2017 09:14:02 GMT):
@jimthematrix 我看到configtx后面会暴露rest api，这个可以方便我们在程序中来调用；我想知道cryptogen后面有计划会暴露API吗
tolak (Fri, 26 May 2017 15:56:38 GMT):
在install chaincode fabric/examples/chaincode/go/chaincode_example02时，遇到这个error： “Error endorsing chaincode: rpc error: code = 2 desc = Error installing chaincode code test_cc:1.0(chaincode /var/hyperledger/production/chaincodes/test_cc.1.0 exists)” 可是/var/hyperledger/production/chaincodes/test_cc.1.0不存在。请问这会是其他什么原因导致的吗？
baohua (Sat, 27 May 2017 10:02:19 GMT):
这个是说你曾经在给定 peer 上安装过这个 cc 了，换个版本号试试
tolak (Sun, 28 May 2017 05:44:55 GMT):
ok
xuanchen (Mon, 29 May 2017 12:13:12 GMT):
Has joined the channel.
jimthematrix (Mon, 29 May 2017 23:22:34 GMT):
@zhangchao blockhash是hash（blocknumber + datahash + prevHash）： https://github.com/hyperledger/fabric-sdk-java/blob/master/src/main/java/org/hyperledger/fabric/sdk/SDKUtils.java#L47
Ainsight (Tue, 30 May 2017 11:04:09 GMT):
Has joined the channel.
chenxuan (Wed, 31 May 2017 01:09:53 GMT):
@zhangzhao
chenxuan (Wed, 31 May 2017 01:10:15 GMT):
看protos下面的proto文件就可以了
chenxuan (Wed, 31 May 2017 01:11:05 GMT):
我打算使用ｈｔｔｐ去访问ｃａ我看了一下接口要是授权是什么？
zhangchao (Wed, 31 May 2017 01:20:56 GMT):
thanks, @jimthematrix @chenxuan , it helps
baohua (Wed, 31 May 2017 02:04:45 GMT):
@chenxuan fabric ca 启动的时候如果没有进行任何配置的话 需要一个默认的用户名和密码进行初始化。否则任何人都没有权限添加注册了。
chenxuan (Wed, 31 May 2017 02:06:20 GMT):
我打算用ｈｔｔｐ去访问ｆａｂｒｉｃ的接口
chenxuan (Wed, 31 May 2017 02:06:35 GMT):
但是register 需要指定授权
chenxuan (Wed, 31 May 2017 02:06:37 GMT):
是什么意思
chenxuan (Wed, 31 May 2017 02:06:38 GMT):
？
chenxuan (Wed, 31 May 2017 02:09:07 GMT):
Message Attachments
baohua (Wed, 31 May 2017 02:10:54 GMT):
是的。restapi 需要带上验证信息，可以参考这里：https://github.com/hyperledger/fabric-ca/blob/master/swagger/swagger-fabric-ca.json
chenxuan (Wed, 31 May 2017 02:11:27 GMT):
我看的就是这个 需要带上的验证信息是什么
chenxuan (Wed, 31 May 2017 02:11:28 GMT):
？
chenxuan (Wed, 31 May 2017 02:11:31 GMT):
我没有看明白
chenxuan (Wed, 31 May 2017 02:15:06 GMT):
@jimthematrix
baohua (Wed, 31 May 2017 02:18:35 GMT):
http 请求的话 你得在头里面加token，填上证书和签名。这块目前没有文档。具体可以看 cli client 里面的实现 cmd/fabric-ca-client/register.go
xixuejia (Wed, 31 May 2017 02:21:33 GMT):
:muscle:
chenxuan (Wed, 31 May 2017 02:41:04 GMT):
＠baohua 怎么单独启动fabric-ca-server里面的main函数报错了
yong (Wed, 31 May 2017 03:52:39 GMT):
我使用fabri-ca生成orderer、peer和admin证书，同时参考example/e2e_cli。在执行peer channel join操作时，出现Error: proposal failed (err: rpc error: code = 2 desc = Failed to deserialize creator identity, err The supplied identity is not valid, Verify() returned x509: certificate signed by unknown authority)
Usage:
peer channel join [flags]
错误。
实在是找不到问题，请大家帮我看看，问题在哪儿
baohua (Thu, 01 Jun 2017 01:47:16 GMT):
出现这种情况 很可能是你本地默认的 msp 的身份并不是加入到通道中的组织的管理员。开 debug 模式查查看，另外查看下本地的 msp 路径
aaronzheng (Thu, 01 Jun 2017 02:01:02 GMT):
虽然问的是java-sdk，希望大神回答下。 困扰了我几小时了，我的cc已经安装了和初始化了，但用channel.sendTransaction后用thenApply进行查询，为什么thenApply里的代码debug不进去。
baohua (Thu, 01 Jun 2017 02:09:38 GMT):
抱歉 这个问题 可以到 #fabric-sdk-java 问一下
grapebaba (Thu, 01 Jun 2017 03:08:39 GMT):
@aaronzheng 这个是java的lambda的问题啊，调试不了
aaronzheng (Thu, 01 Jun 2017 03:24:07 GMT):
我已经找到问题原因啦。感谢各位。！
Donald Liu (Thu, 01 Jun 2017 04:09:51 GMT):
@aaronzheng 能分享一下原因吗？
aaronzheng (Thu, 01 Jun 2017 05:34:14 GMT):
@Donald Liu 要在channel添加eventHub，不然的话，是不会进入sendTransaction后的theApply的
Donald Liu (Thu, 01 Jun 2017 05:39:23 GMT):
OK，感谢！
yahtoo (Thu, 01 Jun 2017 06:54:01 GMT):
你好，问题合并到主分支了还可以使用git commit --amend 提交吗，还是新建一个问题？
baohua (Fri, 02 Jun 2017 01:40:08 GMT):
你说的是 patchset 吗？ 所有 patchset 无法直接往 master 提交的 所以建议新建 jira issue 和 patchset 进行提交。
chenxuan (Fri, 02 Jun 2017 02:17:10 GMT):
我看到最新的fabric当中出现了Org1MSPanchors.tx Org２MSPanchors.tx 我不知道这个是干嘛的,fabric-java-sdk应该怎么去处理
chenxuan (Fri, 02 Jun 2017 02:18:10 GMT):
@baohua
JasonD (Fri, 02 Jun 2017 02:19:26 GMT):
目前 1.0 是否有发布日期计划？
baohua (Fri, 02 Jun 2017 02:21:56 GMT):
suppose within this June
chenxuan (Fri, 02 Jun 2017 02:44:01 GMT):
@baohua
baohua (Fri, 02 Jun 2017 02:46:34 GMT):
aha，这两个文件是配置组织的锚节点用的。如果不做跨组织的交易，可以暂时忽略。
zhangmenghang (Fri, 02 Jun 2017 02:52:42 GMT):
创建通道时是否可以配置只允许某些组织只进行read操作之类的ACL？是在configtx.yaml里面配置吗？
zhangchao (Fri, 02 Jun 2017 06:43:40 GMT):
交易不应该都是跨组织的吗
zhangchao (Fri, 02 Jun 2017 06:45:23 GMT):
consortium blockchain不就是给组织之间提供交易的吗
baohua (Fri, 02 Jun 2017 09:21:03 GMT):
@here
Dear all, we will have group meeting at 10AM next Wednesday morning, pls help update the agenda/attendee at https://wiki.hyperledger.org/groups/twgc/meeting/2017-06-07, thanks!
xixuejia (Fri, 02 Jun 2017 15:30:14 GMT):
@zhangchao @chenxuan 那2个tx是更新anchor peer的，anchor peer用来做跨Organization gossip通信的
chenxuan (Sat, 03 Jun 2017 01:57:21 GMT):
@xixuejia 那怎么没看到使用呢
chenxuan (Sat, 03 Jun 2017 01:57:21 GMT):
？
xixuejia (Sat, 03 Jun 2017 02:00:02 GMT):
https://github.com/xixuejia/fabric/blob/master/examples/e2e_cli/scripts/script.sh#L70-L84
xixuejia (Sat, 03 Jun 2017 02:00:18 GMT):
@chenxuan 参考 e2e-cli
chenxuan (Sat, 03 Jun 2017 02:01:07 GMT):
看到了
yong (Sun, 04 Jun 2017 10:28:38 GMT):
执行peer chaincode instantiate后，在出现dev-peer0.org1.exapmles.com-wstcc-1.0 出现如下错误：
017-06-04 10:08:32.961 UTC [shim] Start -> ERRO 001 Error trying to connect to local peer: grpc: timed out when dialing
Error starting Simple chaincode: Error trying to connect to local peer: grpc: timed out when dialing
大家是怎么解决的？
xixuejia (Sun, 04 Jun 2017 13:21:35 GMT):
@yong 尝试把wstcc对应的docker image删除掉再试一下
yong (Sun, 04 Jun 2017 13:34:46 GMT):
试过了 还是不行
ydk210999 (Mon, 05 Jun 2017 03:18:07 GMT):
Has joined the channel.
ydk210999 (Mon, 05 Jun 2017 03:19:41 GMT):
请问下orderer集群有什么作用？
baohua (Mon, 05 Jun 2017 03:26:37 GMT):
Message Attachments
baohua (Mon, 05 Jun 2017 03:26:53 GMT):
Dear all, for the coming June hackfest, we setup a wechat group, welcome to join and register: https://www.regonline.com/hyperledgerhackfestjune2017
baohua (Mon, 05 Jun 2017 03:27:32 GMT):
@ydk210999 主要是完成排序的作用 将合法的交易分配全局顺序
chenxuan (Mon, 05 Jun 2017 06:38:49 GMT):
@baohua 我跑了fabric_java_sdk下面的那些测试 都是可以的 但是这里有一个问题 所有的证书都是在预先生成好的
chenxuan (Mon, 05 Jun 2017 06:39:12 GMT):
那在正式的环境上面 也是这么来做
chenxuan (Mon, 05 Jun 2017 06:39:13 GMT):
？
LordGoodman (Mon, 05 Jun 2017 09:57:32 GMT):
Has joined the channel.
yp (Mon, 05 Jun 2017 10:53:46 GMT):
跨通道
yong (Mon, 05 Jun 2017 11:05:38 GMT):
@here 每个合约docker里面有一个chaincode可执行程序，是怎么编译生成的啊,我看了下代码：
func (goPlatform *Platform) GenerateDockerBuild(cds *pb.ChaincodeDeploymentSpec, tw *tar.Writer) error {
spec := cds.ChaincodeSpec
pkgname, err := decodeUrl(spec)
if err != nil {
return fmt.Errorf("could not decode url: %s", err)
}
const ldflags = "-linkmode external -extldflags '-static'"
codepackage := bytes.NewReader(cds.CodePackage)
binpackage := bytes.NewBuffer(nil)
err = util.DockerBuild(util.DockerBuildOptions{
Cmd: fmt.Sprintf("GOPATH=/chaincode/input:$GOPATH go build -ldflags \"%s\" -o /chaincode/output/chaincode %s", ldflags, pkgname),
InputStream: codepackage,
OutputStream: binpackage,
})
if err != nil {
return err
}
return cutil.WriteBytesToPackage("binpackage.tar", binpackage.Bytes(), tw)
}
感觉是在上面的代码中生成的，但具体是编译哪儿的代码生成chaincode?另外，生成的chaincode程序主要做什么用，怎么调用对应的链上代码？
Honglei (Mon, 05 Jun 2017 11:06:44 GMT):
go build <<<< 这个命令编译的
yong (Mon, 05 Jun 2017 11:08:38 GMT):
是编译哪儿的代码？ @Honglei
Honglei (Mon, 05 Jun 2017 11:09:12 GMT):
GOPATH=/chaincode/input:
Honglei (Mon, 05 Jun 2017 11:09:37 GMT):
InputStream: codepackage
yong (Mon, 05 Jun 2017 11:10:59 GMT):
fabric目录下没找到GOPATH=/chaincode/input:这个目录啊
Honglei (Mon, 05 Jun 2017 11:11:37 GMT):
他在ccenv的docker里面编译的，这里是构造了一个docker命令，在线编译
yong (Mon, 05 Jun 2017 11:20:59 GMT):
@Honglei 具体是编译fabric目录下哪儿的代码啊？/chaincode/input目录下没有代码
yong (Mon, 05 Jun 2017 11:20:59 GMT):
@Honglei 谢谢
Honglei (Mon, 05 Jun 2017 23:58:18 GMT):
@yong InputStream: codepackage，tar包二进制传进去的
baohua (Tue, 06 Jun 2017 01:26:17 GMT):
@chenxuan 按照 pki 的做法，证书是要被 CA 签署然后分发的。
chenxuan (Tue, 06 Jun 2017 01:27:30 GMT):
但是e2e的例子当中都是使用fabric 源代码构建出来的工具去生成的
chenxuan (Tue, 06 Jun 2017 01:28:06 GMT):
我想的是 既然都有了ca 就不需要去这么做了
baohua (Tue, 06 Jun 2017 01:29:30 GMT):
cryptogen 是一次性本地构建好多。后面是可以用 fabric-ca 来做的。
chenxuan (Tue, 06 Jun 2017 01:31:28 GMT):
那我去试试直接使用ca 来产生cert
yong (Tue, 06 Jun 2017 02:59:29 GMT):
@here 执行peer chaincode install，在对应容器的/var/hyperledger/production/chaincodes下会生成mycc.1.0文件，这个文件起什么作用？
fengfengs (Tue, 06 Jun 2017 03:22:31 GMT):
Has joined the channel.
ydk210999 (Tue, 06 Jun 2017 04:20:40 GMT):
跨链
yong (Tue, 06 Jun 2017 05:31:20 GMT):
@ydk210999 你是mycc.1.0在跨链中起作用吗？具体期什么作用？
ydk210999 (Tue, 06 Jun 2017 05:32:16 GMT):
跨链是我不小心发送的，并不是回答你的问题。不好意思
ydk210999 (Tue, 06 Jun 2017 05:32:42 GMT):
@yong
yp (Tue, 06 Jun 2017 10:46:37 GMT):
@yong instantiate的时候那它去打包images，运行container
yong (Tue, 06 Jun 2017 10:48:03 GMT):
@yp 对应的代码实现在哪个文件？
yong (Tue, 06 Jun 2017 10:50:06 GMT):
@yp 在生成的合约容器中，我就找到了一个chaincode的命令，没见到mycc.1.0。是不是编译到chaincode命令中去了？
yp (Tue, 06 Jun 2017 10:50:34 GMT):
不记得了，应该在platform里面
yp (Tue, 06 Jun 2017 10:50:54 GMT):
到容器后不叫mycc
yp (Tue, 06 Jun 2017 10:59:39 GMT):
mycc.1.0 打包到image的时候，名字叫【chaincode】，不知道现在变没变
yp (Tue, 06 Jun 2017 11:00:04 GMT):
这种命名方式我也是醉了，以前都是拿hash的
yong (Tue, 06 Jun 2017 11:13:37 GMT):
嗯，现在是叫chaincode
yong (Tue, 06 Jun 2017 11:14:06 GMT):
什么hash?chaincode代码的hash吗？
yp (Tue, 06 Jun 2017 11:18:55 GMT):
嗯，以前是拿chaincode的hash 来作为容器里执行文件的名字的
yong (Tue, 06 Jun 2017 11:22:15 GMT):
哦，这样的哈
yong (Tue, 06 Jun 2017 11:23:50 GMT):
configuration transaction怎么产生的？是peer channel create产生的吗？
dinghaiyang (Wed, 07 Jun 2017 02:26:40 GMT):
Has joined the channel.
yahtoo (Wed, 07 Jun 2017 02:45:00 GMT):
@here 在fabric e2e example 加了四笔相同的交易，交易之间没加延时，查询交易结果是错的，加两秒延时结果也是错的，把延时到5秒结果才正确，这有可能是什么原因呢？
cophey (Wed, 07 Jun 2017 02:50:56 GMT):
@baohua 不好意思，刚刚突然断线了
baohua (Wed, 07 Jun 2017 02:52:07 GMT):
:) 有问题可以随时在这里讨论
baohua (Wed, 07 Jun 2017 02:52:20 GMT):
@yahtoo 查的是写入区块后的结果
cophey (Wed, 07 Jun 2017 02:54:06 GMT):
我们是不是要考虑1.0的blockchain-explorer做起来？这样的话，大家对fabric有个直观的印象。
baohua (Wed, 07 Jun 2017 02:56:15 GMT):
欢迎参与啊
cophey (Wed, 07 Jun 2017 03:05:02 GMT):
OK
zhangchao (Wed, 07 Jun 2017 03:26:49 GMT):
未来有没有可能在fabric的区块结构里面加入token的概念，以方便在交易里面使用数字货币体系，FAB里面有没有这样的提议
ydk210999 (Wed, 07 Jun 2017 07:02:54 GMT):
请问下configtx.ymal里关于batchsize的3个参数之间有什么关系？ MaxMessageCount，AbsoluteMaxBytes， PreferredMaxBytes
baohua (Wed, 07 Jun 2017 08:04:21 GMT): ydk210999 (Wed, 07 Jun 2017 08:22:14 GMT): baohua (Wed, 07 Jun 2017 08:35:26 GMT): ydk210999 (Wed, 07 Jun 2017 08:37:00 GMT): aaronzheng (Thu, 08 Jun 2017 03:00:29 GMT): zhangchao (Thu, 08 Jun 2017 06:50:31 GMT): CarlXK (Thu, 08 Jun 2017 08:17:45 GMT): guoger (Thu, 08 Jun 2017 08:24:50 GMT): baohua (Thu, 08 Jun 2017 11:52:22 GMT): baohua (Fri, 09 Jun 2017 01:26:19 GMT): aaronzheng (Fri, 09 Jun 2017 01:31:38 GMT): chenxuan (Fri, 09 Jun 2017 06:55:36 GMT): aaronzheng (Fri, 09 Jun 2017 06:57:12 GMT): chenxuan (Fri, 09 Jun 2017 07:31:12 GMT): chenxuan (Fri, 09 Jun 2017 08:20:38 GMT): chenxuan (Fri, 09 Jun 2017 08:20:50 GMT): chenxuan (Fri, 09 Jun 2017 08:21:08 GMT): chenxuan (Fri, 09 Jun 2017 11:36:09 GMT): chenxuan (Fri, 09 Jun 2017 11:36:54 GMT): chenxuan (Fri, 09 Jun 2017 11:37:31 GMT): chenxuan (Fri, 09 Jun 2017 11:39:12 GMT): baohua (Fri, 09 Jun 2017 14:03:10 GMT): zhangchao (Mon, 12 Jun 2017 03:22:26 GMT): CarlXK (Mon, 12 Jun 2017 04:02:43 GMT): jimthematrix (Mon, 12 Jun 2017 16:31:50 GMT): jimthematrix (Mon, 12 Jun 2017 16:31:50 GMT): jimthematrix (Mon, 12 Jun 2017 16:40:31 GMT): zhangchao (Tue, 13 Jun 2017 01:22:56 GMT): jimthematrix (Tue, 13 Jun 2017 01:54:44 GMT): daijianw (Tue, 13 Jun 2017 01:55:42 GMT): zhangchao (Tue, 13 Jun 2017 01:57:33 GMT): zhangchao (Tue, 13 Jun 2017 01:58:17 GMT): CarlXK (Tue, 13 Jun 2017 02:14:38 GMT): CarlXK (Tue, 13 Jun 2017 02:14:38 GMT): jimthematrix (Tue, 13 Jun 2017 02:18:39 GMT): jimthematrix (Tue, 13 Jun 2017 02:18:39 GMT): jimthematrix (Tue, 13 Jun 2017 02:18:39 GMT): jimthematrix (Tue, 13 Jun 2017 02:18:39 GMT): jimthematrix (Tue, 13 Jun 2017 02:19:59 GMT): CarlXK (Tue, 13 Jun 2017 02:20:11 GMT): jimthematrix (Tue, 13 Jun 2017 02:23:28 GMT): zhangchao (Tue, 13 Jun 2017 03:08:33 GMT): zhangchao (Tue, 13 Jun 2017 03:09:20 GMT): jimthematrix (Tue, 13 Jun 2017 03:11:39 GMT): jimthematrix (Tue, 13 Jun 2017 03:13:04 GMT): zhangchao (Tue, 13 Jun 2017 03:13:50 GMT): CarlXK (Tue, 13 Jun 2017 03:53:39 GMT): CarlXK (Tue, 13 Jun 2017 03:53:39 GMT): Glen (Tue, 13 Jun 2017 07:06:14 GMT): baohua (Wed, 14 Jun 2017 01:55:10 GMT): baohua (Wed, 14 Jun 2017 01:58:17 GMT): dinghaiyang (Wed, 14 Jun 2017 03:04:38 GMT): chenxuan (Wed, 14 Jun 2017 07:09:37 GMT): chenxuan (Wed, 14 Jun 2017 07:09:51 GMT): yahtoo (Wed, 14 Jun 2017 08:19:02 GMT): baohua (Wed, 14 Jun 2017 08:19:10 GMT): yahtoo (Wed, 14 Jun 2017 08:19:49 GMT): yahtoo (Wed, 14 Jun 2017 08:20:13 GMT): baohua (Wed, 14 Jun 2017 08:25:43 GMT): liuwenliang0632 (Wed, 14 Jun 2017 08:43:17 GMT): qiushaoxi (Wed, 14 Jun 2017 08:45:33 GMT): yahtoo (Wed, 14 Jun 2017 08:49:41 GMT): barry_liang (Wed, 14 Jun 2017 08:54:12 GMT): allensoaring (Wed, 14 Jun 2017 09:02:17 GMT): barry_liang (Wed, 14 Jun 2017 09:03:42 GMT): kyle1234 (Thu, 15 Jun 2017 01:11:30 GMT): j3ffyang (Thu, 15 Jun 2017 03:28:26 GMT): chenxuan (Thu, 15 Jun 2017 07:55:29 GMT): chenxuan (Thu, 15 Jun 2017 07:56:18 GMT): chenxuan (Thu, 15 Jun 2017 07:56:31 GMT): chenxuan (Thu, 15 Jun 2017 07:57:21 GMT): chenxuan (Thu, 15 Jun 2017 07:57:39 GMT): chenxuan (Thu, 15 Jun 2017 07:59:08 GMT): chenxuan (Thu, 15 Jun 2017 08:03:40 GMT): HuangLijun (Thu, 15 Jun 2017 08:16:16 GMT): HuangLijun (Thu, 15 Jun 2017 08:22:33 GMT): HuangLijun (Thu, 15 Jun 2017 08:22:33 GMT): chenxuan (Thu, 15 Jun 2017 08:24:26 GMT): HuangLijun (Thu, 15 Jun 2017 08:24:35 GMT): HuangLijun (Thu, 15 Jun 2017 08:24:47 GMT): HuangLijun (Thu, 15 Jun 2017 08:24:47 GMT): chenxuan (Thu, 15 Jun 2017 08:28:46 GMT): chenxuan (Thu, 15 Jun 2017 08:28:59 GMT): HuangLijun (Thu, 15 Jun 2017 08:30:11 GMT): guoger (Thu, 15 Jun 2017 08:37:46 GMT): guoger (Thu, 15 Jun 2017 08:38:25 GMT): chenxuan (Thu, 15 Jun 2017 08:47:37 GMT): chenxuan (Thu, 15 Jun 2017 08:47:46 GMT): chenxuan (Thu, 15 Jun 2017 08:47:54 GMT): guoger (Thu, 15 Jun 2017 08:48:16 GMT): guoger (Thu, 15 Jun 2017 08:48:22 GMT): chenxuan (Thu, 15 Jun 2017 08:49:09 GMT): chenxuan (Thu, 15 Jun 2017 08:49:13 GMT): guoger (Thu, 15 Jun 2017 08:50:12 GMT): guoger (Thu, 15 Jun 2017 08:50:12 GMT): chenxuan (Thu, 15 Jun 2017 08:50:36 GMT): chenxuan (Thu, 15 Jun 2017 08:50:50 GMT): chenxuan (Thu, 15 Jun 2017 08:51:07 GMT): guoger (Thu, 15 Jun 2017 08:53:05 GMT): HuangLijun (Thu, 15 Jun 2017 08:56:22 GMT): chenxuan (Thu, 15 Jun 2017 09:03:03 GMT): chenxuan (Thu, 15 Jun 2017 09:03:11 GMT): chenxuan (Thu, 15 Jun 2017 09:07:28 GMT): qiushaoxi (Thu, 15 Jun 2017 09:25:01 GMT): chenxuan (Thu, 15 Jun 2017 09:25:19 GMT): qiushaoxi (Thu, 15 Jun 2017 09:26:00 GMT): qiushaoxi (Thu, 15 Jun 2017 09:26:05 GMT): chenxuan (Thu, 15 Jun 2017 09:37:17 GMT): chenxuan (Thu, 15 Jun 2017 09:37:23 GMT): qiushaoxi (Thu, 15 Jun 2017 09:37:39 GMT): qiushaoxi (Thu, 15 Jun 2017 09:37:46 GMT): chenxuan (Thu, 15 Jun 2017 09:38:29 GMT): chenxuan (Thu, 15 Jun 2017 11:10:02 GMT): chenxuan (Thu, 15 Jun 2017 11:10:10 GMT): chenxuan (Thu, 15 Jun 2017 11:14:36 GMT): tolak (Thu, 15 Jun 2017 11:48:46 GMT): tolak (Thu, 15 Jun 2017 11:49:44 GMT): laxpio (Thu, 15 Jun 2017 12:40:59 GMT): JohnMoss (Fri, 16 Jun 2017 00:53:01 GMT): chenxuan (Fri, 16 Jun 2017 01:30:51 GMT): chenxuan (Fri, 16 Jun 2017 01:31:11 GMT): chenxuan (Fri, 16 Jun 2017 01:54:57 GMT): chenxuan (Fri, 16 Jun 2017 01:56:12 GMT): chenxuan (Fri, 16 Jun 2017 01:56:23 GMT): baohua (Fri, 16 Jun 2017 01:57:37 GMT): qiushaoxi (Fri, 16 Jun 2017 01:57:57 GMT): qiushaoxi (Fri, 16 Jun 2017 01:58:01 GMT): baohua (Fri, 16 Jun 2017 01:58:20 GMT): baohua (Fri, 16 Jun 2017 01:58:40 GMT): qiushaoxi (Fri, 16 Jun 2017 01:59:19 GMT): qiushaoxi (Fri, 16 Jun 2017 01:59:22 GMT): baohua (Fri, 16 Jun 2017 01:59:45 GMT): chenxuan (Fri, 16 Jun 2017 02:00:38 GMT): chenxuan (Fri, 16 Jun 2017 02:00:56 GMT): chenxuan (Fri, 16 Jun 2017 02:01:26 GMT): chenxuan (Fri, 16 Jun 2017 02:01:44 GMT): chenxuan (Fri, 16 Jun 2017 02:02:05 GMT): chenxuan (Fri, 16 Jun 2017 02:02:54 GMT): chenxuan (Fri, 16 Jun 2017 02:03:41 GMT): baohua (Fri, 16 Jun 2017 02:12:29 GMT): chenxuan (Fri, 16 Jun 2017 02:13:07 GMT): chenxuan (Fri, 16 Jun 2017 02:13:29 GMT): daijianw (Fri, 16 Jun 2017 02:57:28 GMT): baohua (Fri, 16 Jun 2017 02:58:35 GMT): daijianw (Fri, 16 Jun 2017 02:58:50 GMT): baohua (Fri, 16 Jun 2017 02:58:53 GMT): daijianw (Fri, 16 Jun 2017 02:59:10 GMT): qiang0723 (Fri, 16 Jun 2017 03:22:01 GMT): caoyu (Fri, 16 Jun 2017 03:25:06 GMT): chenxuan (Fri, 16 Jun 2017 03:49:13 GMT): chenxuan (Fri, 16 Jun 2017 03:50:16 GMT): chenxuan (Fri, 16 Jun 2017 03:50:36 GMT): chenxuan (Fri, 16 Jun 2017 03:50:45 GMT): chenxuan (Fri, 16 Jun 2017 03:51:16 GMT): baohua (Fri, 16 Jun 2017 04:00:26 GMT): baohua (Fri, 16 Jun 2017 04:00:26 GMT): baohua (Fri, 16 Jun 2017 04:00:26 GMT): chenxuan (Fri, 16 Jun 2017 04:18:02 GMT): chenxuan (Fri, 16 Jun 2017 04:18:09 GMT): chenxuan (Fri, 16 Jun 2017 05:00:49 GMT): chenxuan (Fri, 16 Jun 2017 05:00:53 GMT): chenxuan (Fri, 16 Jun 2017 05:00:54 GMT): jimthematrix (Fri, 16 Jun 2017 13:51:00 GMT): jimthematrix (Fri, 16 Jun 2017 13:51:00 GMT): jimthematrix (Fri, 16 Jun 2017 13:52:34 GMT): jimthematrix (Fri, 16 Jun 2017 13:57:53 GMT): jimthematrix (Fri, 16 Jun 2017 13:58:51 GMT): jimthematrix (Fri, 16 Jun 2017 14:00:48 GMT): dongming (Fri, 16 Jun 2017 14:00:48 GMT): chenxuan (Sat, 17 Jun 2017 01:43:48 GMT): chenxuan (Sat, 17 Jun 2017 01:44:24 GMT): chenxuan (Sat, 17 Jun 2017 03:10:29 GMT): chenxuan (Sat, 17 Jun 2017 03:10:40 GMT): chenxuan (Sat, 17 Jun 2017 03:10:58 GMT): chenxuan (Sat, 17 Jun 2017 03:11:33 GMT): chenxuan (Sat, 17 Jun 2017 03:11:45 GMT): chenxuan (Sat, 17 Jun 2017 03:12:04 GMT): chenxuan (Sat, 17 Jun 2017 03:12:20 GMT): chenxuan (Sat, 17 Jun 2017 03:12:36 GMT): chenxuan (Sat, 17 Jun 2017 03:12:44 GMT): chenxuan (Sat, 17 Jun 2017 03:13:40 GMT): chenxuan (Sat, 17 Jun 2017 03:14:01 GMT): chenxuan (Sat, 17 Jun 2017 03:14:13 GMT): chenxuan (Sat, 17 Jun 2017 03:14:25 GMT): tolak (Sat, 17 Jun 2017 14:39:56 GMT): tolak (Sat, 17 Jun 2017 14:40:13 GMT): tolak (Sun, 18 Jun 2017 02:48:30 GMT): tolak (Sun, 18 Jun 2017 02:48:39 GMT): tolak (Sun, 18 Jun 2017 04:02:05 GMT): tolak (Sun, 18 Jun 2017 04:02:45 GMT): tolak (Sun, 18 Jun 2017 04:09:46 GMT): bluefireH (Sun, 18 Jun 2017 09:08:37 GMT): chenxuan (Sun, 18 Jun 2017 12:08:16 GMT): chenxuan (Sun, 18 Jun 2017 12:09:43 GMT): baohua (Sun, 18 Jun 2017 12:21:56 GMT): baohua (Mon, 19 Jun 2017 01:26:53 GMT): baohua (Mon, 19 Jun 2017 01:27:10 GMT): baohua (Mon, 19 Jun 2017 01:27:10 GMT): baohua (Mon, 19 Jun 2017 02:12:35 GMT): jimthematrix (Mon, 19 Jun 2017 02:26:10 GMT): manish-sethi (Mon, 19 Jun 2017 02:26:10 GMT): dave.enyeart (Mon, 19 Jun 2017 02:26:10 GMT): chenxuan (Mon, 19 Jun 2017 02:26:50 GMT): jimthematrix (Mon, 19 Jun 2017 02:32:01 GMT): chenxuan (Mon, 19 Jun 2017 02:45:16 GMT): chenxuan (Mon, 19 Jun 2017 02:45:34 GMT): chenxuan (Mon, 19 Jun 2017 02:53:40 GMT): chenxuan (Mon, 19 Jun 2017 02:54:21 GMT): fengfengs (Mon, 19 Jun 2017 03:00:51 GMT): jimthematrix (Mon, 19 Jun 2017 03:05:40 GMT): chenxuan (Mon, 19 Jun 2017 03:06:56 GMT): jimthematrix (Mon, 19 Jun 2017 03:08:36 GMT): jimthematrix (Mon, 19 Jun 2017 03:09:32 GMT): chenxuan (Mon, 19 Jun 2017 03:10:45 GMT): chenxuan (Mon, 19 Jun 2017 03:10:45 GMT): chenxuan (Mon, 19 Jun 2017 03:27:51 GMT): tolak (Mon, 19 Jun 2017 03:29:32 GMT): tolak (Mon, 19 Jun 2017 03:29:35 GMT): chenxuan (Mon, 19 Jun 2017 03:29:47 GMT): tolak (Mon, 19 Jun 2017 03:29:56 GMT): tolak (Mon, 19 Jun 2017 03:29:59 GMT): chenxuan (Mon, 19 Jun 2017 04:03:38 GMT): chenxuan (Mon, 19 Jun 2017 04:04:13 GMT): chenxuan (Mon, 19 Jun 2017 04:07:53 GMT): chenxuan (Mon, 19 Jun 2017 04:09:18 GMT): chenxuan (Mon, 19 Jun 2017 04:15:14 GMT): chenxuan (Mon, 19 Jun 2017 05:25:17 GMT): chenxuan (Mon, 19 Jun 2017 05:25:29 GMT): chenxuan (Mon, 19 Jun 2017 05:25:44 GMT): chenxuan (Mon, 19 Jun 2017 05:25:50 GMT): VickyWang (Mon, 19 Jun 2017 05:26:14 GMT): guoger (Mon, 19 Jun 2017 06:09:59 GMT): zhangmenghang (Mon, 19 Jun 2017 06:10:08 GMT): guoger (Mon, 19 Jun 2017 06:10:19 GMT): guoger (Mon, 19 Jun 2017 06:10:22 GMT): guoger (Mon, 19 Jun 2017 06:10:23 GMT): guoger (Mon, 19 Jun 2017 06:10:25 GMT): chenxuan (Mon, 19 Jun 2017 06:10:46 GMT): baohua (Mon, 19 Jun 2017 07:56:24 GMT): baohua (Mon, 19 Jun 2017 07:56:42 GMT): baohua (Mon, 19 Jun 2017 07:57:00 GMT): baohua (Mon, 19 Jun 2017 07:57:07 GMT): baohua (Mon, 19 Jun 2017 07:57:13 GMT): baohua (Mon, 19 Jun 2017 07:57:22 GMT): chenxuan (Mon, 19 Jun 2017 08:59:09 GMT): chenxuan (Mon, 19 Jun 2017 08:59:47 GMT): chenxuan (Mon, 19 Jun 2017 09:01:39 GMT): chenxuan (Mon, 19 Jun 2017 09:01:48 GMT): chenxuan (Mon, 19 Jun 2017 09:34:36 GMT): chenxuan (Mon, 19 Jun 2017 09:37:02 GMT): VickyWang (Mon, 19 Jun 2017 09:49:34 GMT): VickyWang (Mon, 19 Jun 2017 09:49:34 GMT): chenxuan (Mon, 19 Jun 2017 09:58:21 GMT): chenxuan (Mon, 19 Jun 2017 09:58:32 GMT): chenxuan (Mon, 19 Jun 2017 09:58:42 GMT): chenxuan (Mon, 19 Jun 2017 09:58:46 GMT): baohua (Mon, 19 Jun 2017 10:02:58 GMT): baohua (Mon, 19 Jun 2017 10:03:15 GMT): chenxuan (Mon, 19 Jun 2017 10:06:15 GMT): chenxuan (Mon, 19 Jun 2017 10:06:50 GMT): chenxuan (Mon, 19 Jun 2017 10:06:52 GMT): chenxuan (Mon, 19 Jun 2017 10:07:23 GMT): chenxuan (Mon, 19 Jun 2017 10:07:49 GMT): chenxuan (Mon, 19 Jun 2017 10:08:01 GMT): chenxuan (Mon, 19 Jun 2017 10:08:15 GMT): chenxuan (Mon, 19 Jun 2017 10:08:35 GMT): chenxuan (Mon, 19 Jun 2017 10:08:39 GMT): chenxuan (Mon, 19 Jun 2017 10:08:56 GMT): chenxuan (Mon, 19 Jun 2017 10:09:02 GMT): chenxuan (Mon, 19 Jun 2017 10:11:40 GMT): chenxuan (Mon, 19 Jun 2017 10:11:44 GMT): tolak (Mon, 19 Jun 2017 10:28:04 GMT): chenxuan (Mon, 19 Jun 2017 10:34:50 GMT): baohua (Mon, 19 Jun 2017 10:35:33 GMT): chenxuan (Mon, 19 Jun 2017 10:38:44 GMT): chenxuan (Mon, 19 Jun 2017 10:46:19 GMT): chenxuan (Mon, 19 Jun 2017 10:46:26 GMT): chenxuan (Mon, 19 Jun 2017 10:46:31 GMT): chenxuan (Mon, 19 Jun 2017 10:57:37 GMT): chenxuan (Mon, 19 Jun 2017 10:58:44 GMT): chenxuan (Mon, 19 Jun 2017 10:58:45 GMT): chenxuan (Mon, 19 Jun 2017 10:58:50 GMT): baohua (Mon, 19 Jun 2017 12:43:23 GMT): mwagner (Mon, 19 Jun 2017 15:00:25 GMT): tolak (Mon, 19 Jun 2017 15:03:23 GMT): tolak (Mon, 19 Jun 2017 15:03:29 GMT): baohua (Mon, 19 Jun 2017 15:09:58 GMT): tolak (Mon, 19 Jun 2017 15:21:24 GMT): yahtoo (Tue, 20 Jun 2017 00:24:42 GMT): VickyWang (Tue, 20 Jun 2017 01:03:10 GMT): baohua (Tue, 20 Jun 2017 01:11:00 GMT): chenxuan (Tue, 20 Jun 2017 01:21:07 GMT): VickyWang (Tue, 20 Jun 2017 01:39:49 GMT): yahtoo (Tue, 20 Jun 2017 01:41:21 GMT): yahtoo (Tue, 20 Jun 2017 01:41:24 GMT): chenxuan (Tue, 20 Jun 2017 01:51:34 GMT): chenxuan (Tue, 20 Jun 2017 01:51:38 GMT): chenxuan (Tue, 20 Jun 2017 01:54:39 GMT): chenxuan (Tue, 20 Jun 2017 01:54:48 GMT): VickyWang (Tue, 20 Jun 2017 02:03:53 GMT): VickyWang (Tue, 20 Jun 2017 02:05:49 GMT): aarenw (Tue, 20 Jun 2017 04:07:50 GMT): zhuxubin01 (Tue, 20 Jun 2017 05:38:41 GMT): dongqi (Tue, 20 Jun 2017 08:42:11 GMT): baohua (Tue, 20 Jun 2017 10:21:44 GMT): tolak (Tue, 20 Jun 2017 10:26:07 GMT): chenxuan (Tue, 20 Jun 2017 11:52:15 GMT): chenxuan (Tue, 20 Jun 2017 11:52:24 GMT): chenxuan (Tue, 20 Jun 2017 12:19:10 GMT): chenxuan (Tue, 20 Jun 2017 12:19:13 GMT): chenxuan (Tue, 20 Jun 2017 12:19:33 GMT): chenxuan (Tue, 20 Jun 2017 12:19:45 GMT): chenxuan (Tue, 20 Jun 2017 12:20:25 GMT): chenxuan (Tue, 20 Jun 2017 12:20:39 GMT): chenxuan (Tue, 20 Jun 2017 12:20:53 GMT): jimthematrix (Tue, 20 Jun 2017 14:54:32 GMT): xuanchen (Tue, 20 Jun 2017 15:19:24 GMT): baohua (Wed, 21 Jun 2017 01:55:07 GMT): baohua (Wed, 21 Jun 2017 01:55:12 GMT): baohua (Wed, 21 Jun 2017 01:55:15 GMT): baohua (Wed, 21 Jun 2017 01:55:18 GMT): CarlXK (Wed, 21 Jun 2017 02:57:21 GMT): yahtoo (Wed, 21 Jun 2017 08:21:57 GMT): CarlXK (Wed, 21 Jun 2017 08:26:03 GMT): yahtoo (Thu, 22 Jun 2017 07:45:48 GMT): baohua (Thu, 22 Jun 2017 07:51:35 GMT): yahtoo (Thu, 22 Jun 2017 07:59:23 GMT): jchenibm (Thu, 22 Jun 2017 14:55:19 GMT): tolak (Thu, 22 Jun 2017 16:38:53 GMT): baohua (Fri, 23 Jun 2017 01:15:31 GMT): baohua (Fri, 23 Jun 2017 01:15:31 GMT): liuwenliang0632 (Fri, 23 Jun 2017 02:14:24 GMT): tolak (Fri, 23 Jun 2017 02:41:03 GMT): tolak (Fri, 23 Jun 2017 02:42:17 GMT): zhangchao (Fri, 23 Jun 2017 03:40:50 GMT): zhangchao (Fri, 23 Jun 2017 03:44:16 GMT): Claude-ZHENG (Fri, 23 Jun 2017 05:38:47 GMT): Claude-ZHENG (Fri, 23 Jun 2017 05:47:50 GMT): davidkhala (Fri, 23 Jun 2017 08:01:36 GMT): davidkhala (Fri, 23 Jun 2017 08:10:15 GMT): aaronzheng (Fri, 23 Jun 2017 08:16:53 GMT): kevinsong (Fri, 23 Jun 2017 09:17:07 GMT): tolak (Fri, 23 Jun 2017 09:30:56 GMT): tolak (Fri, 23 Jun 2017 09:31:05 GMT): tolak (Fri, 23 Jun 2017 09:31:55 GMT): tolak (Fri, 23 Jun 2017 11:43:49 GMT): tolak (Fri, 23 Jun 2017 11:44:42 GMT): tolak (Fri, 23 Jun 2017 11:44:42 GMT): tolak (Fri, 23 Jun 2017 11:46:02 GMT): baohua (Fri, 23 Jun 2017 15:08:24 GMT): tolak (Sat, 24 Jun 2017 03:01:17 GMT): tolak (Sat, 24 Jun 2017 03:02:45 GMT): jiangyaoguo (Sat, 24 Jun 2017 07:09:30 GMT): jiangyaoguo (Sat, 24 Jun 2017 07:09:35 GMT): tolak (Sat, 24 Jun 2017 08:47:20 GMT): tolak (Sat, 24 Jun 2017 08:47:55 GMT): tolak (Sat, 24 Jun 2017 08:48:28 GMT): jiangyaoguo (Sat, 24 Jun 2017 09:27:29 GMT): tolak (Sat, 24 Jun 2017 14:28:01 GMT): tolak (Sat, 24 Jun 2017 14:28:42 GMT): chenxuan (Mon, 26 Jun 2017 02:23:21 GMT): chenxuan (Mon, 26 Jun 2017 02:23:27 GMT): chenxuan (Mon, 26 Jun 2017 02:23:32 GMT): chenxuan (Mon, 26 Jun 2017 02:23:35 GMT): baoyangc (Mon, 26 Jun 2017 02:33:10 GMT): liuwenliang0632 (Mon, 26 Jun 2017 03:32:03 GMT): baoyangc (Mon, 26 Jun 2017 05:49:48 GMT): baoyangc (Mon, 26 Jun 2017 05:49:54 GMT): baoyangc (Mon, 26 Jun 2017 05:50:43 GMT): davidkhala (Mon, 26 Jun 2017 06:00:39 GMT): chenxuan (Mon, 26 Jun 2017 07:11:36 GMT): chenxuan (Mon, 26 Jun 2017 07:11:39 GMT): chenxuan (Mon, 26 Jun 2017 07:11:44 GMT): baoyangc (Mon, 26 Jun 2017 07:44:07 GMT): zuowang (Mon, 26 Jun 2017 07:50:42 GMT): aaronzheng (Mon, 26 Jun 2017 07:58:30 GMT): baoyangc (Mon, 26 Jun 2017 09:46:56 GMT): baoyangc (Mon, 26 Jun 2017 09:47:12 GMT): baoyangc (Mon, 26 Jun 2017 09:47:28 GMT): tolak (Mon, 26 Jun 2017 12:50:35 GMT): baohua (Mon, 26 Jun 2017 14:32:55 GMT): chenxuan (Mon, 26 Jun 2017 15:04:13 GMT): yahtoo (Tue, 27 Jun 2017 04:01:54 GMT): liuwenliang0632 (Tue, 27 Jun 2017 04:08:45 GMT): yahtoo (Tue, 27 Jun 2017 06:54:02 GMT): yahtoo (Tue, 27 Jun 2017 06:54:19 GMT): yahtoo (Tue, 27 Jun 2017 06:55:18 GMT): liuwenliang0632 (Tue, 27 Jun 2017 08:04:14 GMT): yahtoo (Tue, 27 Jun 2017 08:13:19 GMT): tolak (Tue, 27 Jun 2017 09:21:53 GMT): chenxuan (Tue, 27 Jun 2017 10:09:55 GMT): tolak (Tue, 27 Jun 2017 11:14:29 GMT): baoyangc (Tue, 27 Jun 2017 16:25:08 GMT): baoyangc (Tue, 27 Jun 2017 16:25:12 GMT): baoyangc (Tue, 27 Jun 2017 16:25:17 GMT): baoyangc (Tue, 27 Jun 2017 16:26:06 GMT): baoyangc (Tue, 27 Jun 2017 16:27:06 GMT): baoyangc (Tue, 27 Jun 2017 16:27:17 GMT): baoyangc (Tue, 27 Jun 2017 16:28:40 GMT): baoyangc (Tue, 27 Jun 2017 16:29:21 GMT): baoyangc (Tue, 27 Jun 2017 16:30:02 GMT): baoyangc (Tue, 27 Jun 2017 16:30:31 GMT): davidkhala (Wed, 28 Jun 2017 02:33:51 GMT): davidkhala (Wed, 28 Jun 2017 02:36:58 GMT): baoyangc (Wed, 28 Jun 2017 02:38:27 GMT): davidkhala (Wed, 28 Jun 2017 03:12:13 GMT): baoyangc (Wed, 28 Jun 2017 05:13:56 GMT): baoyangc (Wed, 28 Jun 2017 05:14:01 GMT): davidkhala (Wed, 28 Jun 2017 05:42:50 GMT): baoyangc (Wed, 28 Jun 2017 06:25:21 GMT): qiushaoxi (Wed, 28 Jun 2017 07:48:05 GMT): baoyangc (Thu, 29 Jun 2017 01:22:22 GMT): baoyangc (Thu, 29 Jun 2017 01:22:37 GMT): baoyangc (Thu, 29 Jun 2017 01:23:05 GMT): tolak (Thu, 29 Jun 2017 01:24:53 GMT): baoyangc (Thu, 29 Jun 2017 01:34:26 GMT): baoyangc (Thu, 29 Jun 2017 01:34:32 GMT): baoyangc (Thu, 29 Jun 2017 02:17:01 GMT): baoyangc (Thu, 29 Jun 2017 02:17:23 GMT): tolak (Thu, 29 Jun 2017 03:15:32 GMT): Claude-ZHENG (Thu, 29 Jun 2017 07:51:54 GMT): zhangchao (Fri, 30 Jun 2017 00:45:29 GMT): xixuejia (Fri, 30 Jun 2017 01:16:42 GMT): zhangchao (Fri, 30 Jun 2017 01:22:19 GMT): zhangchao (Fri, 30 Jun 2017 01:22:38 GMT): zhangchao (Fri, 30 Jun 2017 01:25:46 GMT): xixuejia (Fri, 30 Jun 2017 02:13:39 GMT): baoyangc (Sat, 01 Jul 2017 15:50:08 GMT): baoyangc (Sun, 02 Jul 2017 06:39:57 GMT): baoyangc (Sun, 02 Jul 2017 06:40:06 GMT): baoyangc (Sun, 02 Jul 2017 06:40:13 GMT): baohua (Mon, 03 Jul 2017 02:36:11 GMT): qiushaoxi (Mon, 03 Jul 2017 09:31:50 GMT): baoyangc (Tue, 04 Jul 2017 05:08:05 GMT): CarlXK (Tue, 04 Jul 2017 07:28:25 GMT): baohua (Wed, 05 Jul 2017 01:29:21 GMT): baohua (Wed, 05 Jul 2017 01:52:39 GMT): baohua (Wed, 05 Jul 2017 02:01:42 GMT): chenxuan (Wed, 05 Jul 2017 02:16:00 GMT): CarlXK (Wed, 05 Jul 2017 02:23:38 GMT): baohua (Wed, 05 Jul 2017 02:40:07 GMT): baohua (Wed, 05 Jul 2017 02:40:37 GMT): CarlXK (Wed, 05 Jul 2017 06:19:30 GMT): baohua (Wed, 05 Jul 2017 09:09:43 GMT): pandabcai (Wed, 05 Jul 2017 18:27:06 GMT): tongli (Wed, 05 Jul 2017 23:07:44 GMT): tongli (Wed, 05 Jul 2017 23:09:28 GMT): zhuxubin01 (Thu, 06 Jul 2017 02:20:40 GMT): zhuxubin01 (Thu, 06 Jul 2017 02:21:00 GMT): jiangyaoguo (Thu, 06 Jul 2017 03:16:07 GMT): jiangyaoguo (Thu, 06 Jul 2017 03:16:20 GMT): zhuxubin01 (Thu, 06 Jul 2017 03:25:42 GMT): hei 48 (Thu, 06 Jul 2017 04:50:38 GMT): bluecrayon52 (Thu, 06 Jul 2017 14:02:47 GMT): gloriow (Fri, 07 Jul 2017 01:56:42 GMT): ylsGit (Fri, 07 Jul 2017 06:30:37 GMT): xixuejia (Fri, 07 Jul 2017 06:44:31 GMT): xixuejia (Fri, 07 Jul 2017 06:45:10 GMT): ylsGit (Fri, 07 Jul 2017 06:45:16 GMT): xixuejia (Fri, 07 Jul 2017 06:45:35 GMT): ylsGit (Fri, 07 Jul 2017 06:45:41 GMT): ylsGit (Fri, 07 Jul 2017 06:46:06 GMT): xixuejia (Fri, 07 Jul 2017 06:47:26 GMT): xixuejia (Fri, 07 Jul 2017 06:48:26 GMT): ylsGit (Fri, 07 Jul 2017 06:49:10 GMT): xixuejia (Fri, 07 Jul 2017 06:49:41 GMT): ylsGit (Fri, 07 Jul 2017 06:49:55 GMT): xixuejia (Fri, 07 Jul 2017 06:50:07 GMT): xixuejia (Fri, 07 Jul 2017 06:50:47 GMT): ylsGit (Fri, 07 Jul 2017 06:50:57 GMT): ylsGit (Fri, 07 Jul 2017 06:51:07 GMT): ylsGit (Fri, 07 Jul 2017 07:15:58 GMT): baoyangc (Fri, 07 Jul 2017 10:11:11 GMT): baoyangc (Fri, 07 Jul 2017 10:11:32 GMT): baoyangc (Fri, 07 Jul 2017 10:11:52 GMT): wangheng (Sun, 09 Jul 2017 08:07:20 GMT): daijianw (Mon, 10 Jul 2017 08:01:59 GMT): baoyangc (Tue, 11 Jul 2017 07:10:26 GMT): CarlXK (Tue, 11 Jul 2017 12:47:52 GMT): tongli (Tue, 11 Jul 2017 13:39:45 GMT): tongli (Tue, 11 Jul 2017 13:40:10 GMT): tongli (Tue, 11 Jul 2017 13:41:00 GMT): CarlXK (Tue, 11 Jul 2017 13:53:25 GMT): tongli (Tue, 11 Jul 2017 13:54:19 GMT): tongli (Tue, 11 Jul 2017 13:54:40 GMT): tongli (Tue, 11 Jul 2017 13:54:48 GMT): tongli (Tue, 11 Jul 2017 13:55:01 GMT): tongli (Tue, 11 Jul 2017 13:55:26 GMT): tongli (Tue, 11 Jul 2017 13:56:16 GMT): tongli (Tue, 11 Jul 2017 13:57:29 GMT): tongli (Tue, 11 Jul 2017 13:58:11 GMT): tongli (Tue, 11 Jul 2017 13:58:33 GMT): tongli (Tue, 11 Jul 2017 13:59:19 GMT): CarlXK (Tue, 11 Jul 2017 14:02:26 GMT): tongli (Tue, 11 Jul 2017 14:02:59 GMT): tongli (Tue, 11 Jul 2017 14:03:10 GMT): tongli (Tue, 11 Jul 2017 14:03:23 GMT): tongli (Tue, 11 Jul 2017 14:03:34 GMT): tongli (Tue, 11 Jul 2017 14:03:53 GMT): tongli (Tue, 11 Jul 2017 14:04:00 GMT): tongli (Tue, 11 Jul 2017 14:04:13 GMT): baohua (Tue, 11 Jul 2017 14:21:33 GMT): tongli (Tue, 11 Jul 2017 14:22:16 GMT): tongli (Tue, 11 Jul 2017 14:22:22 GMT): baohua (Tue, 11 Jul 2017 14:22:32 GMT): tongli (Tue, 11 Jul 2017 14:22:35 GMT): tongli (Tue, 11 Jul 2017 14:23:01 GMT): baohua (Tue, 11 Jul 2017 14:23:07 GMT): chawlanikhil24 (Tue, 11 Jul 2017 14:23:07 GMT): tongli (Tue, 11 Jul 2017 14:23:36 GMT): tongli (Tue, 11 Jul 2017 14:23:50 GMT): tongli (Tue, 11 Jul 2017 14:23:58 GMT): chawlanikhil24 (Tue, 11 Jul 2017 14:32:15 GMT): chawlanikhil24 (Tue, 11 Jul 2017 14:34:23 GMT): chawlanikhil24 (Tue, 11 Jul 2017 14:38:39 GMT): tongli (Tue, 11 Jul 2017 14:40:25 GMT): tongli (Tue, 11 Jul 2017 14:40:39 GMT): tongli (Tue, 11 Jul 2017 14:40:40 GMT): chawlanikhil24 (Tue, 11 Jul 2017 14:41:52 GMT): chawlanikhil24 (Tue, 11 Jul 2017 14:42:04 GMT): chawlanikhil24 (Tue, 11 Jul 2017 14:42:59 GMT): tongli (Tue, 11 Jul 2017 14:43:50 GMT): chawlanikhil24 (Tue, 11 Jul 2017 14:44:30 GMT): chawlanikhil24 (Tue, 11 Jul 2017 14:44:43 GMT): chawlanikhil24 (Tue, 11 Jul 2017 14:44:43 GMT): tongli (Tue, 11 Jul 2017 14:45:28 GMT): tongli (Tue, 11 Jul 2017 14:45:52 GMT): tongli (Tue, 11 Jul 2017 14:46:10 GMT): tongli (Tue, 11 Jul 2017 14:46:30 GMT): tongli (Tue, 11 Jul 2017 14:47:12 GMT): pandabcai (Wed, 12 Jul 2017 02:00:53 GMT): pandabcai (Wed, 12 Jul 2017 02:04:27 GMT): pandabcai (Wed, 12 Jul 2017 02:07:19 GMT): baohua (Wed, 12 Jul 2017 02:07:53 GMT): baohua (Wed, 12 Jul 2017 02:08:24 GMT): baohua (Wed, 12 Jul 2017 02:08:47 GMT): pandabcai (Wed, 12 Jul 2017 02:10:25 GMT): baohua (Wed, 12 Jul 2017 02:28:27 GMT): baohua (Wed, 12 Jul 2017 02:29:21 GMT): chawlanikhil24 (Wed, 12 Jul 2017 04:22:34 GMT): chawlanikhil24 (Wed, 12 Jul 2017 04:22:34 GMT): aaronzheng (Wed, 12 Jul 2017 07:51:18 GMT): tongli (Wed, 12 Jul 2017 12:38:53 GMT): tongli (Wed, 12 Jul 2017 12:39:15 GMT): baohua (Wed, 12 Jul 2017 14:55:31 GMT): chawlanikhil24 (Wed, 12 Jul 2017 16:39:37 GMT): chawlanikhil24 (Wed, 12 Jul 2017 16:39:41 GMT): tongli (Wed, 12 Jul 2017 17:15:55 GMT): tongli (Wed, 12 Jul 2017 17:16:22 GMT): baohua (Thu, 13 Jul 2017 02:07:58 GMT): HuangLijun (Thu, 13 Jul 2017 09:44:41 GMT): HuangLijun (Thu, 13 Jul 2017 09:50:19 GMT): HuangLijun (Thu, 13 Jul 2017 09:50:19 GMT): baohua (Thu, 13 Jul 2017 10:36:37 GMT): baohua (Thu, 13 Jul 2017 10:45:30 GMT): HuangLijun (Thu, 13 Jul 2017 10:49:14 GMT): chawlanikhil24 (Thu, 13 Jul 2017 12:15:09 GMT): chawlanikhil24 (Thu, 13 Jul 2017 12:15:33 GMT): chawlanikhil24 (Thu, 13 Jul 2017 12:15:55 GMT): chawlanikhil24 (Thu, 13 Jul 2017 12:16:09 GMT): chawlanikhil24 (Thu, 13 Jul 2017 12:16:32 GMT): chawlanikhil24 (Thu, 13 Jul 2017 12:16:32 GMT): chawlanikhil24 (Thu, 13 Jul 2017 12:16:32 GMT): chawlanikhil24 (Thu, 13 Jul 2017 12:17:33 GMT): CarlXK (Thu, 13 Jul 2017 12:30:25 GMT): chawlanikhil24 (Thu, 13 Jul 2017 12:31:27 GMT): chawlanikhil24 (Thu, 13 Jul 2017 12:31:59 GMT): chawlanikhil24 (Thu, 13 Jul 2017 16:21:34 GMT): tongli (Thu, 13 Jul 2017 16:24:27 GMT): chawlanikhil24 (Thu, 13 Jul 2017 16:28:41 GMT): chawlanikhil24 (Thu, 13 Jul 2017 16:29:04 GMT): chawlanikhil24 (Thu, 13 Jul 2017 16:29:25 GMT): C0rWin (Thu, 13 Jul 2017 16:29:57 GMT): tongli (Thu, 13 Jul 2017 16:31:48 GMT): tongli (Thu, 13 Jul 2017 16:31:57 GMT): tongli (Thu, 13 Jul 2017 16:32:16 GMT): tongli (Thu, 13 Jul 2017 16:32:28 GMT): tongli (Thu, 13 Jul 2017 16:33:03 GMT): tongli (Thu, 13 Jul 2017 16:33:21 GMT): chawlanikhil24 (Thu, 13 Jul 2017 16:47:50 GMT): chawlanikhil24 (Thu, 13 Jul 2017 16:48:02 GMT): liuwenliang0632 (Sat, 15 Jul 2017 09:35:30 GMT): chenxuan (Sat, 15 Jul 2017 10:47:49 GMT): liuwenliang0632 (Sat, 15 Jul 2017 12:28:49 GMT): chawlanikhil24 (Sat, 15 Jul 2017 15:32:06 GMT): chawlanikhil24 (Sat, 15 Jul 2017 15:32:06 GMT): chawlanikhil24 (Sat, 15 Jul 2017 15:32:40 GMT): chawlanikhil24 (Sat, 15 Jul 2017 15:33:01 GMT): chawlanikhil24 (Sat, 15 Jul 2017 15:33:13 GMT): chawlanikhil24 (Sat, 15 Jul 2017 15:33:17 GMT): tongli (Sun, 16 Jul 2017 01:19:37 GMT): tongli (Sun, 16 Jul 2017 01:21:04 GMT): chawlanikhil24 (Sun, 16 Jul 2017 16:46:05 GMT): chawlanikhil24 (Sun, 16 Jul 2017 16:46:07 GMT): tongli (Sun, 16 Jul 2017 16:58:06 GMT): chawlanikhil24 (Sun, 16 Jul 2017 19:27:56 GMT): baohua (Mon, 17 Jul 2017 02:01:37 GMT): tongli (Mon, 17 Jul 2017 12:58:12 GMT): tongli (Mon, 17 Jul 2017 12:58:51 GMT): tongli (Mon, 17 Jul 2017 13:01:06 GMT): tongli (Mon, 17 Jul 2017 13:01:38 GMT): tongli (Mon, 17 Jul 2017 13:01:53 GMT): chawlanikhil24 (Mon, 17 Jul 2017 13:02:34 GMT): tongli (Mon, 17 Jul 2017 13:03:28 GMT): chawlanikhil24 (Mon, 17 Jul 2017 13:04:13 GMT): tongli (Mon, 17 Jul 2017 13:04:45 GMT): tongli (Mon, 17 Jul 2017 13:05:16 GMT): tongli (Mon, 17 Jul 2017 13:05:22 GMT): tongli (Mon, 17 Jul 2017 13:05:46 GMT): chawlanikhil24 (Mon, 17 Jul 2017 13:05:52 GMT): tongli (Mon, 17 Jul 2017 13:06:02 GMT): tongli (Mon, 17 Jul 2017 13:06:10 GMT): chawlanikhil24 (Mon, 17 Jul 2017 13:06:18 GMT): tongli (Mon, 17 Jul 2017 13:06:18 GMT): chawlanikhil24 (Mon, 17 Jul 2017 13:06:30 GMT): chawlanikhil24 (Mon, 17 Jul 2017 13:06:39 GMT): tongli (Mon, 17 Jul 2017 13:07:18 GMT): tongli (Mon, 17 Jul 2017 13:07:54 GMT): tongli (Mon, 17 Jul 2017 13:07:57 GMT): tongli (Mon, 17 Jul 2017 13:08:16 GMT): chawlanikhil24 (Mon, 17 Jul 2017 13:09:39 GMT): tongli (Mon, 17 Jul 2017 13:10:44 GMT): tongli (Mon, 17 Jul 2017 13:10:46 GMT): tongli (Mon, 17 Jul 2017 13:11:05 GMT): chawlanikhil24 (Mon, 17 Jul 2017 13:11:31 GMT): chawlanikhil24 (Mon, 17 Jul 2017 13:11:52 GMT): tongli (Mon, 17 Jul 2017 13:11:56 GMT): tongli (Mon, 17 Jul 2017 13:12:25 GMT): chawlanikhil24 (Mon, 17 Jul 2017 13:12:29 GMT): tongli (Mon, 17 Jul 2017 13:12:35 GMT): tongli (Mon, 17 Jul 2017 13:12:39 GMT): chawlanikhil24 (Mon, 17 Jul 2017 13:12:42 GMT): tongli (Mon, 17 Jul 2017 13:12:47 GMT): chawlanikhil24 (Mon, 17 Jul 2017 13:13:01 GMT): tongli (Mon, 17 Jul 2017 13:13:03 GMT): tongli (Mon, 17 Jul 2017 13:13:58 GMT): tongli (Mon, 17 Jul 2017 13:14:10 GMT): tongli (Mon, 17 Jul 2017 13:14:24 GMT): tongli (Mon, 17 Jul 2017 13:14:58 GMT): chawlanikhil24 (Mon, 17 Jul 2017 13:15:05 GMT): chawlanikhil24 (Mon, 17 Jul 2017 13:15:23 GMT): chawlanikhil24 (Mon, 17 Jul 2017 13:15:36 GMT): tongli (Mon, 17 Jul 2017 13:15:37 GMT): tongli (Mon, 17 Jul 2017 13:15:58 GMT): tongli (Mon, 17 Jul 2017 13:16:02 GMT): chawlanikhil24 (Mon, 17 Jul 2017 13:16:32 GMT): chawlanikhil24 (Mon, 17 Jul 2017 13:18:30 GMT): chawlanikhil24 (Mon, 17 Jul 2017 13:18:38 GMT): tongli (Mon, 17 Jul 2017 14:00:37 GMT): tolak (Mon, 17 Jul 2017 15:23:09 GMT): tolak (Mon, 17 Jul 2017 15:23:09 GMT): chawlanikhil24 (Mon, 17 Jul 2017 16:39:35 GMT): tongli (Mon, 17 Jul 2017 16:40:19 GMT): tongli (Mon, 17 Jul 2017 16:40:34 GMT): chawlanikhil24 (Mon, 17 Jul 2017 16:40:42 GMT): tongli (Mon, 17 Jul 2017 16:40:55 GMT): tongli (Mon, 17 Jul 2017 16:41:25 GMT): tongli (Mon, 17 Jul 2017 16:41:55 GMT): tongli (Mon, 17 Jul 2017 16:42:11 GMT): tongli (Mon, 17 Jul 2017 16:42:53 GMT): tongli (Mon, 17 Jul 2017 16:43:04 GMT): chawlanikhil24 (Mon, 17 Jul 2017 16:43:37 GMT): tongli (Mon, 17 Jul 2017 16:44:14 GMT): tongli (Mon, 17 Jul 2017 16:44:29 GMT): chawlanikhil24 (Mon, 17 Jul 2017 16:44:39 GMT): tongli (Mon, 17 Jul 2017 16:44:41 GMT): tongli (Mon, 17 Jul 2017 16:45:06 GMT): chawlanikhil24 (Mon, 17 Jul 2017 16:45:23 GMT): tongli (Mon, 17 Jul 2017 16:45:32 GMT): chawlanikhil24 (Mon, 17 Jul 2017 16:45:43 GMT): tongli (Mon, 17 Jul 2017 16:45:46 GMT): tongli (Mon, 17 Jul 2017 16:46:03 GMT): chawlanikhil24 (Mon, 17 Jul 2017 16:46:12 GMT): tongli (Mon, 17 Jul 2017 16:46:17 GMT): tongli (Mon, 17 Jul 2017 16:46:40 GMT): tongli (Mon, 17 Jul 2017 16:46:56 GMT): tongli (Mon, 17 Jul 2017 16:47:16 GMT): tongli (Mon, 17 Jul 2017 16:47:28 GMT): chawlanikhil24 (Mon, 17 Jul 2017 16:47:35 GMT): tongli (Mon, 17 Jul 2017 16:48:02 GMT): tongli (Mon, 17 Jul 2017 16:48:11 GMT): tongli (Mon, 17 Jul 2017 16:48:37 GMT): chawlanikhil24 (Mon, 17 Jul 2017 16:48:48 GMT): tongli (Mon, 17 Jul 2017 16:48:57 GMT): chawlanikhil24 (Mon, 17 Jul 2017 16:49:04 GMT): chawlanikhil24 (Mon, 17 Jul 2017 16:49:22 GMT): tongli (Mon, 17 Jul 2017 16:49:33 GMT): chawlanikhil24 (Mon, 17 Jul 2017 16:49:33 GMT): tongli (Mon, 17 Jul 2017 16:49:46 GMT): tongli (Mon, 17 Jul 2017 16:50:18 GMT): tongli (Mon, 17 Jul 2017 16:50:25 GMT): tongli (Mon, 17 Jul 2017 16:50:31 GMT): chawlanikhil24 (Mon, 17 Jul 2017 16:51:47 GMT): chawlanikhil24 (Mon, 17 Jul 2017 16:52:00 GMT): chawlanikhil24 (Mon, 17 Jul 2017 16:52:46 GMT): tongli (Mon, 17 Jul 2017 16:58:51 GMT): tongli (Mon, 17 Jul 2017 16:59:05 GMT): tongli (Mon, 17 Jul 2017 16:59:11 GMT): chawlanikhil24 (Mon, 17 Jul 2017 17:03:20 GMT): chawlanikhil24 (Mon, 17 Jul 2017 17:03:27 GMT): chawlanikhil24 (Mon, 17 Jul 2017 17:05:45 GMT): liuwenliang0632 (Tue, 18 Jul 2017 00:46:57 GMT): jimthematrix (Tue, 18 Jul 2017 02:36:40 GMT): tolak (Tue, 18 Jul 2017 02:38:50 GMT): ydk210999 (Tue, 18 Jul 2017 04:34:18 GMT): tongli (Wed, 19 Jul 2017 02:07:30 GMT): tongli (Wed, 19 Jul 2017 02:08:19 GMT): tongli (Wed, 19 Jul 2017 02:32:34 GMT): greg.haskins (Wed, 19 Jul 2017 02:32:34 GMT): tongli (Wed, 19 Jul 2017 02:33:01 GMT): CarlXK (Wed, 19 Jul 2017 02:47:11 GMT): tongli (Wed, 19 Jul 2017 02:51:49 GMT): jimthematrix (Wed, 19 Jul 2017 02:54:12 GMT): CarlXK (Wed, 19 Jul 2017 03:01:48 GMT): tongli (Wed, 19 Jul 2017 03:28:55 GMT): jimthematrix (Wed, 19 Jul 2017 03:31:26 GMT): jimthematrix (Wed, 19 Jul 2017 03:31:26 GMT): jimthematrix (Wed, 19 Jul 2017 03:32:13 GMT): tongli (Wed, 19 Jul 2017 03:35:04 GMT): jimthematrix (Wed, 19 Jul 2017 03:52:56 GMT): jimthematrix (Wed, 19 Jul 2017 03:55:12 GMT): jyellick (Wed, 19 Jul 2017 03:55:12 GMT): jyellick (Wed, 19 Jul 2017 03:59:59 GMT): jyellick (Wed, 19 Jul 2017 04:01:21 GMT): chenxuan (Wed, 19 Jul 2017 09:07:05 GMT): baohua (Wed, 19 Jul 2017 12:23:16 GMT): chenxuan (Wed, 19 Jul 2017 12:41:54 GMT): chenxuan (Wed, 19 Jul 2017 12:41:56 GMT): baohua (Wed, 19 Jul 2017 13:35:52 GMT): tongli (Wed, 19 Jul 2017 17:21:28 GMT): tongli (Wed, 19 Jul 2017 17:24:29 GMT): tongli (Wed, 19 Jul 2017 17:26:30 GMT): tongli (Wed, 19 Jul 2017 17:27:17 GMT): jyellick (Wed, 19 Jul 2017 17:39:40 GMT): jyellick (Wed, 19 Jul 2017 17:40:03 GMT): jyellick (Wed, 19 Jul 2017 17:40:17 GMT): jyellick (Wed, 19 Jul 2017 17:40:53 GMT): tongli (Wed, 19 Jul 2017 17:59:03 GMT): jyellick (Wed, 19 Jul 2017 18:02:32 GMT): tongli (Wed, 19 Jul 2017 18:04:33 GMT): CarlXK (Thu, 20 Jul 2017 02:31:49 GMT): CarlXK (Thu, 20 Jul 2017 02:31:49 GMT): CarlXK (Thu, 20 Jul 2017 02:31:49 GMT): qiushaoxi (Thu, 20 Jul 2017 02:44:58 GMT): baohua (Thu, 20 Jul 2017 02:46:03 GMT): baohua (Thu, 20 Jul 2017 02:46:27 GMT): baohua (Thu, 20 Jul 2017 02:46:35 GMT): qiushaoxi (Thu, 20 Jul 2017 02:47:43 GMT): baohua (Thu, 20 Jul 2017 02:47:58 GMT): baohua (Thu, 20 Jul 2017 02:48:10 GMT): qiushaoxi (Thu, 20 Jul 2017 02:49:22 GMT): baohua (Thu, 20 Jul 2017 02:51:57 GMT): qiushaoxi (Thu, 20 Jul 2017 02:52:23 GMT): liuwenliang0632 (Thu, 20 Jul 2017 03:21:01 GMT): qiushaoxi (Thu, 20 Jul 2017 03:21:17 GMT): qiushaoxi (Thu, 20 Jul 2017 03:21:22 GMT): zhangchao (Thu, 20 Jul 2017 06:47:45 GMT): qiushaoxi (Thu, 20 Jul 2017 06:49:44 GMT): qiushaoxi (Thu, 20 Jul 2017 06:50:10 GMT): baohua (Thu, 20 Jul 2017 14:20:47 GMT): baohua (Thu, 20 Jul 2017 14:20:47 GMT): chawlanikhil24 (Thu, 20 Jul 2017 20:35:29 GMT): chawlanikhil24 (Thu, 20 Jul 2017 20:35:47 GMT): baohua (Fri, 21 Jul 2017 01:37:59 GMT): tongli (Fri, 21 Jul 2017 01:50:03 GMT): tongli (Fri, 21 Jul 2017 01:50:46 GMT): liutc (Fri, 21 Jul 2017 02:07:39 GMT): baohua (Fri, 21 Jul 2017 02:10:08 GMT): baohua (Fri, 21 Jul 2017 02:11:13 GMT): guce (Fri, 21 Jul 2017 02:39:02 GMT): guce (Fri, 21 Jul 2017 02:39:20 GMT): liutc (Fri, 21 Jul 2017 02:42:47 GMT): pandabcai (Fri, 21 Jul 2017 03:27:07 GMT): pandabcai (Fri, 21 Jul 2017 03:34:16 GMT): liutc (Fri, 21 Jul 2017 04:18:12 GMT): chawlanikhil24 (Fri, 21 Jul 2017 04:25:09 GMT): chawlanikhil24 (Fri, 21 Jul 2017 07:00:33 GMT): chawlanikhil24 (Fri, 21 Jul 2017 07:00:59 GMT): CarlXK (Fri, 21 Jul 2017 09:16:55 GMT): CarlXK (Fri, 21 Jul 2017 09:16:55 GMT): chawlanikhil24 (Fri, 21 Jul 2017 09:18:51 GMT): CarlXK (Fri, 21 Jul 2017 10:07:10 GMT): jimthematrix (Fri, 21 Jul 2017 12:37:01 GMT): tongli (Fri, 21 Jul 2017 12:51:31 GMT): tolak (Fri, 21 Jul 2017 13:09:49 GMT): tolak (Fri, 21 Jul 2017 13:10:29 GMT): tolak (Fri, 21 Jul 2017 14:32:58 GMT): tolak (Fri, 21 Jul 2017 14:33:04 GMT): jimthematrix (Fri, 21 Jul 2017 14:47:22 GMT): jimthematrix (Fri, 21 Jul 2017 14:47:22 GMT): tolak (Fri, 21 Jul 2017 14:49:32 GMT): CarlXK (Mon, 24 Jul 2017 02:18:15 GMT): CarlXK (Mon, 24 Jul 2017 02:18:15 GMT): CarlXK (Mon, 24 Jul 2017 02:18:15 GMT): CarlXK (Mon, 24 Jul 2017 02:18:15 GMT): baoyangc (Mon, 24 Jul 2017 15:12:33 GMT): baohua (Tue, 25 Jul 2017 02:04:56 GMT): CarlXK (Tue, 25 Jul 2017 03:32:02 GMT): baohua (Tue, 25 Jul 2017 03:39:01 GMT): jimthematrix (Tue, 25 Jul 2017 04:17:04 GMT): CarlXK (Tue, 25 Jul 2017 04:20:57 GMT): baohua (Tue, 25 Jul 2017 05:20:13 GMT): barry_liang (Tue, 25 Jul 2017 06:22:05 GMT): liuwenliang0632 (Tue, 25 Jul 2017 06:38:08 GMT): liuwenliang0632 (Tue, 25 Jul 2017 06:42:18 GMT): CarlXK (Tue, 25 Jul 2017 08:41:28 GMT): CarlXK (Wed, 26 Jul 2017 01:39:28 GMT): CarlXK (Wed, 26 Jul 2017 01:39:28 GMT): jimthematrix (Wed, 26 Jul 2017 17:55:19 GMT): jimthematrix (Wed, 26 Jul 2017 17:56:59 GMT): CarlXK (Thu, 27 Jul 2017 01:29:30 GMT): liuwenliang0632 (Thu, 27 Jul 2017 08:31:06 GMT): liuwenliang0632 (Thu, 27 Jul 2017 08:32:00 GMT): mochechan-fusions360 (Fri, 28 Jul 2017 02:41:42 GMT): barry_liang (Fri, 28 Jul 2017 03:19:18 GMT): dijun (Fri, 28 Jul 2017 07:56:39 GMT): CarlXK (Fri, 28 Jul 2017 10:39:08 GMT): tongli (Fri, 28 Jul 2017 11:27:14 GMT): tongli (Fri, 28 Jul 2017 11:27:31 GMT): baohua (Fri, 28 Jul 2017 11:41:17 GMT): jimthematrix (Fri, 28 Jul 2017 14:41:10 GMT): jimthematrix (Fri, 28 Jul 2017 14:41:10 GMT): CarlXK (Sat, 29 Jul 2017 02:16:21 GMT): chawlanikhil24 (Sun, 30 Jul 2017 09:45:52 GMT): chawlanikhil24 (Sun, 30 Jul 2017 09:46:15 GMT): chawlanikhil24 (Sun, 30 Jul 2017 09:46:34 GMT): chawlanikhil24 (Sun, 30 Jul 2017 09:47:19 GMT): chawlanikhil24 (Sun, 30 Jul 2017 09:47:29 GMT): tongli (Sun, 30 Jul 2017 12:37:21 GMT): tongli (Sun, 30 Jul 2017 12:37:59 GMT): chenxuan (Mon, 31 Jul 2017 01:39:53 GMT): chenxuan (Mon, 31 Jul 2017 01:40:00 GMT): baohua (Mon, 31 Jul 2017 01:47:31 GMT): chenxuan (Mon, 31 Jul 2017 01:53:42 GMT): chenxuan (Mon, 31 Jul 2017 01:53:58 GMT): chenxuan (Mon, 31 Jul 2017 01:54:19 GMT): chenxuan (Mon, 31 Jul 2017 01:54:38 GMT): qiushaoxi (Mon, 31 Jul 2017 02:25:38 GMT): chenxuan (Mon, 31 Jul 2017 02:28:29 GMT): baohua (Mon, 31 Jul 2017 02:34:12 GMT): jimthematrix (Mon, 31 Jul 2017 02:39:24 GMT): jimthematrix (Mon, 31 Jul 2017 02:40:33 GMT): chenxuan (Mon, 31 Jul 2017 02:40:56 GMT): chenxuan (Mon, 31 Jul 2017 02:40:58 GMT): chenxuan (Mon, 31 Jul 2017 02:41:19 GMT): chenxuan (Mon, 31 Jul 2017 02:41:25 GMT): chawlanikhil24 (Mon, 31 Jul 2017 03:23:02 GMT): chawlanikhil24 (Mon, 31 Jul 2017 03:23:10 GMT): CarlXK (Mon, 31 Jul 2017 06:27:25 GMT): baohua (Mon, 31 Jul 2017 06:28:35 GMT): baohua (Mon, 31 Jul 2017 06:29:01 GMT): CarlXK (Mon, 31 Jul 2017 07:43:23 GMT): qiushaoxi (Mon, 31 Jul 2017 07:54:19 GMT): CarlXK (Mon, 31 Jul 2017 08:11:06 GMT): CarlXK (Mon, 31 Jul 2017 08:11:06 GMT): CarlXK (Mon, 31 Jul 2017 08:18:51 GMT): CarlXK (Mon, 31 Jul 2017 08:44:50 GMT): jimthematrix (Mon, 31 Jul 2017 12:17:57 GMT): chenxuan (Mon, 31 Jul 2017 14:25:02 GMT): chenxuan (Mon, 31 Jul 2017 14:25:12 GMT): chenxuan (Mon, 31 Jul 2017 14:25:17 GMT): chenxuan (Mon, 31 Jul 2017 14:25:17 GMT): jimthematrix (Mon, 31 Jul 2017 14:51:51 GMT): CarlXK (Tue, 01 Aug 2017 02:01:20 GMT): baoyangc (Tue, 01 Aug 2017 02:27:42 GMT): baohua (Tue, 01 Aug 2017 03:00:34 GMT): baoyangc (Tue, 01 Aug 2017 03:22:59 GMT): aaronzheng (Tue, 01 Aug 2017 07:03:46 GMT): CarlXK (Tue, 01 Aug 2017 07:55:32 GMT): baohua (Tue, 01 Aug 2017 07:59:45 GMT): aaronzheng (Tue, 01 Aug 2017 08:13:41 GMT): baohua (Tue, 01 Aug 2017 08:14:24 GMT): aaronzheng (Tue, 01 Aug 2017 08:21:29 GMT): CarlXK (Tue, 01 Aug 2017 09:15:40 GMT): baohua (Tue, 01 Aug 2017 09:42:31 GMT): CarlXK (Tue, 01 Aug 2017 10:18:46 GMT): CarlXK (Tue, 01 Aug 2017 10:18:46 GMT): CarlXK (Tue, 01 Aug 2017 11:04:10 GMT): jimthematrix (Tue, 01 Aug 2017 12:36:11 GMT): CarlXK (Tue, 01 Aug 2017 12:37:22 GMT): CarlXK (Tue, 01 Aug 2017 12:37:27 GMT): jimthematrix (Tue, 01 Aug 2017 12:38:30 GMT): CarlXK (Tue, 01 Aug 2017 12:38:34 GMT): CarlXK (Tue, 01 Aug 2017 12:39:10 GMT): jimthematrix (Tue, 01 Aug 2017 12:39:15 GMT): CarlXK (Tue, 01 Aug 2017 12:39:38 GMT): jimthematrix (Tue, 01 Aug 2017 12:39:55 GMT): CarlXK (Tue, 01 Aug 2017 12:39:59 GMT): jimthematrix (Tue, 01 Aug 2017 12:44:40 GMT): jimthematrix (Tue, 01 Aug 2017 12:44:40 GMT): jimthematrix (Tue, 01 Aug 2017 12:46:36 GMT): CarlXK (Tue, 01 Aug 2017 13:09:52 GMT): CarlXK (Tue, 01 Aug 2017 13:26:27 GMT): CarlXK (Tue, 01 Aug 2017 13:26:27 GMT): CarlXK (Tue, 01 Aug 2017 13:26:27 GMT): CarlXK (Tue, 01 Aug 2017 13:30:16 GMT): dijun (Wed, 02 Aug 2017 01:55:34 GMT): baohua (Wed, 02 Aug 2017 03:04:25 GMT): baohua (Wed, 02 Aug 2017 03:04:40 GMT): CarlXK (Wed, 02 Aug 2017 05:48:25 GMT): yp (Wed, 02 Aug 2017 07:22:38 GMT): yp (Wed, 02 Aug 2017 07:25:27 GMT): Glen (Wed, 02 Aug 2017 07:26:21 GMT): xixuejia (Wed, 02 Aug 2017 07:28:00 GMT): yp (Wed, 02 Aug 2017 07:28:21 GMT): xixuejia (Wed, 02 Aug 2017 07:31:36 GMT): xixuejia (Wed, 02 Aug 2017 07:32:07 GMT): xixuejia (Wed, 02 Aug 2017 07:33:05 GMT): xixuejia (Wed, 02 Aug 2017 07:33:25 GMT): yp (Wed, 02 Aug 2017 07:37:29 GMT): xixuejia (Wed, 02 Aug 2017 07:38:02 GMT): yp (Wed, 02 Aug 2017 07:38:17 GMT): yp (Wed, 02 Aug 2017 07:38:34 GMT): yp (Wed, 02 Aug 2017 07:39:02 GMT): xixuejia (Wed, 02 Aug 2017 07:39:17 GMT): xixuejia (Wed, 02 Aug 2017 07:39:38 GMT): yp (Wed, 02 Aug 2017 07:42:28 GMT): zhuxubin01 (Wed, 02 Aug 2017 11:05:36 GMT): zhuxubin01 (Wed, 02 Aug 2017 11:06:27 GMT): zhuxubin01 (Wed, 02 Aug 2017 11:06:55 GMT): jimthematrix (Wed, 02 Aug 2017 13:02:42 GMT): jimthematrix (Wed, 02 Aug 2017 13:02:42 GMT): jimthematrix (Wed, 02 Aug 2017 13:02:42 GMT): jimthematrix (Wed, 02 Aug 2017 13:02:42 GMT): jimthematrix (Wed, 02 Aug 2017 13:02:42 GMT): jimthematrix (Wed, 02 Aug 2017 13:02:42 GMT): jimthematrix (Wed, 02 Aug 2017 13:02:42 GMT): jimthematrix (Wed, 02 Aug 2017 13:05:29 GMT): CarlXK (Wed, 02 Aug 2017 13:39:40 GMT): CarlXK (Wed, 02 Aug 2017 13:39:40 GMT): chenxuan (Wed, 02 Aug 2017 14:43:55 GMT): chenxuan (Wed, 02 Aug 2017 14:43:56 GMT): chenxuan (Wed, 02 Aug 2017 14:44:06 GMT): jimthematrix (Wed, 02 Aug 2017 14:44:11 GMT): chenxuan (Wed, 02 Aug 2017 14:44:27 GMT): jimthematrix (Wed, 02 Aug 2017 14:59:00 GMT): CarlXK (Wed, 02 Aug 2017 15:01:26 GMT): jimthematrix (Wed, 02 Aug 2017 15:04:24 GMT): jimthematrix (Wed, 02 Aug 2017 15:04:24 GMT): chenxuan (Wed, 02 Aug 2017 15:05:11 GMT): chenxuan (Wed, 02 Aug 2017 15:08:29 GMT): CarlXK (Wed, 02 Aug 2017 15:12:19 GMT): chenxuan (Wed, 02 Aug 2017 15:12:51 GMT): jimthematrix (Wed, 02 Aug 2017 15:13:13 GMT): CarlXK (Wed, 02 Aug 2017 15:13:40 GMT): jimthematrix (Wed, 02 Aug 2017 15:13:45 GMT): jimthematrix (Wed, 02 Aug 2017 15:13:45 GMT): jimthematrix (Wed, 02 Aug 2017 15:13:45 GMT): chenxuan (Wed, 02 Aug 2017 15:14:53 GMT): chenxuan (Wed, 02 Aug 2017 15:15:07 GMT): chenxuan (Wed, 02 Aug 2017 15:15:22 GMT): CarlXK (Wed, 02 Aug 2017 15:15:33 GMT): jimthematrix (Wed, 02 Aug 2017 15:15:56 GMT): jimthematrix (Wed, 02 Aug 2017 15:15:56 GMT): CarlXK (Wed, 02 Aug 2017 15:16:29 GMT): CarlXK (Wed, 02 Aug 2017 15:16:29 GMT): jimthematrix (Wed, 02 Aug 2017 15:16:32 GMT): jimthematrix (Wed, 02 Aug 2017 15:16:32 GMT): CarlXK (Wed, 02 Aug 2017 15:18:13 GMT): CarlXK (Wed, 02 Aug 2017 15:18:24 GMT): chenxuan (Wed, 02 Aug 2017 15:20:11 GMT): chenxuan (Wed, 02 Aug 2017 15:21:25 GMT): chenxuan (Wed, 02 Aug 2017 15:21:39 GMT): chenxuan (Wed, 02 Aug 2017 15:21:45 GMT): chenxuan (Wed, 02 Aug 2017 15:21:57 GMT): greg.haskins (Wed, 02 Aug 2017 19:08:24 GMT): aaronzheng (Thu, 03 Aug 2017 03:46:34 GMT): zhuxubin01 (Thu, 03 Aug 2017 04:34:45 GMT): JackySheng (Thu, 03 Aug 2017 06:51:53 GMT): JackySheng (Thu, 03 Aug 2017 07:30:49 GMT): aaronzheng (Thu, 03 Aug 2017 08:52:32 GMT): ylsGit (Thu, 03 Aug 2017 09:01:22 GMT): aaronzheng (Thu, 03 Aug 2017 09:08:18 GMT): aaronzheng (Thu, 03 Aug 2017 09:42:01 GMT): chenxuan (Thu, 03 Aug 2017 11:03:01 GMT): chenxuan (Thu, 03 Aug 2017 11:03:08 GMT): chenxuan (Thu, 03 Aug 2017 11:03:12 GMT): chenxuan (Thu, 03 Aug 2017 11:03:37 GMT): chenxuan (Thu, 03 Aug 2017 11:03:51 GMT): baohua (Thu, 03 Aug 2017 11:21:55 GMT): jiangyaoguo (Thu, 03 Aug 2017 11:53:24 GMT): jimthematrix (Thu, 03 Aug 2017 13:35:39 GMT): chenxuan (Thu, 03 Aug 2017 13:36:08 GMT): chenxuan (Thu, 03 Aug 2017 13:36:34 GMT): chenxuan (Thu, 03 Aug 2017 13:36:35 GMT): jimthematrix (Thu, 03 Aug 2017 17:28:32 GMT): jimthematrix (Thu, 03 Aug 2017 17:31:58 GMT): chenxuan (Fri, 04 Aug 2017 01:31:42 GMT): aaronzheng (Fri, 04 Aug 2017 02:09:45 GMT): liuwenliang0632 (Fri, 04 Aug 2017 03:19:59 GMT): CarlXK (Fri, 04 Aug 2017 03:22:55 GMT): liuwenliang0632 (Fri, 04 Aug 2017 03:23:36 GMT): CarlXK (Fri, 04 Aug 2017 03:25:08 GMT): CarlXK (Fri, 04 Aug 2017 03:25:08 GMT): aaronzheng (Fri, 04 Aug 2017 05:49:16 GMT): aaronzheng (Fri, 04 Aug 2017 06:36:01 GMT): pancake (Fri, 04 Aug 2017 08:52:18 GMT): pancake (Fri, 04 Aug 2017 08:53:31 GMT): ylsGit (Fri, 04 Aug 2017 11:15:34 GMT): ylsGit (Fri, 04 Aug 2017 11:19:40 GMT): liuwenliang0632 (Fri, 04 Aug 2017 11:20:10 GMT): liuwenliang0632 (Fri, 04 Aug 2017 11:20:54 GMT): ylsGit (Fri, 04 Aug 2017 11:23:49 GMT): ylsGit (Fri, 04 Aug 2017 11:26:01 GMT): baoyangc (Fri, 04 Aug 2017 11:26:13 GMT): baoyangc (Fri, 04 Aug 2017 11:26:30 GMT): liuwenliang0632 (Fri, 04 Aug 2017 11:27:43 GMT): ylsGit (Fri, 04 Aug 2017 11:28:27 GMT): liuwenliang0632 (Fri, 04 Aug 2017 11:34:50 GMT): liuwenliang0632 (Fri, 04 Aug 2017 11:36:43 GMT): baoyangc (Fri, 04 Aug 2017 11:41:04 GMT): chawlanikhil24 (Fri, 04 Aug 2017 11:51:22 GMT): chawlanikhil24 (Fri, 04 Aug 2017 11:52:40 GMT): icodezjb (Mon, 07 Aug 2017 00:27:06 GMT): aaronzheng (Mon, 07 Aug 2017 05:02:39 GMT): aaronzheng (Mon, 07 Aug 2017 05:16:27 GMT): aaronzheng (Mon, 07 Aug 2017 05:19:14 GMT): baohua (Mon, 07 Aug 2017 05:34:21 GMT): aaronzheng (Mon, 07 Aug 2017 05:36:00 GMT): aaronzheng (Mon, 07 Aug 2017 05:53:15 GMT): baohua (Mon, 07 Aug 2017 05:58:32 GMT): aaronzheng (Mon, 07 Aug 2017 07:10:52 GMT): baohua (Mon, 07 Aug 2017 07:11:27 GMT): aaronzheng (Mon, 07 Aug 2017 07:39:28 GMT): aaronzheng (Mon, 07 Aug 2017 08:37:41 GMT): JackySheng (Mon, 07 Aug 2017 09:08:15 GMT): JackySheng (Mon, 07 Aug 2017 09:08:38 GMT): JackySheng (Mon, 07 Aug 2017 09:09:03 GMT): JackySheng (Mon, 07 Aug 2017 09:10:26 GMT): aaronzheng (Mon, 07 Aug 2017 09:16:30 GMT): JackySheng (Mon, 07 Aug 2017 09:21:48 GMT): JackySheng (Mon, 07 Aug 2017 09:22:28 GMT): JackySheng (Mon, 07 Aug 2017 09:22:55 GMT): JackySheng (Mon, 07 Aug 2017 09:23:34 GMT): JackySheng (Mon, 07 Aug 2017 09:23:53 GMT): JackySheng (Mon, 07 Aug 2017 09:24:14 GMT): aaronzheng (Mon, 07 Aug 2017 09:25:32 GMT): JackySheng (Mon, 07 Aug 2017 09:30:08 GMT): JackySheng (Mon, 07 Aug 2017 09:30:59 GMT): JackySheng (Mon, 07 Aug 2017 09:31:02 GMT): JackySheng (Mon, 07 Aug 2017 09:31:22 GMT): JackySheng (Mon, 07 Aug 2017 09:31:37 GMT): JackySheng (Mon, 07 Aug 2017 09:32:19 GMT): JackySheng (Mon, 07 Aug 2017 09:32:37 GMT): JackySheng (Mon, 07 Aug 2017 09:33:45 GMT): JackySheng (Mon, 07 Aug 2017 09:34:21 GMT): aaronzheng (Mon, 07 Aug 2017 09:38:34 GMT): aaronzheng (Mon, 07 Aug 2017 09:39:56 GMT): aaronzheng (Mon, 07 Aug 2017 09:40:33 GMT): JackySheng (Mon, 07 Aug 2017 09:48:03 GMT): JackySheng (Mon, 07 Aug 2017 09:50:31 GMT): JackySheng (Mon, 07 Aug 2017 09:52:40 GMT): zhuxubin01 (Mon, 07 Aug 2017 12:18:14 GMT): aaronzheng (Tue, 08 Aug 2017 01:17:46 GMT): baohua (Tue, 08 Aug 2017 05:59:06 GMT): aaronzheng (Tue, 08 Aug 2017 06:13:59 GMT): liuwenliang0632 (Wed, 09 Aug 2017 01:38:55 GMT): dongqi (Wed, 09 Aug 2017 02:39:31 GMT): dongqi (Wed, 09 Aug 2017 02:40:10 GMT): aaronzheng (Wed, 09 Aug 2017 03:10:11 GMT): aaronzheng (Wed, 09 Aug 2017 03:18:48 GMT): CarlXK (Wed, 09 Aug 2017 05:50:29 GMT): aaronzheng (Wed, 09 Aug 2017 06:11:18 GMT): CarlXK (Wed, 09 Aug 2017 06:26:20 GMT): CarlXK (Wed, 09 Aug 2017 06:26:42 GMT): aaronzheng (Wed, 09 Aug 2017 06:45:38 GMT): aaronzheng (Wed, 09 Aug 2017 06:56:49 GMT): chawlanikhil24 (Wed, 09 Aug 2017 12:00:06 GMT): Claude-ZHENG (Thu, 10 Aug 2017 01:39:27 GMT): aaronzheng (Thu, 10 Aug 2017 01:45:26 GMT): baohua (Thu, 10 Aug 2017 02:23:53 GMT): baohua (Thu, 10 Aug 2017 02:24:56 GMT): baohua (Thu, 10 Aug 2017 02:25:38 GMT): chawlanikhil24 (Thu, 10 Aug 2017 04:39:01 GMT): aaronzheng (Thu, 10 Aug 2017 07:33:43 GMT): mochechan-fusions360 (Thu, 10 Aug 2017 09:24:11 GMT): aaronzheng (Fri, 11 Aug 2017 00:48:09 GMT): baohua (Fri, 11 Aug 2017 01:27:15 GMT): ydk210999 (Fri, 11 Aug 2017 01:27:58 GMT): ydk210999 (Fri, 11 Aug 2017 01:32:49 GMT): baohua (Fri, 11 Aug 2017 01:49:10 GMT): ydk210999 (Fri, 11 Aug 2017 01:53:31 GMT): ydk210999 (Fri, 11 Aug 2017 02:46:14 GMT): ydk210999 (Fri, 11 Aug 2017 02:51:28 GMT): luomin (Sun, 13 Aug 2017 22:59:18 GMT): tolak (Mon, 14 Aug 2017 02:04:30 GMT): baohua (Mon, 14 Aug 2017 23:12:42 GMT): yuhaoDeng (Wed, 16 Aug 2017 01:33:45 GMT): jrui (Wed, 16 Aug 2017 08:40:09 GMT): zhuxubin01 (Thu, 17 Aug 2017 02:05:30 GMT): zhuxubin01 (Thu, 17 Aug 2017 02:06:04 GMT): chenxuan (Thu, 17 Aug 2017 03:03:30 GMT): chenxuan (Thu, 17 Aug 2017 03:03:35 GMT): zhuxubin01 (Thu, 17 Aug 2017 06:54:12 GMT): barry_liang (Thu, 17 Aug 2017 09:51:52 GMT): barry_liang (Fri, 18 Aug 2017 02:49:44 GMT): baohua (Fri, 18 Aug 2017 02:56:16 GMT): baohua (Fri, 18 Aug 2017 02:56:29 GMT): barry_liang (Fri, 18 Aug 2017 03:07:50 GMT): baohua (Fri, 18 Aug 2017 04:15:18 GMT): matingwei (Fri, 18 Aug 2017 05:10:25 GMT): aaronzheng (Fri, 18 Aug 2017 06:08:52 GMT): grapebaba (Fri, 18 Aug 2017 06:11:50 GMT): baohua (Fri, 18 Aug 2017 06:54:23 GMT): baohua (Fri, 18 Aug 2017 06:54:34 GMT): grapebaba (Fri, 18 Aug 2017 06:55:24 GMT): CarlXK (Fri, 18 Aug 2017 07:21:20 GMT): barry_liang (Fri, 18 Aug 2017 07:22:55 GMT): CarlXK (Fri, 18 Aug 2017 07:22:57 GMT): barry_liang (Fri, 18 Aug 2017 07:23:04 GMT): CarlXK (Fri, 18 Aug 2017 07:23:46 GMT): barry_liang (Fri, 18 Aug 2017 07:24:18 GMT): CarlXK (Fri, 18 Aug 2017 07:24:44 GMT): barry_liang (Fri, 18 Aug 2017 07:25:13 GMT): CarlXK (Fri, 18 Aug 2017 07:25:33 GMT): barry_liang (Fri, 18 Aug 2017 07:26:03 GMT): barry_liang (Fri, 18 Aug 2017 07:26:16 GMT): CarlXK (Fri, 18 Aug 2017 07:27:32 GMT): CarlXK (Fri, 18 Aug 2017 07:27:54 GMT): barry_liang (Fri, 18 Aug 2017 07:28:20 GMT): CarlXK (Fri, 18 Aug 2017 07:28:32 GMT): barry_liang (Fri, 18 Aug 2017 07:29:11 GMT): CarlXK (Fri, 18 Aug 2017 07:29:45 GMT): liutc (Fri, 18 Aug 2017 09:46:54 GMT): baohua (Fri, 18 Aug 2017 10:51:19 GMT): baohua (Fri, 18 Aug 2017 13:56:21 GMT): muralisr (Fri, 18 Aug 2017 13:56:21 GMT): baohua (Fri, 18 Aug 2017 13:56:58 GMT): baohua (Fri, 18 Aug 2017 13:57:09 GMT): baohua (Fri, 18 Aug 2017 13:58:05 GMT): muralisr (Fri, 18 Aug 2017 14:01:20 GMT): muralisr (Fri, 18 Aug 2017 14:01:54 GMT): tolak (Sat, 19 Aug 2017 12:29:47 GMT): chenxuan (Sat, 19 Aug 2017 13:08:51 GMT): tolak (Sat, 19 Aug 2017 13:24:30 GMT): baohua (Sat, 19 Aug 2017 13:46:47 GMT): chenxuan (Sat, 19 Aug 2017 14:01:41 GMT): chenxuan (Sat, 19 Aug 2017 14:01:41 GMT): baohua (Sat, 19 Aug 2017 14:02:20 GMT): chenxuan (Sat, 19 Aug 2017 14:02:32 GMT): chenxuan (Sat, 19 Aug 2017 14:02:32 GMT): chenxuan (Sat, 19 Aug 2017 14:03:11 GMT): chenxuan (Sat, 19 Aug 2017 14:03:46 GMT): chenxuan (Sat, 19 Aug 2017 14:05:16 GMT): baohua (Sat, 19 Aug 2017 14:05:42 GMT): baohua (Sat, 19 Aug 2017 14:06:03 GMT): tolak (Sun, 20 Aug 2017 04:14:02 GMT): barry_liang (Mon, 21 Aug 2017 01:24:32 GMT): barry_liang (Mon, 21 Aug 2017 01:25:33 GMT): baohua (Mon, 21 Aug 2017 01:29:08 GMT): barry_liang (Mon, 21 Aug 2017 01:33:09 GMT): barry_liang (Mon, 21 Aug 2017 01:36:22 GMT): baohua (Mon, 21 Aug 2017 01:36:39 GMT): duwenhui (Mon, 21 Aug 2017 05:30:45 GMT): aaronzheng (Mon, 21 Aug 2017 07:10:12 GMT): liutc (Mon, 21 Aug 2017 07:22:12 GMT): aaronzheng (Mon, 21 Aug 2017 08:12:42 GMT): duwenhui (Mon, 21 Aug 2017 10:03:48 GMT): ylsGit (Tue, 22 Aug 2017 01:19:43 GMT): tolak (Tue, 22 Aug 2017 02:05:36 GMT): CarlXK (Tue, 22 Aug 2017 03:40:04 GMT): baohua (Tue, 22 Aug 2017 04:34:39 GMT): CarlXK (Tue, 22 Aug 2017 06:30:35 GMT): baohua (Tue, 22 Aug 2017 07:27:08 GMT): baohua (Tue, 22 Aug 2017 07:27:18 GMT): CarlXK (Tue, 22 Aug 2017 08:12:23 GMT): jimthematrix (Tue, 22 Aug 2017 14:23:00 GMT): jimthematrix (Tue, 22 Aug 2017 14:31:09 GMT): jimthematrix (Tue, 22 Aug 2017 14:31:09 GMT): jimthematrix (Tue, 22 Aug 2017 14:35:08 GMT): tolak (Tue, 22 Aug 2017 15:23:15 GMT): baohua (Wed, 23 Aug 2017 01:57:19 GMT): asaningmaxchain (Wed, 23 Aug 2017 02:11:06 GMT): jimthematrix (Wed, 23 Aug 2017 02:14:20 GMT): jimthematrix (Wed, 23 Aug 2017 02:14:20 GMT): duwenhui (Wed, 23 Aug 2017 02:16:48 GMT): duwenhui (Wed, 23 Aug 2017 02:17:00 GMT): zhangchao (Wed, 23 Aug 2017 02:18:30 GMT): zhangchao (Wed, 23 Aug 2017 02:18:58 GMT): aaronzheng (Wed, 23 Aug 2017 02:29:30 GMT): MCC (Wed, 23 Aug 2017 02:29:33 GMT): duwenhui (Wed, 23 Aug 2017 02:34:10 GMT): duwenhui (Wed, 23 Aug 2017 02:35:29 GMT): duwenhui (Wed, 23 Aug 2017 02:35:29 GMT): duwenhui (Wed, 23 Aug 2017 02:37:25 GMT): asaningmaxchain (Wed, 23 Aug 2017 02:42:09 GMT): baohua (Wed, 23 Aug 2017 02:46:36 GMT): duwenhui (Wed, 23 Aug 2017 02:46:58 GMT): baohua (Wed, 23 Aug 2017 02:46:58 GMT): duwenhui (Wed, 23 Aug 2017 02:47:36 GMT): baohua (Wed, 23 Aug 2017 02:47:39 GMT): asaningmaxchain (Wed, 23 Aug 2017 02:51:16 GMT): duwenhui (Wed, 23 Aug 2017 02:51:44 GMT): duwenhui (Wed, 23 Aug 2017 02:52:47 GMT): duwenhui (Wed, 23 Aug 2017 02:52:57 GMT): aaronzheng (Wed, 23 Aug 2017 02:54:34 GMT): duwenhui (Wed, 23 Aug 2017 02:55:11 GMT): zhangchao (Wed, 23 Aug 2017 03:09:44 GMT): aaronzheng (Wed, 23 Aug 2017 06:58:19 GMT): tolak (Wed, 23 Aug 2017 08:29:39 GMT): jimthematrix (Wed, 23 Aug 2017 12:20:56 GMT): jimthematrix (Wed, 23 Aug 2017 12:20:56 GMT): jimthematrix (Wed, 23 Aug 2017 12:21:55 GMT): yahtoo (Thu, 24 Aug 2017 02:00:01 GMT): jimthematrix (Thu, 24 Aug 2017 02:03:19 GMT): guoger (Thu, 24 Aug 2017 02:06:33 GMT): yahtoo (Thu, 24 Aug 2017 02:11:26 GMT): jimthematrix (Thu, 24 Aug 2017 02:32:08 GMT): tolak (Thu, 24 Aug 2017 02:39:06 GMT): zhangchao (Thu, 24 Aug 2017 03:29:58 GMT): yahtoo (Thu, 24 Aug 2017 04:06:24 GMT): tolak (Thu, 24 Aug 2017 04:19:42 GMT): tolak (Thu, 24 Aug 2017 04:22:36 GMT): ylsGit (Thu, 24 Aug 2017 09:32:03 GMT): ylsGit (Thu, 24 Aug 2017 09:32:24 GMT): Claude-ZHENG (Thu, 24 Aug 2017 09:33:05 GMT): Claude-ZHENG (Thu, 24 Aug 2017 09:33:25 GMT): ylsGit (Thu, 24 Aug 2017 09:34:16 GMT): ylsGit (Thu, 24 Aug 2017 09:35:29 GMT): ylsGit (Thu, 24 Aug 2017 09:35:59 GMT): baohua (Thu, 24 Aug 2017 09:36:26 GMT): ylsGit (Thu, 24 Aug 2017 09:36:39 GMT): ylsGit (Thu, 24 Aug 2017 09:40:26 GMT): baohua (Thu, 24 Aug 2017 09:57:24 GMT): dave.enyeart (Thu, 24 Aug 2017 10:00:09 GMT): aaronzheng (Thu, 24 Aug 2017 10:17:18 GMT): ylsGit (Thu, 24 Aug 2017 10:31:28 GMT): ylsGit (Thu, 24 Aug 2017 10:31:37 GMT): ylsGit (Thu, 24 Aug 2017 10:32:55 GMT): zhuxubin01 (Thu, 24 Aug 2017 12:17:43 GMT): baohua (Fri, 25 Aug 2017 01:36:49 GMT): baohua (Fri, 25 Aug 2017 01:37:14 GMT): ylsGit (Fri, 25 Aug 2017 01:39:57 GMT): baohua (Fri, 25 Aug 2017 01:40:43 GMT): baohua (Fri, 25 Aug 2017 01:41:14 GMT): baohua (Fri, 25 Aug 2017 01:41:14 GMT): ylsGit (Fri, 25 Aug 2017 01:42:30 GMT): boliang (Fri, 25 Aug 2017 02:25:31 GMT): zhuxubin01 (Fri, 25 Aug 2017 08:48:17 GMT): yahtoo (Fri, 25 Aug 2017 09:27:12 GMT): zhuxubin01 (Fri, 25 Aug 2017 10:06:57 GMT): liutc (Fri, 25 Aug 2017 10:35:41 GMT): MCC (Mon, 28 Aug 2017 03:41:15 GMT): MCC (Mon, 28 Aug 2017 03:42:09 GMT): MCC (Mon, 28 Aug 2017 03:42:43 GMT): Xeriou (Mon, 28 Aug 2017 05:58:22 GMT): Xeriou (Mon, 28 Aug 2017 06:02:23 GMT): MCC (Mon, 28 Aug 2017 06:03:34 GMT): MCC (Mon, 28 Aug 2017 06:03:56 GMT): Xeriou (Mon, 28 Aug 2017 06:10:19 GMT): MCC (Mon, 28 Aug 2017 06:10:22 GMT): MCC (Mon, 28 Aug 2017 06:11:19 GMT): MCC (Mon, 28 Aug 2017 06:11:39 GMT): MCC (Mon, 28 Aug 2017 06:12:49 GMT): Xeriou (Mon, 28 Aug 2017 06:13:51 GMT): MCC (Mon, 28 Aug 2017 06:14:15 GMT): MCC (Mon, 28 Aug 2017 06:15:12 GMT): Xeriou (Mon, 28 Aug 2017 06:15:54 GMT): MCC (Mon, 28 Aug 2017 06:16:15 GMT): Xeriou (Mon, 28 Aug 2017 06:19:13 GMT): Xeriou (Mon, 28 Aug 2017 06:19:55 GMT): Xeriou (Mon, 28 Aug 2017 06:20:31 GMT): Xeriou (Mon, 28 Aug 2017 06:21:23 GMT): MCC (Mon, 28 Aug 2017 06:27:10 GMT): Xeriou (Mon, 28 Aug 2017 06:36:05 GMT): Xeriou (Mon, 28 Aug 2017 06:36:15 GMT): Xeriou (Mon, 28 Aug 2017 06:56:13 GMT): baohua (Tue, 29 Aug 2017 01:10:27 GMT): jimthematrix (Tue, 29 Aug 2017 01:25:47 GMT): Xeriou (Tue, 29 Aug 2017 02:23:55 GMT): aaronzheng (Tue, 29 Aug 2017 02:50:47 GMT): baoyangc (Tue, 29 Aug 2017 05:35:05 GMT): baoyangc (Tue, 29 Aug 2017 05:39:53 GMT): baoyangc (Tue, 29 Aug 2017 05:41:01 GMT): baoyangc (Tue, 29 Aug 2017 05:41:44 GMT): zhuxubin01 (Tue, 29 Aug 2017 08:59:11 GMT): baoyangc (Tue, 29 Aug 2017 10:44:02 GMT): tongli (Tue, 29 Aug 2017 13:21:42 GMT): tongli (Tue, 29 Aug 2017 13:22:03 GMT): tongli (Tue, 29 Aug 2017 13:22:21 GMT): MikeMayori (Tue, 29 Aug 2017 19:21:36 GMT): MikeMayori (Tue, 29 Aug 2017 19:21:38 GMT): MikeMayori (Tue, 29 Aug 2017 19:21:50 GMT): ylsGit (Wed, 30 Aug 2017 02:13:21 GMT): liuwenliang0632 (Wed, 30 Aug 2017 02:57:15 GMT): liuwenliang0632 (Wed, 30 Aug 2017 02:57:15 GMT): ylsGit (Wed, 30 Aug 2017 03:29:29 GMT): ylsGit (Wed, 30 Aug 2017 03:29:29 GMT): ylsGit (Wed, 30 Aug 2017 03:31:09 GMT): aaronzheng (Wed, 30 Aug 2017 06:26:22 GMT): davidkhala (Wed, 30 Aug 2017 07:00:26 GMT): davidkhala (Wed, 30 Aug 2017 07:01:02 GMT): aaronzheng (Wed, 30 Aug 2017 07:01:06 GMT): davidkhala (Wed, 30 Aug 2017 07:01:08 GMT): davidkhala (Wed, 30 Aug 2017 07:02:28 GMT): liutc (Wed, 30 Aug 2017 07:32:48 GMT): aaronzheng (Wed, 30 Aug 2017 07:50:12 GMT): Hangyu (Wed, 30 Aug 2017 08:37:06 GMT): CarlXK (Wed, 30 Aug 2017 09:27:19 GMT): ydk210999 (Wed, 30 Aug 2017 09:33:46 GMT): asaningmaxchain (Wed, 30 Aug 2017 09:36:59 GMT): ylsGit (Wed, 30 Aug 2017 10:03:38 GMT): liutc (Wed, 30 Aug 2017 10:15:14 GMT): HuangLijun (Wed, 30 Aug 2017 10:32:29 GMT): jimthematrix (Wed, 30 Aug 2017 14:05:37 GMT): jimthematrix (Wed, 30 Aug 2017 14:19:30 GMT): jimthematrix (Wed, 30 Aug 2017 14:19:30 GMT): ydk210999 (Wed, 30 Aug 2017 14:21:56 GMT): jimthematrix (Wed, 30 Aug 2017 14:23:56 GMT): jimthematrix (Wed, 30 Aug 2017 14:23:56 GMT): jimthematrix (Wed, 30 Aug 2017 14:23:56 GMT): jimthematrix (Wed, 30 Aug 2017 14:25:25 GMT): ydk210999 (Wed, 30 Aug 2017 14:26:00 GMT): CarlXK (Thu, 31 Aug 2017 01:43:49 GMT): CarlXK (Thu, 31 Aug 2017 01:43:49 GMT): CarlXK (Thu, 31 Aug 2017 01:43:49 GMT): CarlXK (Thu, 31 Aug 2017 01:43:49 GMT): gxx (Thu, 31 Aug 2017 01:57:44 GMT): zhuxubin01 (Thu, 31 Aug 2017 02:10:04 GMT): baoyangc (Thu, 31 Aug 2017 02:13:38 GMT): baoyangc (Thu, 31 Aug 2017 02:14:10 GMT): ylsGit (Thu, 31 Aug 2017 03:32:05 GMT): ylsGit (Thu, 31 Aug 2017 03:32:54 GMT): aaronzheng (Thu, 31 Aug 2017 03:49:04 GMT): aaronzheng (Thu, 31 Aug 2017 03:50:31 GMT): jimthematrix (Thu, 31 Aug 2017 04:05:50 GMT): duwenhui (Thu, 31 Aug 2017 06:05:39 GMT): ylsGit (Thu, 31 Aug 2017 07:15:51 GMT): CarlXK (Thu, 31 Aug 2017 08:08:40 GMT): Hangyu (Thu, 31 Aug 2017 08:16:20 GMT): Hangyu (Thu, 31 Aug 2017 08:22:57 GMT): Hangyu (Thu, 31 Aug 2017 08:23:21 GMT): aaronzheng (Thu, 31 Aug 2017 08:47:37 GMT): Hangyu (Thu, 31 Aug 2017 09:02:10 GMT): Hangyu (Thu, 31 Aug 2017 09:03:35 GMT): CarlXK (Thu, 31 Aug 2017 09:17:04 GMT): CarlXK (Thu, 31 Aug 2017 09:17:04 GMT): CarlXK (Thu, 31 Aug 2017 09:20:13 GMT): Hangyu (Thu, 31 Aug 2017 11:40:38 GMT): jimthematrix (Thu, 31 Aug 2017 13:35:46 GMT): Hangyu (Thu, 31 Aug 2017 23:46:36 GMT): CarlXK (Fri, 01 Sep 2017 02:04:00 GMT): baohua (Fri, 01 Sep 2017 02:05:29 GMT): CarlXK (Fri, 01 Sep 2017 02:07:19 GMT): CarlXK (Fri, 01 Sep 2017 02:08:00 GMT): liuwenliang0632 (Fri, 01 Sep 2017 02:08:55 GMT): liuwenliang0632 (Fri, 01 Sep 2017 02:09:46 GMT): asaningmaxchain (Fri, 01 Sep 2017 02:11:11 GMT): liuwenliang0632 (Fri, 01 Sep 2017 02:11:38 GMT): asaningmaxchain (Fri, 01 Sep 2017 02:11:55 GMT): asaningmaxchain (Fri, 01 Sep 2017 02:11:58 GMT): liuwenliang0632 (Fri, 01 Sep 2017 02:14:28 GMT): asaningmaxchain (Fri, 01 Sep 2017 02:15:33 GMT): liuwenliang0632 (Fri, 01 Sep 2017 02:16:11 GMT): liuwenliang0632 (Fri, 01 Sep 2017 02:17:21 GMT): asaningmaxchain (Fri, 01 Sep 2017 02:18:12 GMT): liuwenliang0632 (Fri, 01 Sep 2017 02:34:12 GMT): liuwenliang0632 (Fri, 01 Sep 2017 02:34:52 GMT): liuwenliang0632 (Fri, 01 Sep 2017 02:35:26 GMT): asaningmaxchain (Fri, 01 Sep 2017 02:35:42 GMT): liuwenliang0632 (Fri, 01 Sep 2017 02:41:51 GMT): liuwenliang0632 (Fri, 01 Sep 2017 02:46:08 GMT): liuwenliang0632 (Fri, 01 Sep 2017 02:46:22 GMT): liutc (Fri, 01 Sep 2017 02:57:15 GMT): baoyangc (Fri, 01 Sep 2017 02:58:50 GMT): baoyangc (Fri, 01 Sep 2017 02:58:59 GMT): baoyangc (Fri, 01 Sep 2017 03:00:05 GMT): baoyangc (Fri, 01 Sep 2017 03:08:33 GMT): Xcy (Fri, 01 Sep 2017 05:02:57 GMT): baoyangc (Fri, 01 Sep 2017 06:21:10 GMT): liutc (Fri, 01 Sep 2017 07:08:36 GMT): Hangyu (Fri, 01 Sep 2017 10:24:50 GMT): baoyangc (Sat, 02 Sep 2017 02:41:00 GMT): huiwenhan (Sat, 02 Sep 2017 09:02:19 GMT): liutc (Sat, 02 Sep 2017 13:27:52 GMT): smith (Mon, 04 Sep 2017 07:09:09 GMT): zhuxubin01 (Mon, 04 Sep 2017 10:09:31 GMT): shanfeng (Tue, 05 Sep 2017 01:45:07 GMT): jimthematrix (Tue, 05 Sep 2017 03:13:30 GMT): jimthematrix (Tue, 05 Sep 2017 03:16:22 GMT): liutc (Tue, 05 Sep 2017 03:20:55 GMT): baohua (Tue, 05 Sep 2017 03:22:22 GMT): baohua (Tue, 05 Sep 2017 03:23:29 GMT): liutc (Tue, 05 Sep 2017 03:26:28 GMT): jimthematrix (Tue, 05 Sep 2017 03:28:31 GMT): liutc (Tue, 05 Sep 2017 03:33:25 GMT): Xeriou (Tue, 05 Sep 2017 08:18:33 GMT): Xeriou (Tue, 05 Sep 2017 08:28:23 GMT): jimthematrix (Tue, 05 Sep 2017 19:52:33 GMT): jimthematrix (Tue, 05 Sep 2017 19:53:01 GMT): Xeriou (Wed, 06 Sep 2017 05:51:40 GMT): jimthematrix (Wed, 06 Sep 2017 15:24:43 GMT): Xeriou (Mon, 11 Sep 2017 03:17:03 GMT): Xeriou (Mon, 11 Sep 2017 03:17:20 GMT): Xeriou (Mon, 11 Sep 2017 03:24:45 GMT): Xeriou (Mon, 11 Sep 2017 03:24:45 GMT): Xeriou (Mon, 11 Sep 2017 03:26:36 GMT): Xeriou (Mon, 11 Sep 2017 03:27:36 GMT): Xeriou (Mon, 11 Sep 2017 03:29:49 GMT): jimthematrix (Mon, 11 Sep 2017 12:46:29 GMT): jimthematrix (Mon, 11 Sep 2017 12:46:29 GMT): jimthematrix (Mon, 11 Sep 2017 12:47:22 GMT): baohua (Mon, 11 Sep 2017 14:44:31 GMT): liujinlong (Tue, 12 Sep 2017 08:14:15 GMT): ylsGit (Tue, 12 Sep 2017 08:27:11 GMT): yyyyyyy9 (Tue, 12 Sep 2017 14:13:48 GMT): Redscarfs (Wed, 13 Sep 2017 08:09:18 GMT): baoyangc (Thu, 14 Sep 2017 02:06:23 GMT): baoyangc (Thu, 14 Sep 2017 02:06:56 GMT): gxx (Thu, 14 Sep 2017 02:12:00 GMT): seancheney (Thu, 14 Sep 2017 07:04:26 GMT): zhaoliang1133 (Thu, 14 Sep 2017 08:14:32 GMT): smith (Fri, 15 Sep 2017 09:26:31 GMT): smith (Fri, 15 Sep 2017 09:26:31 GMT): smith (Fri, 15 Sep 2017 09:26:31 GMT): smith (Fri, 15 Sep 2017 09:26:31 GMT): smith (Fri, 15 Sep 2017 09:26:31 GMT): smith (Fri, 15 Sep 2017 09:26:31 GMT): waaagh (Fri, 15 Sep 2017 14:50:40 GMT): james3443112 (Sat, 16 Sep 2017 09:47:17 GMT): james3443112 (Sat, 16 Sep 2017 09:48:25 GMT): Xeriou (Sun, 17 Sep 2017 12:37:19 GMT): CarlXK (Mon, 18 Sep 2017 02:32:09 GMT): CarlXK (Mon, 18 Sep 2017 02:32:09 GMT): CarlXK (Mon, 18 Sep 2017 06:11:55 GMT): zhaoliang1133 (Mon, 18 Sep 2017 06:30:53 GMT): tolak (Mon, 18 Sep 2017 07:29:25 GMT): jrui (Mon, 18 Sep 2017 10:08:06 GMT): jrui (Mon, 18 Sep 2017 10:08:25 GMT): jimthematrix (Mon, 18 Sep 2017 12:26:42 GMT): jimthematrix (Mon, 18 Sep 2017 12:31:41 GMT): jimthematrix (Mon, 18 Sep 2017 12:38:05 GMT): CarlXK (Tue, 19 Sep 2017 01:33:44 GMT): zhuxubin01 (Tue, 19 Sep 2017 08:42:21 GMT): qingsongGuo (Thu, 21 Sep 2017 05:01:14 GMT): jimthematrix (Thu, 21 Sep 2017 23:07:06 GMT): mochechan-fusions360 (Fri, 22 Sep 2017 09:40:42 GMT): ZheliangLiu (Fri, 22 Sep 2017 20:16:15 GMT): zhuxubin01 (Mon, 25 Sep 2017 03:42:59 GMT): baohua (Mon, 25 Sep 2017 05:46:28 GMT): baohua (Mon, 25 Sep 2017 05:46:40 GMT): zhuxubin01 (Mon, 25 Sep 2017 05:49:20 GMT): baohua (Mon, 25 Sep 2017 05:50:37 GMT): baohua (Mon, 25 Sep 2017 05:50:58 GMT): zhuxubin01 (Mon, 25 Sep 2017 05:51:21 GMT): baohua (Mon, 25 Sep 2017 05:52:51 GMT): zhuxubin01 (Mon, 25 Sep 2017 05:53:12 GMT): baohua (Mon, 25 Sep 2017 05:53:46 GMT): guoger (Mon, 25 Sep 2017 06:47:36 GMT): guoger (Mon, 25 Sep 2017 06:47:56 GMT): guoger (Mon, 25 Sep 2017 06:49:28 GMT): guoger (Mon, 25 Sep 2017 06:50:48 GMT): guoger (Mon, 25 Sep 2017 06:51:27 GMT): zhuxubin01 (Mon, 25 Sep 2017 06:58:13 GMT): zhuxubin01 (Mon, 25 Sep 2017 06:58:45 GMT): zhuxubin01 (Mon, 25 Sep 2017 06:59:08 GMT): guoger (Mon, 25 Sep 2017 07:21:43 GMT): zhuxubin01 (Mon, 25 Sep 2017 07:28:21 GMT): guoger (Mon, 25 Sep 2017 07:33:20 GMT): zhuxubin01 (Mon, 25 Sep 2017 07:35:34 GMT): guoger (Mon, 25 Sep 2017 07:35:43 GMT): zhuxubin01 (Mon, 25 Sep 2017 07:35:59 GMT): guoger (Mon, 25 Sep 2017 07:35:59 GMT): zhuxubin01 (Mon, 25 Sep 2017 07:36:06 GMT): zhuxubin01 (Mon, 25 Sep 2017 07:36:40 GMT): guoger (Mon, 25 Sep 2017 07:37:58 GMT): guoger (Mon, 25 Sep 2017 07:37:58 GMT): zhuxubin01 (Mon, 25 Sep 2017 07:40:00 GMT): zhuxubin01 (Mon, 25 Sep 2017 07:40:25 GMT): guoger (Mon, 25 Sep 2017 07:43:18 GMT): guoger (Mon, 25 Sep 2017 07:43:42 GMT): guoger (Mon, 25 Sep 2017 07:44:00 GMT): zhuxubin01 (Mon, 25 Sep 2017 07:44:28 GMT): guoger (Mon, 25 Sep 2017 07:47:40 GMT): guoger (Mon, 25 Sep 2017 07:47:47 GMT): guoger (Mon, 25 Sep 2017 07:48:14 GMT): zhuxubin01 (Mon, 25 Sep 2017 07:59:05 GMT): zhuxubin01 (Mon, 25 Sep 2017 07:59:13 GMT): Yafei.Chen (Mon, 25 Sep 2017 09:55:17 GMT): zhuxubin01 (Mon, 25 Sep 2017 13:08:52 GMT): it2911 (Tue, 26 Sep 2017 06:39:06 GMT): silentbalanceyh (Wed, 27 Sep 2017 03:54:16 GMT): Ryan--Yang (Wed, 27 Sep 2017 06:11:15 GMT): hxmhlt (Wed, 27 Sep 2017 13:07:50 GMT): Ryan--Yang (Thu, 28 Sep 2017 07:17:16 GMT): Ryan--Yang (Thu, 28 Sep 2017 07:17:16 GMT): Ryan--Yang (Thu, 28 Sep 2017 07:17:16 GMT): Ryan--Yang (Thu, 28 Sep 2017 07:17:16 GMT): Xeriou (Thu, 28 Sep 2017 07:58:23 GMT): Xeriou (Thu, 28 Sep 2017 07:58:23 GMT): mochechan-fusions360 (Thu, 28 Sep 2017 08:07:24 GMT): baohua (Thu, 28 Sep 2017 15:27:50 GMT): Glen (Fri, 29 Sep 2017 01:35:05 GMT): Glen (Fri, 29 Sep 2017 01:35:10 GMT): Hangyu (Fri, 29 Sep 2017 01:39:57 GMT): Glen (Fri, 29 Sep 2017 01:40:20 GMT): Glen (Fri, 29 Sep 2017 01:40:40 GMT): Hangyu (Fri, 29 Sep 2017 01:42:49 GMT): Glen (Fri, 29 Sep 2017 01:43:48 GMT): Hangyu (Fri, 29 Sep 2017 01:44:25 GMT): Glen (Fri, 29 Sep 2017 01:44:31 GMT): Hangyu (Fri, 29 Sep 2017 01:45:46 GMT): Glen (Fri, 29 Sep 2017 01:46:21 GMT): Glen (Fri, 29 Sep 2017 01:47:05 GMT): Glen (Fri, 29 Sep 2017 01:47:05 GMT): Glen (Fri, 29 Sep 2017 01:47:18 GMT): Glen (Fri, 29 Sep 2017 01:47:38 GMT): Glen (Fri, 29 Sep 2017 01:48:27 GMT): Hangyu (Fri, 29 Sep 2017 01:53:50 GMT): Glen (Fri, 29 Sep 2017 02:00:45 GMT): Glen (Fri, 29 Sep 2017 02:00:48 GMT): jessica (Wed, 04 Oct 2017 19:38:02 GMT): manish-sethi (Fri, 06 Oct 2017 00:26:17 GMT): KevinBai (Sat, 07 Oct 2017 08:34:09 GMT): KevinBai (Sun, 08 Oct 2017 03:29:45 GMT): chenshiok (Mon, 09 Oct 2017 01:42:49 GMT): shiyj93 (Mon, 09 Oct 2017 01:58:26 GMT): opengloves (Mon, 09 Oct 2017 05:29:41 GMT): hxmhlt (Mon, 09 Oct 2017 08:16:02 GMT): hxmhlt (Mon, 09 Oct 2017 08:17:18 GMT): hxmhlt (Mon, 09 Oct 2017 08:17:29 GMT): hxmhlt (Mon, 09 Oct 2017 08:17:55 GMT): hxmhlt (Mon, 09 Oct 2017 08:18:21 GMT): baohua (Mon, 09 Oct 2017 09:06:26 GMT): zhuxubin01 (Mon, 09 Oct 2017 09:27:53 GMT): zhuxubin01 (Mon, 09 Oct 2017 09:28:36 GMT): chenshiok (Mon, 09 Oct 2017 11:27:17 GMT): baohua (Tue, 10 Oct 2017 01:45:25 GMT): KevinBai (Tue, 10 Oct 2017 01:51:18 GMT): xiaoping378 (Wed, 11 Oct 2017 14:04:13 GMT): mredmundto (Thu, 12 Oct 2017 04:37:12 GMT): Glen (Thu, 12 Oct 2017 05:26:34 GMT): Glen (Thu, 12 Oct 2017 05:26:43 GMT): Glen (Thu, 12 Oct 2017 05:26:43 GMT): scott_xu (Thu, 12 Oct 2017 07:13:48 GMT): KevinBai (Sat, 14 Oct 2017 08:33:16 GMT): baohua (Sun, 15 Oct 2017 13:22:01 GMT): KevinBai (Sun, 15 Oct 2017 16:26:29 GMT): baohua (Mon, 16 Oct 2017 01:31:52 GMT): KevinBai (Mon, 16 Oct 2017 04:37:45 GMT): KevinBai (Mon, 16 Oct 2017 04:41:31 GMT): baohua (Mon, 16 Oct 2017 05:47:58 GMT): KevinBai (Mon, 16 Oct 2017 06:50:39 GMT): KevinBai (Mon, 16 Oct 2017 06:51:22 GMT): KevinBai (Mon, 16 Oct 2017 06:52:13 GMT): KevinBai (Mon, 16 Oct 2017 06:53:53 GMT): KevinBai (Mon, 16 Oct 2017 07:01:22 GMT): baohua (Mon, 16 Oct 2017 07:06:43 GMT): KevinBai (Mon, 16 Oct 2017 07:07:21 GMT): KevinBai (Mon, 16 Oct 2017 07:37:28 GMT): wabob2012 (Mon, 16 Oct 2017 08:15:32 GMT): shiyj (Mon, 16 Oct 2017 09:15:44 GMT): liuwenliang0632 (Tue, 17 Oct 2017 01:31:45 GMT): KevinBai (Tue, 17 Oct 2017 01:42:02 GMT): lin2K (Thu, 19 Oct 2017 08:47:00 GMT): tangtao (Fri, 20 Oct 2017 10:05:45 GMT): realhuyi (Sat, 21 Oct 2017 11:59:22 GMT): baohua (Mon, 23 Oct 2017 20:35:06 GMT): opengloves (Tue, 24 Oct 2017 07:28:20 GMT): opengloves (Tue, 24 Oct 2017 07:28:20 GMT): opengloves (Tue, 24 Oct 2017 07:32:19 GMT): opengloves (Tue, 24 Oct 2017 07:32:54 GMT): opengloves (Tue, 24 Oct 2017 07:33:50 GMT): CarlXK (Tue, 24 Oct 2017 08:36:35 GMT): baohua (Tue, 24 Oct 2017 14:37:55 GMT): baohua (Tue, 24 Oct 2017 14:38:36 GMT): baohua (Tue, 24 Oct 2017 14:39:31 GMT): liutc (Wed, 25 Oct 2017 01:48:49 GMT): CarlXK (Wed, 25 Oct 2017 01:49:53 GMT): baohua (Wed, 25 Oct 2017 01:49:54 GMT): liutc (Wed, 25 Oct 2017 01:50:55 GMT): jimthematrix (Wed, 25 Oct 2017 01:50:57 GMT): jimthematrix (Wed, 25 Oct 2017 01:52:20 GMT): liutc (Wed, 25 Oct 2017 01:52:35 GMT): jimthematrix (Wed, 25 Oct 2017 01:53:27 GMT): CarlXK (Wed, 25 Oct 2017 01:55:00 GMT): liutc (Wed, 25 Oct 2017 01:55:45 GMT): CarlXK (Wed, 25 Oct 2017 01:55:55 GMT): jimthematrix (Wed, 25 Oct 2017 01:56:24 GMT): baoyangc (Wed, 25 Oct 2017 01:56:30 GMT): jimthematrix (Wed, 25 Oct 2017 01:56:53 GMT): jimthematrix (Wed, 25 Oct 2017 01:57:33 GMT): CarlXK (Wed, 25 Oct 2017 01:57:50 GMT): liutc (Wed, 25 Oct 2017 01:58:02 GMT): jimthematrix (Wed, 25 Oct 2017 01:58:45 GMT): CarlXK (Wed, 25 Oct 2017 01:59:24 GMT): liutc (Wed, 25 Oct 2017 02:00:13 GMT): CarlXK (Wed, 25 Oct 2017 02:00:35 GMT): CarlXK (Wed, 25 Oct 2017 02:00:50 GMT): jimthematrix (Wed, 25 Oct 2017 02:01:50 GMT): jimthematrix (Wed, 25 Oct 2017 02:02:27 GMT): jimthematrix (Wed, 25 Oct 2017 02:02:27 GMT): CarlXK (Wed, 25 Oct 2017 02:03:54 GMT): CarlXK (Wed, 25 Oct 2017 02:03:54 GMT): baoyangc (Wed, 25 Oct 2017 02:08:43 GMT): lin2K (Wed, 25 Oct 2017 06:45:48 GMT): lin2K (Wed, 25 Oct 2017 06:45:57 GMT): CarlXK (Thu, 26 Oct 2017 01:39:47 GMT): CarlXK (Thu, 26 Oct 2017 01:39:47 GMT): labcoinpoc (Thu, 26 Oct 2017 07:17:59 GMT): labcoinpoc (Thu, 26 Oct 2017 08:12:48 GMT): labcoinpoc (Thu, 26 Oct 2017 08:13:41 GMT): RocMax (Thu, 26 Oct 2017 09:30:20 GMT): baoyangc (Thu, 26 Oct 2017 10:50:03 GMT): baoyangc (Thu, 26 Oct 2017 10:50:31 GMT): huangpeng (Thu, 26 Oct 2017 15:12:12 GMT): baoyangc (Fri, 27 Oct 2017 02:02:05 GMT): baoyangc (Fri, 27 Oct 2017 02:02:26 GMT): jimthematrix (Fri, 27 Oct 2017 02:15:36 GMT): jimthematrix (Fri, 27 Oct 2017 02:17:20 GMT): jimthematrix (Fri, 27 Oct 2017 02:17:41 GMT): labcoinpoc (Fri, 27 Oct 2017 02:20:41 GMT): labcoinpoc (Fri, 27 Oct 2017 02:21:14 GMT): labcoinpoc (Fri, 27 Oct 2017 02:46:53 GMT): chalene (Fri, 27 Oct 2017 08:17:00 GMT): ziyuan (Sun, 29 Oct 2017 14:41:24 GMT): jimthematrix (Mon, 30 Oct 2017 15:58:59 GMT): jimthematrix (Mon, 30 Oct 2017 15:58:59 GMT): labcoinpoc (Tue, 31 Oct 2017 00:36:39 GMT): labcoinpoc (Tue, 31 Oct 2017 07:35:12 GMT): zhuxubin01 (Thu, 02 Nov 2017 07:27:39 GMT): zhuxubin01 (Thu, 02 Nov 2017 07:27:43 GMT): labcoinpoc (Thu, 02 Nov 2017 07:36:26 GMT): zhuxubin01 (Thu, 02 Nov 2017 07:41:01 GMT): zhuxubin01 (Thu, 02 Nov 2017 07:41:38 GMT): zhuxubin01 (Thu, 02 Nov 2017 07:41:50 GMT): labcoinpoc (Thu, 02 Nov 2017 07:44:09 GMT): labcoinpoc (Thu, 02 Nov 2017 07:45:29 GMT): zhuxubin01 (Thu, 02 Nov 2017 07:46:32 GMT): zhuxubin01 (Thu, 02 Nov 2017 07:48:14 GMT): labcoinpoc (Thu, 02 Nov 2017 07:58:03 GMT): labcoinpoc (Thu, 02 Nov 2017 08:11:10 GMT): zhuxubin01 (Thu, 02 Nov 2017 08:32:35 GMT): zhuxubin01 (Thu, 02 Nov 2017 08:34:22 GMT): labcoinpoc (Thu, 02 Nov 2017 08:36:12 GMT): zhuxubin01 (Thu, 02 Nov 2017 08:38:30 GMT): labcoinpoc (Thu, 02 Nov 2017 09:19:15 GMT): labcoinpoc (Thu, 02 Nov 2017 09:20:11 GMT): labcoinpoc (Thu, 02 Nov 2017 09:21:04 GMT): zhuxubin01 (Thu, 02 Nov 2017 09:26:05 GMT): KevinBai (Fri, 03 Nov 2017 03:33:06 GMT): Randyshu2018 (Fri, 03 Nov 2017 03:33:18 GMT): ylsGit (Fri, 03 Nov 2017 03:50:44 GMT): KevinBai (Fri, 03 Nov 2017 03:59:37 GMT): KevinBai (Fri, 03 Nov 2017 03:59:41 GMT): ylsGit (Fri, 03 Nov 2017 04:00:34 GMT): ylsGit (Fri, 03 Nov 2017 04:01:46 GMT): ylsGit (Fri, 03 Nov 2017 04:02:23 GMT): KevinBai (Fri, 03 Nov 2017 04:04:30 GMT): ylsGit (Fri, 03 Nov 2017 04:17:35 GMT): fangyincheng (Sat, 04 Nov 2017 03:53:14 GMT): baohua (Sun, 05 Nov 2017 12:46:00 GMT): baohua (Mon, 06 Nov 2017 01:45:16 GMT): guoger (Mon, 06 Nov 2017 01:46:32 GMT): liutc (Mon, 06 Nov 2017 03:07:46 GMT): baohua (Mon, 06 Nov 2017 04:49:34 GMT): lin2K (Mon, 06 Nov 2017 08:34:07 GMT): lin2K (Mon, 06 Nov 2017 08:40:47 GMT): baohua (Mon, 06 Nov 2017 08:42:49 GMT): lin2K (Mon, 06 Nov 2017 08:44:04 GMT): lin2K (Mon, 06 Nov 2017 08:49:33 GMT): zhaochy (Mon, 06 Nov 2017 09:24:08 GMT): zhaochy (Mon, 06 Nov 2017 09:26:24 GMT): tongli (Mon, 06 Nov 2017 14:04:56 GMT): Haghighat (Mon, 06 Nov 2017 14:04:56 GMT): tongli (Mon, 06 Nov 2017 14:05:23 GMT): CryptoSha (Mon, 06 Nov 2017 18:09:48 GMT): labcoinpoc (Tue, 07 Nov 2017 00:36:53 GMT): qingsongGuo (Tue, 07 Nov 2017 02:44:21 GMT): labcoinpoc (Tue, 07 Nov 2017 02:44:52 GMT): qingsongGuo (Tue, 07 Nov 2017 02:45:51 GMT): qingsongGuo (Tue, 07 Nov 2017 02:46:16 GMT): labcoinpoc (Tue, 07 Nov 2017 02:46:38 GMT): qingsongGuo (Tue, 07 Nov 2017 02:46:43 GMT): qingsongGuo (Tue, 07 Nov 2017 02:46:53 GMT): qingsongGuo (Tue, 07 Nov 2017 02:47:17 GMT): labcoinpoc (Tue, 07 Nov 2017 02:47:24 GMT): qingsongGuo (Tue, 07 Nov 2017 02:47:31 GMT): labcoinpoc (Tue, 07 Nov 2017 02:47:50 GMT): qingsongGuo (Tue, 07 Nov 2017 02:47:56 GMT): labcoinpoc (Tue, 07 Nov 2017 02:48:30 GMT): qingsongGuo (Tue, 07 Nov 2017 02:48:56 GMT): qingsongGuo (Tue, 07 Nov 2017 02:49:03 GMT): qingsongGuo (Tue, 07 Nov 2017 02:49:07 GMT): qingsongGuo (Tue, 07 Nov 2017 02:49:29 GMT): labcoinpoc (Tue, 07 Nov 2017 02:56:44 GMT): labcoinpoc (Tue, 07 Nov 2017 02:57:25 GMT): labcoinpoc (Tue, 07 Nov 2017 03:03:26 GMT): qingsongGuo (Tue, 07 Nov 2017 03:17:51 GMT): qingsongGuo (Tue, 07 Nov 2017 03:18:00 GMT): qingsongGuo (Tue, 07 Nov 2017 03:18:13 GMT): qingsongGuo (Tue, 07 Nov 2017 03:18:32 GMT): labcoinpoc (Tue, 07 Nov 2017 03:40:52 GMT): labcoinpoc (Tue, 07 Nov 2017 03:42:12 GMT): qingsongGuo (Tue, 07 Nov 2017 03:47:05 GMT): labcoinpoc (Tue, 07 Nov 2017 04:11:41 GMT): zhuxubin01 (Tue, 07 Nov 2017 06:09:10 GMT): qingsongGuo (Tue, 07 Nov 2017 06:10:02 GMT): zhuxubin01 (Tue, 07 Nov 2017 06:10:14 GMT): zhuxubin01 (Tue, 07 Nov 2017 06:10:41 GMT): zhuxubin01 (Tue, 07 Nov 2017 06:10:59 GMT): qingsongGuo (Tue, 07 Nov 2017 06:11:52 GMT): zhuxubin01 (Tue, 07 Nov 2017 06:13:09 GMT): labcoinpoc (Tue, 07 Nov 2017 06:22:06 GMT): labcoinpoc (Tue, 07 Nov 2017 06:22:36 GMT): labcoinpoc (Tue, 07 Nov 2017 06:24:10 GMT): qingsongGuo (Tue, 07 Nov 2017 06:28:43 GMT): qingsongGuo (Tue, 07 Nov 2017 06:29:14 GMT): qingsongGuo (Tue, 07 Nov 2017 06:31:08 GMT): qingsongGuo (Tue, 07 Nov 2017 06:32:17 GMT): qingsongGuo (Tue, 07 Nov 2017 06:32:26 GMT): qingsongGuo (Tue, 07 Nov 2017 06:32:35 GMT): labcoinpoc (Tue, 07 Nov 2017 06:37:06 GMT): labcoinpoc (Tue, 07 Nov 2017 06:38:30 GMT): qingsongGuo (Tue, 07 Nov 2017 06:43:35 GMT): qingsongGuo (Tue, 07 Nov 2017 06:44:33 GMT): labcoinpoc (Tue, 07 Nov 2017 06:45:51 GMT): qingsongGuo (Tue, 07 Nov 2017 06:45:57 GMT): qingsongGuo (Tue, 07 Nov 2017 06:46:32 GMT): labcoinpoc (Tue, 07 Nov 2017 06:47:08 GMT): qingsongGuo (Tue, 07 Nov 2017 06:47:31 GMT): qingsongGuo (Tue, 07 Nov 2017 06:47:52 GMT): labcoinpoc (Tue, 07 Nov 2017 06:48:15 GMT): qingsongGuo (Tue, 07 Nov 2017 06:50:07 GMT): qingsongGuo (Tue, 07 Nov 2017 06:50:33 GMT): labcoinpoc (Tue, 07 Nov 2017 06:51:00 GMT): labcoinpoc (Tue, 07 Nov 2017 06:54:46 GMT): labcoinpoc (Tue, 07 Nov 2017 06:55:35 GMT): qingsongGuo (Tue, 07 Nov 2017 06:55:44 GMT): qingsongGuo (Tue, 07 Nov 2017 06:56:16 GMT): qingsongGuo (Tue, 07 Nov 2017 06:56:31 GMT): labcoinpoc (Tue, 07 Nov 2017 06:56:42 GMT): labcoinpoc (Tue, 07 Nov 2017 06:58:25 GMT): qingsongGuo (Tue, 07 Nov 2017 06:58:35 GMT): labcoinpoc (Tue, 07 Nov 2017 06:59:13 GMT): qingsongGuo (Tue, 07 Nov 2017 06:59:25 GMT): labcoinpoc (Tue, 07 Nov 2017 07:00:17 GMT): qingsongGuo (Tue, 07 Nov 2017 07:02:18 GMT): labcoinpoc (Tue, 07 Nov 2017 07:02:39 GMT): labcoinpoc (Tue, 07 Nov 2017 07:03:35 GMT): labcoinpoc (Tue, 07 Nov 2017 07:03:38 GMT): labcoinpoc (Tue, 07 Nov 2017 07:05:28 GMT): labcoinpoc (Tue, 07 Nov 2017 07:05:47 GMT): qingsongGuo (Tue, 07 Nov 2017 07:08:39 GMT): qingsongGuo (Tue, 07 Nov 2017 07:09:21 GMT): labcoinpoc (Tue, 07 Nov 2017 07:09:25 GMT): qingsongGuo (Tue, 07 Nov 2017 07:11:30 GMT): labcoinpoc (Tue, 07 Nov 2017 07:11:42 GMT): labcoinpoc (Tue, 07 Nov 2017 07:12:17 GMT): labcoinpoc (Tue, 07 Nov 2017 07:14:39 GMT): qingsongGuo (Tue, 07 Nov 2017 07:21:37 GMT): qingsongGuo (Tue, 07 Nov 2017 07:21:54 GMT): qingsongGuo (Tue, 07 Nov 2017 07:22:36 GMT): labcoinpoc (Tue, 07 Nov 2017 07:30:13 GMT): labcoinpoc (Tue, 07 Nov 2017 07:30:47 GMT): labcoinpoc (Tue, 07 Nov 2017 07:31:04 GMT): labcoinpoc (Tue, 07 Nov 2017 07:31:19 GMT): qingsongGuo (Tue, 07 Nov 2017 07:33:37 GMT): qingsongGuo (Tue, 07 Nov 2017 07:34:06 GMT): labcoinpoc (Tue, 07 Nov 2017 07:35:38 GMT): labcoinpoc (Tue, 07 Nov 2017 07:35:38 GMT): labcoinpoc (Tue, 07 Nov 2017 07:35:49 GMT): qingsongGuo (Tue, 07 Nov 2017 07:38:05 GMT): labcoinpoc (Tue, 07 Nov 2017 07:39:18 GMT): qingsongGuo (Tue, 07 Nov 2017 07:39:56 GMT): zhuxubin01 (Tue, 07 Nov 2017 07:41:20 GMT): qingsongGuo (Tue, 07 Nov 2017 07:41:51 GMT): qingsongGuo (Tue, 07 Nov 2017 07:41:57 GMT): zhuxubin01 (Tue, 07 Nov 2017 07:42:04 GMT): zhuxubin01 (Tue, 07 Nov 2017 07:42:22 GMT): qingsongGuo (Tue, 07 Nov 2017 07:42:28 GMT): qingsongGuo (Tue, 07 Nov 2017 07:42:33 GMT): zhuxubin01 (Tue, 07 Nov 2017 07:42:39 GMT): zhuxubin01 (Tue, 07 Nov 2017 07:42:53 GMT): zhuxubin01 (Tue, 07 Nov 2017 07:43:27 GMT): zhuxubin01 (Tue, 07 Nov 2017 07:43:50 GMT): zhuxubin01 (Tue, 07 Nov 2017 07:44:14 GMT): labcoinpoc (Tue, 07 Nov 2017 07:44:17 GMT): qingsongGuo (Tue, 07 Nov 2017 07:46:06 GMT): qingsongGuo (Tue, 07 Nov 2017 07:46:38 GMT): labcoinpoc (Tue, 07 Nov 2017 07:46:50 GMT): labcoinpoc (Tue, 07 Nov 2017 07:47:12 GMT): labcoinpoc (Tue, 07 Nov 2017 07:48:48 GMT): zhuxubin01 (Tue, 07 Nov 2017 07:49:10 GMT): qingsongGuo (Tue, 07 Nov 2017 07:53:08 GMT): qingsongGuo (Tue, 07 Nov 2017 07:53:30 GMT): qingsongGuo (Tue, 07 Nov 2017 07:53:42 GMT): qingsongGuo (Tue, 07 Nov 2017 08:50:26 GMT): qingsongGuo (Tue, 07 Nov 2017 08:50:41 GMT): labcoinpoc (Tue, 07 Nov 2017 08:54:46 GMT): qingsongGuo (Tue, 07 Nov 2017 09:27:03 GMT): qingsongGuo (Tue, 07 Nov 2017 09:28:00 GMT): qingsongGuo (Tue, 07 Nov 2017 09:28:12 GMT): qingsongGuo (Tue, 07 Nov 2017 09:41:45 GMT): qingsongGuo (Tue, 07 Nov 2017 09:42:09 GMT): qingsongGuo (Tue, 07 Nov 2017 09:42:13 GMT): zhuxubin01 (Tue, 07 Nov 2017 09:46:45 GMT): labcoinpoc (Tue, 07 Nov 2017 09:54:42 GMT): qingsongGuo (Tue, 07 Nov 2017 10:24:45 GMT): jimthematrix (Tue, 07 Nov 2017 15:19:41 GMT): jimthematrix (Tue, 07 Nov 2017 15:22:49 GMT): jimthematrix (Tue, 07 Nov 2017 15:25:11 GMT): jimthematrix (Tue, 07 Nov 2017 15:33:19 GMT): labcoinpoc (Wed, 08 Nov 2017 00:34:36 GMT): jimthematrix (Wed, 08 Nov 2017 14:33:07 GMT): lcj (Thu, 09 Nov 2017 01:15:55 GMT): lcj (Thu, 09 Nov 2017 01:16:42 GMT): labcoinpoc (Thu, 09 Nov 2017 01:21:25 GMT): lcj (Thu, 09 Nov 2017 01:22:27 GMT): labcoinpoc (Thu, 09 Nov 2017 01:22:50 GMT): lcj (Thu, 09 Nov 2017 01:22:57 GMT): lcj (Thu, 09 Nov 2017 01:23:08 GMT): labcoinpoc (Thu, 09 Nov 2017 01:23:38 GMT): lcj (Thu, 09 Nov 2017 01:24:13 GMT): lcj (Thu, 09 Nov 2017 01:25:04 GMT): labcoinpoc (Thu, 09 Nov 2017 01:26:48 GMT): lcj (Thu, 09 Nov 2017 01:29:16 GMT): labcoinpoc (Thu, 09 Nov 2017 02:54:52 GMT): baohua (Thu, 09 Nov 2017 03:25:15 GMT): lcj (Thu, 09 Nov 2017 04:07:49 GMT): labcoinpoc (Thu, 09 Nov 2017 04:26:17 GMT): labcoinpoc (Thu, 09 Nov 2017 04:26:17 GMT): nauqnew (Thu, 09 Nov 2017 06:40:59 GMT): nauqnew (Thu, 09 Nov 2017 06:53:15 GMT): nauqnew (Thu, 09 Nov 2017 06:59:27 GMT): nauqnew (Thu, 09 Nov 2017 07:06:33 GMT): nauqnew (Thu, 09 Nov 2017 07:08:54 GMT): Bllose (Thu, 09 Nov 2017 09:00:29 GMT): Bllose (Thu, 09 Nov 2017 09:01:27 GMT): qingsongGuo (Thu, 09 Nov 2017 09:10:29 GMT): lcj (Fri, 10 Nov 2017 01:07:33 GMT): labcoinpoc (Fri, 10 Nov 2017 01:18:01 GMT): lcj (Fri, 10 Nov 2017 01:19:35 GMT): lcj (Fri, 10 Nov 2017 01:20:05 GMT): labcoinpoc (Fri, 10 Nov 2017 01:25:01 GMT): lcj (Fri, 10 Nov 2017 01:30:43 GMT): labcoinpoc (Fri, 10 Nov 2017 01:34:56 GMT): lcj (Fri, 10 Nov 2017 01:37:22 GMT): lcj (Fri, 10 Nov 2017 01:37:49 GMT): lcj (Fri, 10 Nov 2017 01:39:40 GMT): labcoinpoc (Fri, 10 Nov 2017 01:41:22 GMT): labcoinpoc (Fri, 10 Nov 2017 01:42:07 GMT): labcoinpoc (Fri, 10 Nov 2017 01:42:07 GMT): lcj (Fri, 10 Nov 2017 01:43:25 GMT): lcj (Fri, 10 Nov 2017 01:45:23 GMT): labcoinpoc (Fri, 10 Nov 2017 02:29:07 GMT): lcj (Fri, 10 Nov 2017 02:37:11 GMT): lcj (Fri, 10 Nov 2017 02:38:23 GMT): lcj (Fri, 10 Nov 2017 02:42:50 GMT): labcoinpoc (Fri, 10 Nov 2017 02:44:57 GMT): labcoinpoc (Fri, 10 Nov 2017 02:46:33 GMT): lcj (Fri, 10 Nov 2017 02:55:34 GMT): legend-linux (Sat, 11 Nov 2017 03:19:42 GMT): legend-linux (Sat, 11 Nov 2017 03:20:49 GMT): Tianjian (Sat, 11 Nov 2017 08:53:21 GMT): Tianjian (Sat, 11 Nov 2017 09:11:03 GMT): barry_liang (Mon, 13 Nov 2017 01:26:02 GMT): baohua (Mon, 13 Nov 2017 01:59:11 GMT): barry_liang (Mon, 13 Nov 2017 02:56:52 GMT): baohua (Mon, 13 Nov 2017 03:07:31 GMT): barry_liang (Mon, 13 Nov 2017 03:20:32 GMT): lcj (Mon, 13 Nov 2017 08:07:26 GMT): lcj (Mon, 13 Nov 2017 08:09:10 GMT): asaningmaxchain (Mon, 13 Nov 2017 11:17:33 GMT): nauqnew (Mon, 13 Nov 2017 12:45:34 GMT): myin2000 (Mon, 13 Nov 2017 20:28:15 GMT): lcj (Tue, 14 Nov 2017 01:29:05 GMT): asaningmaxchain (Tue, 14 Nov 2017 01:29:28 GMT): lcj (Tue, 14 Nov 2017 01:29:49 GMT): lcj (Tue, 14 Nov 2017 01:48:19 GMT): labcoinpoc (Tue, 14 Nov 2017 02:03:45 GMT): labcoinpoc (Tue, 14 Nov 2017 02:03:45 GMT): labcoinpoc (Tue, 14 Nov 2017 02:03:45 GMT): lcj (Tue, 14 Nov 2017 02:06:41 GMT): labcoinpoc (Tue, 14 Nov 2017 02:07:07 GMT): lcj (Tue, 14 Nov 2017 02:07:12 GMT): lcj (Tue, 14 Nov 2017 02:08:32 GMT): lcj (Tue, 14 Nov 2017 02:08:50 GMT): labcoinpoc (Tue, 14 Nov 2017 02:09:08 GMT): lcj (Tue, 14 Nov 2017 02:10:26 GMT): labcoinpoc (Tue, 14 Nov 2017 02:12:43 GMT): lcj (Tue, 14 Nov 2017 02:15:51 GMT): labcoinpoc (Tue, 14 Nov 2017 02:36:42 GMT): labcoinpoc (Tue, 14 Nov 2017 02:41:28 GMT): lcj (Tue, 14 Nov 2017 02:45:41 GMT): lin2K (Tue, 14 Nov 2017 08:45:43 GMT): xchao0213 (Wed, 15 Nov 2017 03:33:16 GMT): flyq (Wed, 15 Nov 2017 06:30:48 GMT): flyq (Wed, 15 Nov 2017 06:32:32 GMT): zhoujunshan (Wed, 15 Nov 2017 07:21:52 GMT): zhoujunshan (Wed, 15 Nov 2017 07:51:16 GMT): lcj (Wed, 15 Nov 2017 09:19:47 GMT): lcj (Wed, 15 Nov 2017 09:22:06 GMT): zhoujunshan (Wed, 15 Nov 2017 09:25:04 GMT): tedljw (Wed, 15 Nov 2017 09:28:17 GMT): lcj (Wed, 15 Nov 2017 09:29:29 GMT): lcj (Wed, 15 Nov 2017 09:31:13 GMT): lcj (Wed, 15 Nov 2017 09:31:32 GMT): lcj (Wed, 15 Nov 2017 09:32:35 GMT): tedljw (Wed, 15 Nov 2017 09:34:54 GMT): marryton007 (Thu, 16 Nov 2017 01:50:29 GMT): tedljw (Thu, 16 Nov 2017 06:08:11 GMT): lcj (Thu, 16 Nov 2017 06:32:02 GMT): lcj (Thu, 16 Nov 2017 06:33:02 GMT): marryton007 (Thu, 16 Nov 2017 06:54:43 GMT): marryton007 (Thu, 16 Nov 2017 06:57:59 GMT): tedljw (Fri, 17 Nov 2017 00:12:57 GMT): tedljw (Fri, 17 Nov 2017 00:50:27 GMT): marryton007 (Fri, 17 Nov 2017 01:37:19 GMT): lcj (Fri, 17 Nov 2017 01:49:09 GMT): marryton007 (Fri, 17 Nov 2017 01:52:36 GMT): leo (Fri, 17 Nov 2017 02:19:40 GMT): leo (Fri, 17 Nov 2017 02:20:52 GMT): leo (Fri, 17 Nov 2017 02:21:31 GMT): tedljw (Fri, 17 Nov 2017 02:26:53 GMT): leo (Fri, 17 Nov 2017 02:34:54 GMT): leo (Fri, 17 Nov 2017 02:36:03 GMT): tedljw (Fri, 17 Nov 2017 02:42:04 GMT): leo (Fri, 17 Nov 2017 03:36:12 GMT): RocMax (Fri, 17 Nov 2017 04:30:40 GMT): leo (Fri, 17 Nov 2017 06:06:07 GMT): tedljw (Fri, 17 Nov 2017 09:00:51 GMT): RocMax (Fri, 17 Nov 2017 09:26:42 GMT): xchao0213 (Fri, 17 Nov 2017 09:28:38 GMT): xchao0213 (Fri, 17 Nov 2017 10:11:19 GMT): leo (Sat, 18 Nov 2017 03:42:59 GMT): mredmundto85 (Sun, 19 Nov 2017 08:36:46 GMT): baohua (Mon, 20 Nov 2017 01:34:38 GMT): nauqnew (Mon, 20 Nov 2017 09:06:38 GMT): marryton007 (Tue, 21 Nov 2017 06:46:59 GMT): ylsGit (Tue, 21 Nov 2017 10:32:48 GMT): ylsGit (Tue, 21 Nov 2017 11:05:27 GMT): grapebaba (Tue, 21 Nov 2017 11:16:24 GMT): grapebaba (Tue, 21 Nov 2017 11:16:39 GMT): ylsGit (Wed, 22 Nov 2017 01:55:07 GMT): baoyangc (Wed, 22 Nov 2017 04:00:24 GMT): baoyangc (Wed, 22 Nov 2017 04:00:34 GMT): yangjiannr (Wed, 22 Nov 2017 09:20:51 GMT): cumt168 (Wed, 22 Nov 2017 12:18:58 GMT): cumt168 (Wed, 22 Nov 2017 12:19:12 GMT): cumt168 (Wed, 22 Nov 2017 12:19:23 GMT): cumt168 (Wed, 22 Nov 2017 12:23:04 GMT): cumt168 (Wed, 22 Nov 2017 12:23:31 GMT): baoyangc (Thu, 23 Nov 2017 01:45:11 GMT): LinfengLiang (Thu, 23 Nov 2017 09:49:29 GMT): tywang (Fri, 24 Nov 2017 04:29:21 GMT): CarlXK (Fri, 24 Nov 2017 07:21:30 GMT): HenryJuan (Tue, 28 Nov 2017 01:01:44 GMT): baoyangc (Tue, 28 Nov 2017 03:25:27 GMT): baoyangc (Tue, 28 Nov 2017 03:26:20 GMT): baoyangc (Tue, 28 Nov 2017 03:26:36 GMT): ylsGit (Tue, 28 Nov 2017 08:53:17 GMT): zeroest (Wed, 29 Nov 2017 07:49:06 GMT): Luke_Chen (Thu, 30 Nov 2017 06:34:33 GMT): lcj (Tue, 05 Dec 2017 01:18:59 GMT): baohua (Tue, 05 Dec 2017 03:25:23 GMT): barry_liang (Tue, 05 Dec 2017 09:24:21 GMT): barry_liang (Tue, 05 Dec 2017 09:24:31 GMT): baohua (Wed, 06 Dec 2017 04:11:02 GMT): tian (Wed, 06 Dec 2017 12:01:23 GMT): baohua (Thu, 07 Dec 2017 03:36:34 GMT): liutc (Thu, 07 Dec 2017 03:41:13 GMT): ZheliangLiu (Thu, 07 Dec 2017 05:23:40 GMT): tedljw (Thu, 07 Dec 2017 05:34:36 GMT): ZheliangLiu (Thu, 07 Dec 2017 05:39:09 GMT): tedljw (Thu, 07 Dec 2017 05:39:42 GMT): ZheliangLiu (Thu, 07 Dec 2017 05:39:53 GMT): ZheliangLiu (Thu, 07 Dec 2017 05:50:11 GMT): baohua (Thu, 07 Dec 2017 06:23:27 GMT): liutc (Thu, 07 Dec 2017 12:28:02 GMT): baohua (Fri, 08 Dec 2017 01:52:06 GMT): qurikuduo (Fri, 08 Dec 2017 02:05:57 GMT): qurikuduo (Fri, 08 Dec 2017 02:06:45 GMT): qurikuduo (Fri, 08 Dec 2017 02:08:23 GMT): baohua (Sun, 10 Dec 2017 01:18:53 GMT): baohua (Sun, 10 Dec 2017 01:19:08 GMT): baohua (Sun, 10 Dec 2017 01:20:45 GMT): liutc (Mon, 11 Dec 2017 02:32:25 GMT): guolidong (Tue, 12 Dec 2017 10:13:44 GMT): cs-wang (Wed, 13 Dec 2017 09:19:02 GMT): cs-wang (Wed, 13 Dec 2017 09:29:03 GMT): dijun (Wed, 13 Dec 2017 09:44:40 GMT): cs-wang (Wed, 13 Dec 2017 09:47:44 GMT): Norberthu (Wed, 13 Dec 2017 10:00:25 GMT): dijun (Wed, 13 Dec 2017 10:09:50 GMT): cs-wang (Wed, 13 Dec 2017 10:28:02 GMT): baohua (Wed, 13 Dec 2017 14:48:43 GMT): baohua (Wed, 13 Dec 2017 14:49:03 GMT): yingmsky (Thu, 14 Dec 2017 09:14:54 GMT): lcj (Fri, 15 Dec 2017 08:13:01 GMT): lcj (Fri, 15 Dec 2017 08:15:23 GMT): lcj (Fri, 15 Dec 2017 08:45:15 GMT): baohua (Fri, 15 Dec 2017 08:55:57 GMT): lcj (Fri, 15 Dec 2017 09:00:53 GMT): dijun (Fri, 15 Dec 2017 09:01:01 GMT): dijun (Fri, 15 Dec 2017 09:04:23 GMT): lcj (Fri, 15 Dec 2017 09:05:52 GMT): dijun (Fri, 15 Dec 2017 09:06:48 GMT): lcj (Fri, 15 Dec 2017 09:06:52 GMT): dijun (Fri, 15 Dec 2017 09:07:54 GMT): lcj (Fri, 15 Dec 2017 09:09:16 GMT): Norberthu (Fri, 15 Dec 2017 12:26:21 GMT): Norberthu (Fri, 15 Dec 2017 12:28:42 GMT): ZheliangLiu (Sat, 16 Dec 2017 00:13:01 GMT): Norberthu (Mon, 18 Dec 2017 01:57:49 GMT): labcoinpoc (Mon, 18 Dec 2017 02:05:56 GMT): ZheliangLiu (Mon, 18 Dec 2017 02:08:25 GMT): baohua (Mon, 18 Dec 2017 04:29:07 GMT): happy975 (Tue, 19 Dec 2017 09:26:15 GMT): guolidong (Wed, 20 Dec 2017 04:04:17 GMT): guolidong (Wed, 20 Dec 2017 04:05:20 GMT): wbwangk (Thu, 21 Dec 2017 13:42:09 GMT): wbwangk (Thu, 21 Dec 2017 13:42:58 GMT): wbwangk (Thu, 21 Dec 2017 13:47:49 GMT): labcoinpoc (Fri, 22 Dec 2017 00:40:05 GMT): wbwangk (Fri, 22 Dec 2017 01:00:15 GMT): zeroest (Sun, 24 Dec 2017 11:48:02 GMT): baohua (Mon, 25 Dec 2017 01:18:30 GMT): xeonpitar (Mon, 25 Dec 2017 02:12:44 GMT): zeroest (Mon, 25 Dec 2017 10:56:02 GMT): baohua (Tue, 26 Dec 2017 05:22:35 GMT): liurf (Tue, 26 Dec 2017 06:28:22 GMT): liurf (Tue, 26 Dec 2017 06:28:58 GMT): baohua (Tue, 26 Dec 2017 08:40:08 GMT): Canxing (Tue, 26 Dec 2017 13:45:13 GMT): liurf (Wed, 27 Dec 2017 02:27:11 GMT): peter.li (Wed, 27 Dec 2017 06:27:45 GMT): baohua (Thu, 28 Dec 2017 13:23:39 GMT): dexhunter (Sat, 30 Dec 2017 07:51:44 GMT): amongv587 (Sun, 31 Dec 2017 02:00:17 GMT): baohua (Tue, 02 Jan 2018 00:48:18 GMT): WalkerLiu (Tue, 02 Jan 2018 05:31:21 GMT): WalkerLiu (Tue, 02 Jan 2018 05:36:24 GMT): songyuanjie (Wed, 03 Jan 2018 00:26:20 GMT): baohua (Wed, 03 Jan 2018 00:42:56 GMT): WalkerLiu (Wed, 03 Jan 2018 02:55:11 GMT): DanielXLee (Wed, 03 Jan 2018 03:20:03 GMT): Eleonora (Thu, 04 Jan 2018 15:13:41 GMT): Eleonora (Thu, 04 Jan 2018 15:14:14 GMT): italycappuccino (Tue, 09 Jan 2018 11:02:25 GMT): weixuan58 (Tue, 09 Jan 2018 16:03:30 GMT): weixuan58 (Tue, 09 Jan 2018 16:03:39 GMT): lcj (Wed, 10 Jan 2018 07:21:24 GMT): baohua (Wed, 10 Jan 2018 07:27:06 GMT): lcj (Wed, 10 Jan 2018 07:29:53 GMT): duwenhui (Thu, 11 Jan 2018 03:56:48 GMT): duwenhui (Thu, 11 Jan 2018 06:02:24 GMT): emmansun (Thu, 11 Jan 2018 06:18:22 GMT): emmansun (Thu, 11 Jan 2018 06:30:41 GMT): margase (Fri, 12 Jan 2018 02:52:45 GMT): crj (Fri, 12 Jan 2018 04:39:11 GMT): crj (Fri, 12 Jan 2018 04:41:34 GMT): Mathroz1206 (Fri, 12 Jan 2018 09:05:50 GMT): KrisLuan (Fri, 12 Jan 2018 15:13:20 GMT): wbwangk (Mon, 15 Jan 2018 02:01:10 GMT): emmansun (Mon, 15 Jan 2018 02:03:43 GMT): wbwangk (Mon, 15 Jan 2018 02:05:25 GMT): wbwangk (Mon, 15 Jan 2018 02:07:04 GMT): wbwangk (Mon, 15 Jan 2018 02:09:17 GMT): emmansun (Mon, 15 Jan 2018 02:10:54 GMT): wbwangk (Mon, 15 Jan 2018 02:10:55 GMT): labcoinpoc (Mon, 15 Jan 2018 02:11:52 GMT): wbwangk (Mon, 15 Jan 2018 02:12:23 GMT): labcoinpoc (Mon, 15 Jan 2018 02:12:24 GMT): wbwangk (Mon, 15 Jan 2018 02:13:51 GMT): labcoinpoc (Mon, 15 Jan 2018 02:15:43 GMT): emmansun (Mon, 15 Jan 2018 02:16:43 GMT): wbwangk (Mon, 15 Jan 2018 02:18:14 GMT): emmansun (Mon, 15 Jan 2018 02:19:28 GMT): labcoinpoc (Mon, 15 Jan 2018 02:19:44 GMT): emmansun (Mon, 15 Jan 2018 02:20:50 GMT): labcoinpoc (Mon, 15 Jan 2018 02:20:52 GMT): wbwangk (Mon, 15 Jan 2018 02:23:00 GMT): emmansun (Mon, 15 Jan 2018 02:25:12 GMT): baohua (Mon, 15 Jan 2018 03:58:55 GMT): baohua (Mon, 15 Jan 2018 03:59:00 GMT): crj (Tue, 16 Jan 2018 08:43:46 GMT): crj (Tue, 16 Jan 2018 08:44:58 GMT): CaryMa (Tue, 16 Jan 2018 20:59:54 GMT): liurf (Wed, 17 Jan 2018 10:03:08 GMT): james3443112 (Thu, 18 Jan 2018 06:45:57 GMT): tolerious (Thu, 18 Jan 2018 07:32:43 GMT): duwenhui (Thu, 18 Jan 2018 08:10:09 GMT): duwenhui (Thu, 18 Jan 2018 08:11:30 GMT): crj (Fri, 19 Jan 2018 09:28:53 GMT): frankz (Sat, 20 Jan 2018 12:35:35 GMT): frankz (Sat, 20 Jan 2018 13:03:39 GMT): frankz (Sat, 20 Jan 2018 13:13:35 GMT): gumoon (Sun, 21 Jan 2018 06:57:07 GMT): crj (Mon, 22 Jan 2018 02:50:45 GMT): crj (Mon, 22 Jan 2018 02:51:43 GMT): crj (Mon, 22 Jan 2018 02:52:23 GMT): crj (Mon, 22 Jan 2018 03:38:24 GMT): davisyao (Mon, 22 Jan 2018 07:28:32 GMT): crj (Mon, 22 Jan 2018 08:16:06 GMT): gxx (Mon, 22 Jan 2018 12:08:08 GMT): rogerso (Tue, 23 Jan 2018 02:41:34 GMT): pangxt (Tue, 23 Jan 2018 08:11:52 GMT): Yieazy (Wed, 24 Jan 2018 02:46:07 GMT): mumubin (Wed, 24 Jan 2018 10:41:50 GMT): mumubin (Wed, 24 Jan 2018 10:42:46 GMT): dusx (Thu, 25 Jan 2018 01:50:35 GMT): dusx (Thu, 25 Jan 2018 01:53:17 GMT): baohua (Thu, 25 Jan 2018 06:18:32 GMT): kerokhin (Fri, 26 Jan 2018 06:09:16 GMT): jack21 (Sat, 27 Jan 2018 11:37:47 GMT): nolimitkun (Sun, 28 Jan 2018 22:27:19 GMT): HarryZhu (Mon, 29 Jan 2018 00:13:43 GMT): xiaomai (Mon, 29 Jan 2018 03:48:56 GMT): xiaomai (Mon, 29 Jan 2018 03:52:37 GMT): baohua (Mon, 29 Jan 2018 04:36:54 GMT): jack21 (Mon, 29 Jan 2018 13:33:18 GMT): guoger (Mon, 29 Jan 2018 15:43:24 GMT): ShimingLiu (Tue, 30 Jan 2018 03:05:09 GMT): HarryZhu (Tue, 30 Jan 2018 05:34:33 GMT): HarryZhu (Tue, 30 Jan 2018 05:34:33 GMT): james3443112 (Tue, 30 Jan 2018 05:42:55 GMT): james3443112 (Tue, 30 Jan 2018 05:49:32 GMT): james3443112 (Tue, 30 Jan 2018 05:51:36 GMT): james3443112 (Tue, 30 Jan 2018 06:15:08 GMT): RocMax (Tue, 30 Jan 2018 23:23:47 GMT): james3443112 (Wed, 31 Jan 2018 00:39:27 GMT): Randyshu2018 (Wed, 31 Jan 2018 01:58:16 GMT): guoger (Wed, 31 Jan 2018 02:05:39 GMT): Randyshu2018 (Wed, 31 Jan 2018 02:11:27 GMT): mumubin (Wed, 31 Jan 2018 03:16:36 GMT): baohua (Wed, 31 Jan 2018 03:31:46 GMT): Norberthu (Wed, 31 Jan 2018 06:02:55 GMT): baohua (Wed, 31 Jan 2018 06:54:52 GMT): Norberthu (Wed, 31 Jan 2018 09:22:13 GMT): james3443112 (Thu, 01 Feb 2018 02:11:52 GMT): ShimingLiu (Thu, 01 Feb 2018 07:24:29 GMT): ShimingLiu (Thu, 01 Feb 2018 07:25:48 GMT): ShimingLiu (Thu, 01 Feb 2018 07:30:34 GMT): baohua (Thu, 01 Feb 2018 15:07:44 GMT): screeners410 (Thu, 01 Feb 2018 15:47:10 GMT): ShimingLiu (Fri, 02 Feb 2018 01:39:09 GMT): ShimingLiu (Fri, 02 Feb 2018 01:40:33 GMT): ShimingLiu (Fri, 02 Feb 2018 01:44:40 GMT): james3443112 (Fri, 02 Feb 2018 02:07:18 GMT): james3443112 (Fri, 02 Feb 2018 02:09:03 GMT): wbwangk (Fri, 02 Feb 2018 06:44:14 GMT): vchengsong (Fri, 02 Feb 2018 16:34:31 GMT): jack21 (Sat, 03 Feb 2018 13:40:29 GMT): zzylmt (Mon, 05 Feb 2018 02:18:10 GMT): Randyshu2018 (Mon, 05 Feb 2018 03:01:26 GMT): labcoinpoc (Mon, 05 Feb 2018 04:26:15 GMT): Randyshu2018 (Mon, 05 Feb 2018 06:05:11 GMT): james3443112 (Mon, 05 Feb 2018 06:16:44 GMT): labcoinpoc (Mon, 05 Feb 2018 06:20:22 GMT): james3443112 (Mon, 05 Feb 2018 06:21:12 GMT): james3443112 (Mon, 05 Feb 2018 06:21:50 GMT): james3443112 (Mon, 05 Feb 2018 06:22:01 GMT): labcoinpoc (Mon, 05 Feb 2018 06:25:06 GMT): james3443112 (Mon, 05 Feb 2018 06:26:11 GMT): james3443112 (Mon, 05 Feb 2018 06:26:32 GMT): labcoinpoc (Mon, 05 Feb 2018 06:26:59 GMT): james3443112 (Mon, 05 Feb 2018 06:27:29 GMT): james3443112 (Mon, 05 Feb 2018 06:27:39 GMT): labcoinpoc (Mon, 05 Feb 2018 06:28:12 GMT): james3443112 (Mon, 05 Feb 2018 06:30:15 GMT): james3443112 (Mon, 05 Feb 2018 06:30:30 GMT): james3443112 (Mon, 05 Feb 2018 06:30:52 GMT): labcoinpoc (Mon, 05 Feb 2018 06:31:25 GMT): labcoinpoc (Mon, 05 Feb 2018 06:32:22 GMT): james3443112 (Mon, 05 Feb 2018 06:34:09 GMT): james3443112 (Mon, 05 Feb 2018 06:39:18 GMT): james3443112 (Mon, 05 Feb 2018 06:39:32 GMT): james3443112 (Mon, 05 Feb 2018 06:39:47 GMT): labcoinpoc (Mon, 05 Feb 2018 06:51:49 GMT): james3443112 (Mon, 05 Feb 2018 06:54:01 GMT): james3443112 (Mon, 05 Feb 2018 06:54:37 GMT): nauqnew (Mon, 05 Feb 2018 07:06:59 GMT): james3443112 (Mon, 05 Feb 2018 07:13:24 GMT): james3443112 (Mon, 05 Feb 2018 13:47:48 GMT): james3443112 (Mon, 05 Feb 2018 14:04:39 GMT): qcy (Mon, 05 Feb 2018 17:57:00 GMT): qcy (Mon, 05 Feb 2018 18:16:33 GMT): JiuZhuYou (Tue, 06 Feb 2018 01:22:37 GMT): baohua (Tue, 06 Feb 2018 01:23:30 GMT): henryhs (Tue, 06 Feb 2018 01:23:30 GMT): qcy (Tue, 06 Feb 2018 01:35:57 GMT): baohua (Tue, 06 Feb 2018 01:40:36 GMT): Delon (Tue, 06 Feb 2018 07:26:34 GMT): Hengming (Tue, 06 Feb 2018 14:08:27 GMT): vchengsong (Wed, 07 Feb 2018 06:41:53 GMT): vchengsong (Wed, 07 Feb 2018 06:42:20 GMT): minibear126 (Wed, 07 Feb 2018 09:15:37 GMT): menglj (Thu, 08 Feb 2018 01:47:49 GMT): manxiaqu (Thu, 08 Feb 2018 07:10:00 GMT): Pterpan (Thu, 08 Feb 2018 08:19:10 GMT): Hengming (Thu, 08 Feb 2018 10:09:54 GMT): vchengsong (Fri, 09 Feb 2018 05:17:14 GMT): hanton (Fri, 09 Feb 2018 12:50:06 GMT): nycycr (Sat, 10 Feb 2018 06:25:29 GMT): Pitt (Mon, 12 Feb 2018 02:46:34 GMT): xiaoyao 1 (Tue, 13 Feb 2018 06:09:10 GMT): lingtony (Tue, 13 Feb 2018 08:00:04 GMT): baohua (Wed, 14 Feb 2018 08:32:15 GMT): qcy (Wed, 14 Feb 2018 08:33:51 GMT): DongkyuPark98 (Wed, 14 Feb 2018 21:01:07 GMT): Phenix.Zhang (Thu, 22 Feb 2018 04:57:34 GMT): Hengming (Fri, 23 Feb 2018 07:20:27 GMT): Hengming (Fri, 23 Feb 2018 07:20:58 GMT): Hengming (Fri, 23 Feb 2018 07:21:38 GMT): PDLTNetwork (Sat, 24 Feb 2018 07:44:21 GMT): PDLTNetwork (Sat, 24 Feb 2018 07:47:17 GMT): lingtony (Sat, 24 Feb 2018 14:17:45 GMT): baohua (Sun, 25 Feb 2018 01:50:12 GMT): labcoinpoc (Mon, 26 Feb 2018 00:58:45 GMT): labcoinpoc (Mon, 26 Feb 2018 00:58:45 GMT): labcoinpoc (Mon, 26 Feb 2018 00:58:45 GMT): bittom (Mon, 26 Feb 2018 03:23:47 GMT): ZheliangLiu (Mon, 26 Feb 2018 03:46:02 GMT): baohua (Mon, 26 Feb 2018 03:57:02 GMT): ZheliangLiu (Mon, 26 Feb 2018 04:09:50 GMT): jack21 (Mon, 26 Feb 2018 07:45:31 GMT): jack21 (Mon, 26 Feb 2018 07:47:07 GMT): jack21 (Mon, 26 Feb 2018 07:48:04 GMT): jack21 (Mon, 26 Feb 2018 07:51:14 GMT): MCC (Mon, 26 Feb 2018 09:12:21 GMT): MCC (Mon, 26 Feb 2018 09:12:52 GMT): Foen1x (Mon, 26 Feb 2018 15:59:25 GMT): baohua (Tue, 27 Feb 2018 01:01:40 GMT): baohua (Tue, 27 Feb 2018 01:36:22 GMT): zhouskun (Tue, 27 Feb 2018 02:33:31 GMT): Foen1x (Tue, 27 Feb 2018 08:28:49 GMT): nauqnew (Tue, 27 Feb 2018 10:27:04 GMT): nauqnew (Tue, 27 Feb 2018 10:33:59 GMT): Foen1x (Tue, 27 Feb 2018 10:51:37 GMT): zyc (Wed, 28 Feb 2018 01:34:34 GMT): baohua (Wed, 28 Feb 2018 02:00:59 GMT): Demon (Wed, 28 Feb 2018 04:25:55 GMT): Vincent (Wed, 28 Feb 2018 06:21:50 GMT): alacrity (Wed, 28 Feb 2018 07:08:32 GMT): Vincent (Wed, 28 Feb 2018 07:18:37 GMT): george19120 (Thu, 01 Mar 2018 13:14:15 GMT): lingtony (Thu, 01 Mar 2018 14:52:40 GMT): FeiCheng (Fri, 02 Mar 2018 01:35:12 GMT): streetpoet (Sat, 03 Mar 2018 15:11:56 GMT): vnobo (Tue, 06 Mar 2018 04:09:11 GMT): vnobo (Tue, 06 Mar 2018 04:09:32 GMT): ShimingLiu (Tue, 06 Mar 2018 07:56:42 GMT): Norberthu (Tue, 06 Mar 2018 09:42:34 GMT): Demon (Wed, 07 Mar 2018 02:04:02 GMT): sam-carmichael (Wed, 07 Mar 2018 06:06:05 GMT): fanjianhang (Thu, 08 Mar 2018 07:50:00 GMT): fanjianhang (Thu, 08 Mar 2018 07:50:57 GMT): baohua (Thu, 08 Mar 2018 13:42:36 GMT): no02 (Thu, 08 Mar 2018 15:51:15 GMT): no02 (Thu, 08 Mar 2018 15:52:38 GMT): zhangguiping (Fri, 09 Mar 2018 01:50:22 GMT): baohua (Fri, 09 Mar 2018 02:48:00 GMT): zhangyueru (Fri, 09 Mar 2018 08:21:29 GMT): zhangyueru (Fri, 09 Mar 2018 08:21:49 GMT): george19120 (Sun, 11 Mar 2018 04:19:09 GMT): george19120 (Sun, 11 Mar 2018 04:19:50 GMT): george19120 (Sun, 11 Mar 2018 04:21:12 GMT): nolimitkun (Sun, 11 Mar 2018 11:31:46 GMT): gxx (Mon, 12 Mar 2018 02:27:00 GMT): yinzhiwu (Mon, 12 Mar 2018 07:41:21 GMT): yinzhiwu (Mon, 12 Mar 2018 07:42:48 GMT): yinzhiwu (Mon, 12 Mar 2018 07:42:48 GMT): yinzhiwu (Mon, 12 Mar 2018 07:43:27 GMT): yuseven (Mon, 12 Mar 2018 07:51:32 GMT): baohua (Mon, 12 Mar 2018 07:55:18 GMT): baohua (Mon, 12 Mar 2018 07:55:39 GMT): yinzhiwu (Mon, 12 Mar 2018 08:22:27 GMT): Wind2esg (Mon, 12 Mar 2018 10:37:29 GMT): george19120 (Mon, 12 Mar 2018 11:02:51 GMT): yinzhiwu (Mon, 12 Mar 2018 14:21:32 GMT): yinzhiwu (Mon, 12 Mar 2018 14:22:07 GMT): yinzhiwu (Mon, 12 Mar 2018 14:22:41 GMT): baohua (Mon, 12 Mar 2018 14:23:45 GMT): yinzhiwu (Mon, 12 Mar 2018 14:27:16 GMT): yinzhiwu (Mon, 12 Mar 2018 14:27:59 GMT): yinzhiwu (Mon, 12 Mar 2018 14:28:56 GMT): yinzhiwu (Mon, 12 Mar 2018 14:30:28 GMT): yinzhiwu (Mon, 12 Mar 2018 14:32:15 GMT): baohua (Mon, 12 Mar 2018 14:43:27 GMT): baohua (Mon, 12 Mar 2018 14:44:14 GMT): yinzhiwu (Mon, 12 Mar 2018 14:59:41 GMT): rjones (Mon, 12 Mar 2018 16:14:10 GMT): baohua (Tue, 13 Mar 2018 01:34:38 GMT): baohua (Tue, 13 Mar 2018 01:36:53 GMT): yinzhiwu (Tue, 13 Mar 2018 02:46:08 GMT): yinzhiwu (Tue, 13 Mar 2018 02:47:08 GMT): yinzhiwu (Tue, 13 Mar 2018 02:52:34 GMT): yinzhiwu (Tue, 13 Mar 2018 03:16:05 GMT): baohua (Tue, 13 Mar 2018 04:22:56 GMT): baohua (Tue, 13 Mar 2018 04:23:50 GMT): yinzhiwu (Tue, 13 Mar 2018 06:31:37 GMT): yinzhiwu (Tue, 13 Mar 2018 06:46:06 GMT): ly774347894 (Tue, 13 Mar 2018 12:45:09 GMT): baohua (Wed, 14 Mar 2018 01:56:56 GMT): baohua (Wed, 14 Mar 2018 02:23:09 GMT): gxx0720 (Wed, 14 Mar 2018 02:44:42 GMT): Norberthu (Wed, 14 Mar 2018 02:46:13 GMT): baohua (Wed, 14 Mar 2018 02:46:54 GMT): Norberthu (Wed, 14 Mar 2018 02:47:12 GMT): baohua (Wed, 14 Mar 2018 03:23:23 GMT): Norberthu (Wed, 14 Mar 2018 03:34:35 GMT): jamesgorden (Wed, 14 Mar 2018 09:25:11 GMT): MatrixMuto (Wed, 14 Mar 2018 16:37:37 GMT): baohua (Thu, 15 Mar 2018 01:56:42 GMT): baohua (Thu, 15 Mar 2018 01:56:42 GMT): baohua (Thu, 15 Mar 2018 01:56:42 GMT): baohua (Thu, 15 Mar 2018 02:11:13 GMT): vchengsong (Thu, 15 Mar 2018 03:05:17 GMT): tigerluhu1 (Thu, 15 Mar 2018 04:00:17 GMT): siyuyifang (Thu, 15 Mar 2018 09:54:55 GMT): george19120 (Thu, 15 Mar 2018 13:50:25 GMT): george19120 (Thu, 15 Mar 2018 13:56:09 GMT): labcoinpoc (Fri, 16 Mar 2018 06:32:53 GMT): TigerXu (Fri, 16 Mar 2018 09:28:42 GMT): yinzhiwu (Fri, 16 Mar 2018 09:38:33 GMT): yinzhiwu (Fri, 16 Mar 2018 09:38:33 GMT): yinzhiwu (Fri, 16 Mar 2018 09:38:38 GMT): siyuyifang (Fri, 16 Mar 2018 09:53:45 GMT): siyuyifang (Fri, 16 Mar 2018 09:53:56 GMT): CaryMa (Sun, 18 Mar 2018 03:44:07 GMT): george19120 (Sun, 18 Mar 2018 08:17:15 GMT): george19120 (Sun, 18 Mar 2018 08:25:37 GMT): doubleeight (Sun, 18 Mar 2018 08:39:42 GMT): siyuyifang (Mon, 19 Mar 2018 01:28:44 GMT): baohua (Mon, 19 Mar 2018 01:32:50 GMT): baohua (Mon, 19 Mar 2018 01:33:35 GMT): shiyj93 (Mon, 19 Mar 2018 08:59:13 GMT): sunlead910 (Tue, 20 Mar 2018 03:03:02 GMT): ck0316 (Tue, 20 Mar 2018 03:36:13 GMT): ymk (Tue, 20 Mar 2018 09:02:21 GMT): ShikarSharma (Tue, 20 Mar 2018 22:56:38 GMT): zhuquanbin (Wed, 21 Mar 2018 07:34:41 GMT): zhuquanbin (Wed, 21 Mar 2018 07:47:29 GMT): qb (Wed, 21 Mar 2018 09:54:44 GMT): songyuanjie (Wed, 21 Mar 2018 09:57:36 GMT): songyuanjie (Wed, 21 Mar 2018 10:09:26 GMT): bxo (Wed, 21 Mar 2018 10:11:38 GMT): jack21 (Wed, 21 Mar 2018 14:21:16 GMT): jack21 (Wed, 21 Mar 2018 14:21:32 GMT): jack21 (Wed, 21 Mar 2018 14:21:57 GMT): jack21 (Wed, 21 Mar 2018 14:24:32 GMT): jack21 (Wed, 21 Mar 2018 14:25:43 GMT): jack21 (Wed, 21 Mar 2018 14:25:44 GMT): jchenibm (Thu, 22 Mar 2018 03:55:02 GMT): jchenibm (Thu, 22 Mar 2018 03:55:04 GMT): xiangyue (Thu, 22 Mar 2018 06:36:34 GMT): zmgzt (Thu, 22 Mar 2018 09:38:36 GMT): Hangyu (Fri, 23 Mar 2018 01:28:52 GMT): songyuanjie (Fri, 23 Mar 2018 01:31:43 GMT): Hangyu (Fri, 23 Mar 2018 01:33:10 GMT): songyuanjie (Fri, 23 Mar 2018 01:37:36 GMT): Hangyu (Fri, 23 Mar 2018 01:39:52 GMT): songyuanjie (Fri, 23 Mar 2018 01:41:29 GMT): Hangyu (Fri, 23 Mar 2018 01:47:56 GMT): songyuanjie (Fri, 23 Mar 2018 01:52:14 GMT): Hangyu (Fri, 23 Mar 2018 01:52:45 GMT): songyuanjie (Fri, 23 Mar 2018 01:54:01 GMT): songyuanjie (Fri, 23 Mar 2018 02:05:18 GMT): songyuanjie (Fri, 23 Mar 2018 02:05:18 GMT): yinzhiwu (Fri, 23 Mar 2018 02:38:41 GMT): songyuanjie (Fri, 23 Mar 2018 02:39:46 GMT): yinzhiwu (Fri, 23 Mar 2018 03:04:45 GMT): CarlXK (Fri, 23 Mar 2018 07:10:32 GMT): CarlXK (Fri, 23 Mar 2018 07:25:29 GMT): jchenibm (Fri, 23 Mar 2018 08:14:57 GMT): jchenibm (Fri, 23 Mar 2018 08:16:21 GMT): songyuanjie (Fri, 23 Mar 2018 08:20:06 GMT): baohua (Fri, 23 Mar 2018 10:56:03 GMT): zzx02 (Sat, 24 Mar 2018 04:09:12 GMT): yuanlv (Sun, 25 Mar 2018 06:11:30 GMT): yuanlv (Sun, 25 Mar 2018 06:12:41 GMT): wghwyn (Sun, 25 Mar 2018 13:53:57 GMT): CarlXK (Mon, 26 Mar 2018 02:14:13 GMT): CarlXK (Mon, 26 Mar 2018 02:15:27 GMT): CarlXK (Mon, 26 Mar 2018 02:20:49 GMT): xiangyue (Mon, 26 Mar 2018 02:49:00 GMT): baohua (Mon, 26 Mar 2018 02:54:33 GMT): baohua (Mon, 26 Mar 2018 02:55:23 GMT): baohua (Mon, 26 Mar 2018 02:55:24 GMT): CarlXK (Mon, 26 Mar 2018 02:56:12 GMT): xiangyue (Mon, 26 Mar 2018 03:39:09 GMT): CarlXK (Mon, 26 Mar 2018 07:00:23 GMT): jack21 (Mon, 26 Mar 2018 07:02:36 GMT): jack21 (Mon, 26 Mar 2018 07:02:56 GMT): Tuoba (Mon, 26 Mar 2018 19:39:29 GMT): mrFranklin (Tue, 27 Mar 2018 01:03:37 GMT): baohua (Tue, 27 Mar 2018 01:32:48 GMT): zhuxubin01 (Tue, 27 Mar 2018 03:54:06 GMT): mrFranklin (Tue, 27 Mar 2018 04:58:53 GMT): baohua (Wed, 28 Mar 2018 01:57:42 GMT): baohua (Wed, 28 Mar 2018 01:57:51 GMT): Zhitao (Thu, 29 Mar 2018 08:29:40 GMT): davidhu (Thu, 29 Mar 2018 10:13:57 GMT): davidhu (Thu, 29 Mar 2018 10:16:25 GMT): richzhao (Thu, 29 Mar 2018 16:20:43 GMT): richzhao (Thu, 29 Mar 2018 16:38:20 GMT): richzhao (Thu, 29 Mar 2018 16:48:59 GMT): Yi (Fri, 30 Mar 2018 02:40:46 GMT): CarlXK (Fri, 30 Mar 2018 02:45:51 GMT): davidhu (Fri, 30 Mar 2018 10:01:08 GMT): davidhu (Sat, 31 Mar 2018 12:16:32 GMT): yuanlv (Sun, 01 Apr 2018 09:50:50 GMT): labcoinpoc (Mon, 02 Apr 2018 00:38:43 GMT): peihongbin (Mon, 02 Apr 2018 02:26:02 GMT): baohua (Tue, 03 Apr 2018 00:19:24 GMT): richzhao (Tue, 03 Apr 2018 03:14:21 GMT): richzhao (Tue, 03 Apr 2018 03:16:01 GMT): baohua (Tue, 03 Apr 2018 03:18:24 GMT): richzhao (Tue, 03 Apr 2018 04:33:02 GMT): baohua (Tue, 03 Apr 2018 04:40:43 GMT): richzhao (Tue, 03 Apr 2018 04:53:01 GMT): baohua (Tue, 03 Apr 2018 04:56:27 GMT): richzhao (Tue, 03 Apr 2018 04:58:31 GMT): baohua (Tue, 03 Apr 2018 04:59:46 GMT): richzhao (Tue, 03 Apr 2018 05:01:38 GMT): richzhao (Tue, 03 Apr 2018 05:04:21 GMT): baohua (Tue, 03 Apr 2018 05:08:17 GMT): baohua (Tue, 03 Apr 2018 05:09:45 GMT): baohua (Tue, 03 Apr 2018 05:10:19 GMT): richzhao (Tue, 03 Apr 2018 05:21:16 GMT): david636 (Wed, 04 Apr 2018 00:39:08 GMT): dockeryounger (Sun, 08 Apr 2018 03:03:59 GMT): liutuol (Sun, 08 Apr 2018 07:05:22 GMT): liutuol (Sun, 08 Apr 2018 07:09:25 GMT): qingsongGuo (Sun, 08 Apr 2018 08:08:36 GMT): qingsongGuo (Sun, 08 Apr 2018 08:08:41 GMT): qingsongGuo (Sun, 08 Apr 2018 08:09:52 GMT): javascrack (Mon, 09 Apr 2018 12:24:44 GMT): javascrack (Mon, 09 Apr 2018 12:25:04 GMT): javascrack (Mon, 09 Apr 2018 12:27:29 GMT): javascrack (Mon, 09 Apr 2018 12:27:34 GMT): baohua (Mon, 09 Apr 2018 13:07:33 GMT): baohua (Mon, 09 Apr 2018 13:07:33 GMT): baohua (Mon, 09 Apr 2018 13:10:39 GMT): baohua (Mon, 09 Apr 2018 13:16:05 GMT): baohua (Tue, 10 Apr 2018 01:21:39 GMT): javascrack (Tue, 10 Apr 2018 01:22:45 GMT): xixuejia (Tue, 10 Apr 2018 02:58:16 GMT): zhenbing (Tue, 10 Apr 2018 09:00:17 GMT): zhenbing (Tue, 10 Apr 2018 09:01:31 GMT): solmichaelk (Tue, 10 Apr 2018 15:24:03 GMT): baohua (Wed, 11 Apr 2018 01:57:46 GMT): baohua (Wed, 11 Apr 2018 02:06:36 GMT): baohua (Wed, 11 Apr 2018 02:53:09 GMT): Yi (Wed, 11 Apr 2018 03:50:15 GMT): baohua (Wed, 11 Apr 2018 04:58:14 GMT): Yi (Wed, 11 Apr 2018 05:39:03 GMT): bailang71 (Wed, 11 Apr 2018 06:59:01 GMT): yuqian0218 (Thu, 12 Apr 2018 02:26:58 GMT): yuqian0218 (Thu, 12 Apr 2018 03:40:34 GMT): labcoinpoc (Thu, 12 Apr 2018 04:24:01 GMT): yuqian0218 (Thu, 12 Apr 2018 04:54:15 GMT): baohua (Fri, 13 Apr 2018 03:25:50 GMT): baohua (Fri, 13 Apr 2018 03:25:54 GMT): LinfengLiang (Fri, 13 Apr 2018 04:58:01 GMT): LinfengLiang (Fri, 13 Apr 2018 07:49:41 GMT): LinfengLiang (Fri, 13 Apr 2018 07:50:05 GMT): LinfengLiang (Fri, 13 Apr 2018 07:50:13 GMT): LinfengLiang (Fri, 13 Apr 2018 07:50:19 GMT): baohua (Fri, 13 Apr 2018 07:51:46 GMT): LinfengLiang (Fri, 13 Apr 2018 07:53:54 GMT): LinfengLiang (Fri, 13 Apr 2018 08:07:35 GMT): LinfengLiang (Fri, 13 Apr 2018 08:09:43 GMT): baohua (Fri, 13 Apr 2018 08:13:42 GMT): LinfengLiang (Fri, 13 Apr 2018 08:16:21 GMT): LinfengLiang (Fri, 13 Apr 2018 08:26:08 GMT): LinfengLiang (Fri, 13 Apr 2018 08:26:08 GMT): LinfengLiang (Fri, 13 Apr 2018 08:26:08 GMT): baohua (Fri, 13 Apr 2018 09:11:42 GMT): LinfengLiang (Fri, 13 Apr 2018 09:15:26 GMT): treesong (Tue, 17 Apr 2018 04:48:03 GMT): KevinBai (Tue, 17 Apr 2018 06:20:41 GMT): YorkYu (Wed, 18 Apr 2018 04:10:22 GMT): baohua (Thu, 19 Apr 2018 07:24:14 GMT): james3443112 (Fri, 20 Apr 2018 12:48:07 GMT): james3443112 (Fri, 20 Apr 2018 13:15:46 GMT): james3443112 (Fri, 20 Apr 2018 13:19:17 GMT): james3443112 (Fri, 20 Apr 2018 13:19:39 GMT): james3443112 (Fri, 20 Apr 2018 13:55:45 GMT): giggle (Sat, 21 Apr 2018 01:53:32 GMT): giggle (Sat, 21 Apr 2018 03:13:30 GMT): giggle (Sat, 21 Apr 2018 03:13:36 GMT): giggle (Sat, 21 Apr 2018 03:14:17 GMT): giggle (Sat, 21 Apr 2018 03:14:40 GMT): giggle (Sat, 21 Apr 2018 04:28:19 GMT): panzheng (Sat, 21 Apr 2018 09:23:59 GMT): baohua (Mon, 23 Apr 2018 04:33:40 GMT): baohua (Mon, 23 Apr 2018 04:33:51 GMT): chenxl (Mon, 23 Apr 2018 05:20:16 GMT): KevinBai (Mon, 23 Apr 2018 08:04:53 GMT): giggle (Mon, 23 Apr 2018 08:08:28 GMT): chenxl (Mon, 23 Apr 2018 08:55:50 GMT): baohua (Mon, 23 Apr 2018 09:21:33 GMT): chenxl (Mon, 23 Apr 2018 09:36:49 GMT): rickr (Mon, 23 Apr 2018 11:23:25 GMT): baohua (Mon, 23 Apr 2018 11:39:46 GMT): baohua (Mon, 23 Apr 2018 11:39:47 GMT): YorkYu (Mon, 23 Apr 2018 13:06:29 GMT): baohua (Tue, 24 Apr 2018 00:46:07 GMT): songyuanjie (Wed, 25 Apr 2018 00:55:02 GMT): james3443112 (Wed, 25 Apr 2018 05:59:18 GMT): Yieazy (Wed, 25 Apr 2018 06:22:31 GMT): IVictorFeng (Thu, 26 Apr 2018 02:32:27 GMT): guolidong (Thu, 26 Apr 2018 13:22:15 GMT): guolidong (Fri, 27 Apr 2018 07:50:13 GMT): xiaozhongqing (Fri, 27 Apr 2018 08:49:41 GMT): baohua (Fri, 27 Apr 2018 14:10:34 GMT): guolidong (Sat, 28 Apr 2018 03:14:56 GMT): guolidong (Sat, 28 Apr 2018 03:21:15 GMT): SunnyBeanLove (Wed, 02 May 2018 07:19:28 GMT): SunnyBeanLove (Wed, 02 May 2018 07:19:45 GMT): KevinBai (Wed, 02 May 2018 10:45:59 GMT): guolidong (Wed, 02 May 2018 11:30:20 GMT): guolidong (Wed, 02 May 2018 11:35:29 GMT): guolidong (Wed, 02 May 2018 12:07:21 GMT): guolidong (Wed, 02 May 2018 12:12:04 GMT): james3443112 (Thu, 03 May 2018 02:16:27 GMT): james3443112 (Thu, 03 May 2018 06:27:44 GMT): songyuanjie (Fri, 04 May 2018 02:15:01 GMT): KevinBai (Fri, 04 May 2018 07:33:15 GMT): guolidong (Fri, 04 May 2018 08:04:46 GMT): KevinBai (Fri, 04 May 2018 08:06:17 GMT): guolidong (Fri, 04 May 2018 08:08:13 GMT): KevinBai (Fri, 04 May 2018 08:09:12 GMT): ArkiZh (Mon, 07 May 2018 12:59:44 GMT): ArkiZh (Mon, 07 May 2018 13:12:32 GMT): baohua (Mon, 07 May 2018 13:36:04 GMT): baohua (Tue, 08 May 2018 02:16:42 GMT): richzhao (Tue, 08 May 2018 02:28:17 GMT): zhouzhengji (Tue, 08 May 2018 13:29:56 GMT): zhouzhengji (Tue, 08 May 2018 13:40:29 GMT): baohua (Wed, 09 May 2018 00:08:29 GMT): panzheng (Wed, 09 May 2018 01:15:42 GMT): panzheng (Wed, 09 May 2018 01:35:46 GMT): baohua (Wed, 09 May 2018 01:57:55 GMT): baohua (Wed, 09 May 2018 01:58:28 GMT): baohua (Wed, 09 May 2018 01:59:35 GMT): panzheng (Wed, 09 May 2018 01:59:39 GMT): KevinBai (Wed, 09 May 2018 02:28:21 GMT): KevinBai (Wed, 09 May 2018 02:29:09 GMT): baohua (Wed, 09 May 2018 04:22:12 GMT): xinfancn1981 (Thu, 10 May 2018 02:20:59 GMT): guolidong (Thu, 10 May 2018 13:40:54 GMT): guolidong (Thu, 10 May 2018 13:40:54 GMT): guolidong (Thu, 10 May 2018 13:42:36 GMT): guolidong (Thu, 10 May 2018 13:45:15 GMT): zhuquanbin (Fri, 11 May 2018 02:55:58 GMT): baohua (Fri, 11 May 2018 07:38:05 GMT): crj (Fri, 11 May 2018 08:39:16 GMT): crj (Fri, 11 May 2018 08:40:12 GMT): james3443112 (Fri, 11 May 2018 09:11:00 GMT): zhenbing (Fri, 11 May 2018 10:15:21 GMT): feuvan (Mon, 14 May 2018 06:01:00 GMT): zlliu (Mon, 14 May 2018 10:02:23 GMT): zlliu (Mon, 14 May 2018 10:02:23 GMT): zlliu (Mon, 14 May 2018 10:02:23 GMT): zhouzhengji (Mon, 14 May 2018 12:40:59 GMT): zhouzhengji (Mon, 14 May 2018 12:41:19 GMT): zhouzhengji (Mon, 14 May 2018 12:42:46 GMT): zhouzhengji (Mon, 14 May 2018 12:43:33 GMT): xinfancn1981 (Tue, 15 May 2018 02:22:22 GMT): baohua (Tue, 15 May 2018 03:39:52 GMT): baohua (Tue, 15 May 2018 03:40:54 GMT): xinfancn1981 (Tue, 15 May 2018 03:54:40 GMT): KevinBai (Thu, 17 May 2018 09:17:27 GMT): KevinBai (Thu, 17 May 2018 09:19:08 GMT): KevinBai (Thu, 17 May 2018 09:19:35 GMT): chenshiok (Fri, 18 May 2018 02:47:29 GMT): xiaocorn (Fri, 18 May 2018 02:53:53 GMT): KevinBai (Fri, 18 May 2018 04:08:23 GMT): baohua (Fri, 18 May 2018 09:07:31 GMT): baohua (Fri, 18 May 2018 09:08:36 GMT): labcoinpoc (Fri, 18 May 2018 09:30:07 GMT): baoyangc (Mon, 21 May 2018 02:08:29 GMT): baoyangc (Mon, 21 May 2018 02:17:09 GMT): KevinBai (Mon, 21 May 2018 08:05:54 GMT): baohua (Tue, 22 May 2018 01:31:51 GMT): peter.li (Tue, 22 May 2018 08:08:03 GMT): baohua (Tue, 22 May 2018 08:39:23 GMT): peter.li (Tue, 22 May 2018 09:23:30 GMT): peter.li (Tue, 22 May 2018 09:23:44 GMT): baohua (Tue, 22 May 2018 09:30:52 GMT): baohua (Tue, 22 May 2018 09:30:52 GMT): peter.li (Tue, 22 May 2018 09:31:47 GMT): baohua (Wed, 23 May 2018 00:12:30 GMT): peter.li (Wed, 23 May 2018 00:42:33 GMT): baohua (Wed, 23 May 2018 00:50:48 GMT): peter.li (Wed, 23 May 2018 00:53:47 GMT): baohua (Wed, 23 May 2018 00:56:08 GMT): peter.li (Wed, 23 May 2018 00:58:37 GMT): baohua (Wed, 23 May 2018 00:59:54 GMT): peter.li (Wed, 23 May 2018 01:07:49 GMT): baohua (Wed, 23 May 2018 01:51:14 GMT): ping40 (Wed, 23 May 2018 13:19:29 GMT): zhangyouxi (Thu, 24 May 2018 01:49:12 GMT): zhangyouxi (Thu, 24 May 2018 01:49:48 GMT): KevinBai (Thu, 24 May 2018 02:52:44 GMT): huangliping (Fri, 25 May 2018 05:43:16 GMT): HuangCarl (Fri, 25 May 2018 05:52:57 GMT): huangliping (Fri, 25 May 2018 07:41:49 GMT): HandsomeRoger (Fri, 25 May 2018 08:36:53 GMT): smallX (Mon, 28 May 2018 04:12:46 GMT): MFLion (Tue, 29 May 2018 00:09:35 GMT): jgm-learn (Wed, 30 May 2018 01:44:44 GMT): yljgo (Wed, 30 May 2018 03:18:13 GMT): baoyangc (Thu, 31 May 2018 01:41:29 GMT): yljgo (Thu, 31 May 2018 07:32:26 GMT): yljgo (Thu, 31 May 2018 07:32:43 GMT): Alex0 (Thu, 31 May 2018 10:10:07 GMT): songyuanjie (Fri, 01 Jun 2018 06:13:23 GMT): yangjian212423 (Fri, 01 Jun 2018 07:35:17 GMT): demonkm (Sun, 03 Jun 2018 02:30:59 GMT): Gaoqi (Mon, 04 Jun 2018 21:51:43 GMT): baohua (Tue, 05 Jun 2018 01:13:46 GMT): yangjian212423 (Tue, 05 Jun 2018 02:00:34 GMT): baohua (Wed, 06 Jun 2018 09:17:44 GMT): abraham (Wed, 06 Jun 2018 15:39:27 GMT): muuzisoft (Thu, 07 Jun 2018 01:55:19 GMT): muuzisoft (Thu, 07 Jun 2018 01:55:50 GMT): baohua (Thu, 07 Jun 2018 08:13:53 GMT): longac (Thu, 07 Jun 2018 13:55:04 GMT): muuzisoft (Fri, 08 Jun 2018 02:33:30 GMT): wangrangli (Fri, 08 Jun 2018 05:36:06 GMT): CarlXK (Sun, 10 Jun 2018 05:08:05 GMT): xxg4813 (Mon, 11 Jun 2018 02:20:46 GMT): RealDeanZhao (Mon, 11 Jun 2018 08:21:34 GMT): RealDeanZhao (Mon, 11 Jun 2018 08:22:56 GMT): RealDeanZhao (Mon, 11 Jun 2018 08:23:01 GMT): RealDeanZhao (Mon, 11 Jun 2018 08:23:06 GMT): RealDeanZhao (Mon, 11 Jun 2018 08:24:41 GMT): RealDeanZhao (Mon, 11 Jun 2018 12:43:49 GMT): RealDeanZhao (Mon, 11 Jun 2018 12:44:01 GMT): baohua (Wed, 13 Jun 2018 01:52:52 GMT): davidkhala (Wed, 13 Jun 2018 04:59:46 GMT): RealDeanZhao (Wed, 13 Jun 2018 07:54:48 GMT): RealDeanZhao (Wed, 13 Jun 2018 07:55:26 GMT): RealDeanZhao (Wed, 13 Jun 2018 07:55:45 GMT): RealDeanZhao (Wed, 13 Jun 2018 07:55:54 GMT): RealDeanZhao (Wed, 13 Jun 2018 10:03:38 GMT): kenty (Fri, 15 Jun 2018 15:11:05 GMT): lushan6999 (Sun, 17 Jun 2018 05:03:23 GMT): baohua (Tue, 19 Jun 2018 00:14:29 GMT): abraham (Tue, 19 Jun 2018 02:31:26 GMT): abraham (Tue, 19 Jun 2018 02:32:31 GMT): baoyangc (Tue, 19 Jun 2018 06:14:54 GMT): fanbin (Tue, 19 Jun 2018 07:03:07 GMT): davidkhala (Wed, 20 Jun 2018 03:44:44 GMT): baoyangc (Wed, 20 Jun 2018 06:02:24 GMT): davidkhala (Wed, 20 Jun 2018 06:05:52 GMT): baohua (Wed, 20 Jun 2018 13:11:53 GMT): Katie_Wei (Wed, 20 Jun 2018 18:43:02 GMT): shuailaotou (Fri, 22 Jun 2018 08:08:28 GMT): shuailaotou (Fri, 22 Jun 2018 08:14:52 GMT): baohua (Fri, 22 Jun 2018 14:11:29 GMT): yyyfor (Tue, 26 Jun 2018 08:21:49 GMT): CsterKuroi (Thu, 28 Jun 2018 08:37:21 GMT): flytofly (Thu, 28 Jun 2018 08:47:49 GMT): huangliping (Fri, 29 Jun 2018 08:08:27 GMT): flytofly (Sun, 01 Jul 2018 05:40:18 GMT): davidhu (Mon, 02 Jul 2018 03:55:08 GMT): labcoinpoc (Mon, 02 Jul 2018 07:48:41 GMT): davidhu (Mon, 02 Jul 2018 09:00:53 GMT): bohaoist (Mon, 02 Jul 2018 11:08:03 GMT): baohua (Tue, 03 Jul 2018 04:07:07 GMT): ZhangMingxi (Tue, 03 Jul 2018 12:21:57 GMT): davidhu (Wed, 04 Jul 2018 02:55:03 GMT): labcoinpoc (Wed, 04 Jul 2018 04:00:28 GMT): davidhu (Wed, 04 Jul 2018 06:18:43 GMT): davidhu (Wed, 04 Jul 2018 06:21:03 GMT): labcoinpoc (Wed, 04 Jul 2018 07:42:42 GMT): davidhu (Wed, 04 Jul 2018 08:46:02 GMT): labcoinpoc (Wed, 04 Jul 2018 09:24:34 GMT): tinywell (Mon, 09 Jul 2018 03:06:16 GMT): EricYang (Mon, 09 Jul 2018 11:07:52 GMT): davidhu (Tue, 10 Jul 2018 00:43:16 GMT): labcoinpoc (Tue, 10 Jul 2018 02:08:09 GMT): baohua (Tue, 10 Jul 2018 03:08:43 GMT): huangliping (Tue, 10 Jul 2018 04:01:43 GMT): davidhu (Tue, 10 Jul 2018 06:04:51 GMT): labcoinpoc (Tue, 10 Jul 2018 06:07:46 GMT): KevinBai (Wed, 11 Jul 2018 02:06:22 GMT): yimao (Wed, 11 Jul 2018 02:26:35 GMT): baohua (Wed, 11 Jul 2018 02:38:34 GMT): KevinBai (Wed, 11 Jul 2018 02:40:01 GMT): shuailaotou (Wed, 11 Jul 2018 07:36:29 GMT): shuailaotou (Wed, 11 Jul 2018 07:36:35 GMT): shuailaotou (Wed, 11 Jul 2018 07:36:46 GMT): shuailaotou (Wed, 11 Jul 2018 08:43:59 GMT): WadeLu (Thu, 12 Jul 2018 07:35:58 GMT): uj8050 (Fri, 13 Jul 2018 11:48:17 GMT): jiulama (Sat, 14 Jul 2018 07:25:04 GMT): bluefire (Tue, 17 Jul 2018 06:26:33 GMT): memphisw (Tue, 17 Jul 2018 06:57:43 GMT): baohua (Tue, 17 Jul 2018 07:49:16 GMT): memphisw (Tue, 17 Jul 2018 08:00:59 GMT): baohua (Tue, 17 Jul 2018 13:07:27 GMT): louisliu2048 (Wed, 18 Jul 2018 02:23:04 GMT): louisliu2048 (Wed, 18 Jul 2018 02:26:11 GMT): baohua (Wed, 18 Jul 2018 04:26:11 GMT): bluefire (Wed, 18 Jul 2018 09:25:53 GMT): bluefire (Wed, 18 Jul 2018 09:26:37 GMT): memphisw (Thu, 19 Jul 2018 02:40:36 GMT): memphisw (Thu, 19 Jul 2018 02:44:30 GMT): memphisw (Thu, 19 Jul 2018 02:46:51 GMT): baohua (Thu, 19 Jul 2018 14:02:16 GMT): memphisw (Fri, 20 Jul 2018 07:19:38 GMT): tinywell (Mon, 23 Jul 2018 01:14:44 GMT): memphisw (Mon, 23 Jul 2018 05:37:34 GMT): bobzhao (Mon, 23 Jul 2018 15:29:17 GMT): davidhu (Tue, 24 Jul 2018 00:20:30 GMT): labcoinpoc (Tue, 24 Jul 2018 00:48:30 GMT): labcoinpoc (Tue, 24 Jul 2018 00:48:30 GMT): davidhu (Tue, 24 Jul 2018 00:51:52 GMT): davidhu (Tue, 24 Jul 2018 00:53:54 GMT): labcoinpoc (Tue, 24 Jul 2018 00:56:16 GMT): labcoinpoc (Tue, 24 Jul 2018 00:56:50 GMT): labcoinpoc (Tue, 24 Jul 2018 00:56:50 GMT): labcoinpoc (Tue, 24 Jul 2018 01:00:06 GMT): labcoinpoc (Tue, 24 Jul 2018 01:01:28 GMT): labcoinpoc (Tue, 24 Jul 2018 01:01:28 GMT): davidhu (Tue, 24 Jul 2018 01:02:13 GMT): davidhu (Tue, 24 Jul 2018 01:02:40 GMT): labcoinpoc (Tue, 24 Jul 2018 01:02:41 GMT): davidhu (Tue, 24 Jul 2018 01:03:06 GMT): baohua (Tue, 24 Jul 2018 02:50:48 GMT): Wilsonli (Tue, 24 Jul 2018 13:46:52 GMT): docici (Wed, 25 Jul 2018 10:26:29 GMT): wangrangli (Thu, 26 Jul 2018 02:13:40 GMT): labcoinpoc (Thu, 26 Jul 2018 02:23:06 GMT): davidhu (Thu, 26 Jul 2018 02:48:08 GMT): wangrangli (Thu, 26 Jul 2018 03:12:24 GMT): wangrangli (Thu, 26 Jul 2018 06:47:58 GMT): memphisw (Fri, 27 Jul 2018 02:28:56 GMT): hloou (Sun, 29 Jul 2018 15:54:36 GMT): davidhu (Mon, 30 Jul 2018 01:44:29 GMT): davidhu (Mon, 30 Jul 2018 08:02:53 GMT): yljgo (Tue, 31 Jul 2018 02:52:59 GMT): baohua (Tue, 31 Jul 2018 03:09:52 GMT): baohua (Tue, 31 Jul 2018 04:32:38 GMT): wangrangli (Tue, 31 Jul 2018 05:50:59 GMT): davidhu (Tue, 31 Jul 2018 07:17:42 GMT): davidhu (Tue, 31 Jul 2018 07:27:03 GMT): wangrangli (Tue, 31 Jul 2018 08:14:34 GMT): huangliping (Tue, 31 Jul 2018 09:13:43 GMT): zavier (Tue, 31 Jul 2018 13:03:22 GMT): huangliping (Wed, 01 Aug 2018 00:36:45 GMT): KevinBai (Wed, 01 Aug 2018 02:06:58 GMT): zerppen (Wed, 01 Aug 2018 03:21:03 GMT): baohua (Wed, 01 Aug 2018 04:00:17 GMT): GaoAkka (Wed, 01 Aug 2018 10:11:59 GMT): tinywell (Wed, 01 Aug 2018 10:52:08 GMT): jyellick (Wed, 01 Aug 2018 15:38:34 GMT): davidhu (Thu, 02 Aug 2018 08:47:43 GMT): davidhu (Thu, 02 Aug 2018 08:48:31 GMT): davidhu (Thu, 02 Aug 2018 08:49:15 GMT): davidhu (Thu, 02 Aug 2018 08:50:28 GMT): labcoinpoc (Thu, 02 Aug 2018 08:58:00 GMT): davidhu (Thu, 02 Aug 2018 09:04:00 GMT): davidhu (Thu, 02 Aug 2018 09:05:59 GMT): labcoinpoc (Thu, 02 Aug 2018 09:08:48 GMT): labcoinpoc (Thu, 02 Aug 2018 09:11:24 GMT): davidhu (Thu, 02 Aug 2018 09:17:20 GMT): labcoinpoc (Thu, 02 Aug 2018 09:21:31 GMT): labcoinpoc (Thu, 02 Aug 2018 09:29:38 GMT): davidhu (Thu, 02 Aug 2018 09:31:09 GMT): davidhu (Thu, 02 Aug 2018 09:31:39 GMT): wangrangli (Thu, 02 Aug 2018 11:11:33 GMT): davidhu (Fri, 03 Aug 2018 00:42:46 GMT): davidhu (Fri, 03 Aug 2018 00:42:47 GMT): labcoinpoc (Fri, 03 Aug 2018 01:21:29 GMT): davidhu (Fri, 03 Aug 2018 02:23:02 GMT): davidhu (Fri, 03 Aug 2018 03:57:26 GMT): davidhu (Fri, 03 Aug 2018 03:58:04 GMT): wangrangli (Fri, 03 Aug 2018 06:35:48 GMT): BenZhang (Fri, 03 Aug 2018 16:20:12 GMT): zerppen (Mon, 06 Aug 2018 02:58:10 GMT): wangrangli (Mon, 06 Aug 2018 05:43:05 GMT): yljgo (Mon, 06 Aug 2018 06:47:56 GMT): zerppen (Mon, 06 Aug 2018 07:46:20 GMT): yljgo (Mon, 06 Aug 2018 08:12:52 GMT): davidhu (Tue, 07 Aug 2018 00:21:24 GMT): Randyshu2018 (Tue, 07 Aug 2018 03:33:11 GMT): wangrangli (Tue, 07 Aug 2018 04:54:59 GMT): baohua (Tue, 07 Aug 2018 05:50:24 GMT): grapebaba (Wed, 08 Aug 2018 01:37:30 GMT): davidhu (Wed, 08 Aug 2018 02:43:11 GMT): yljgo (Wed, 08 Aug 2018 03:31:01 GMT): grapebaba (Wed, 08 Aug 2018 11:24:16 GMT): grapebaba (Wed, 08 Aug 2018 11:24:32 GMT): r808silva (Wed, 08 Aug 2018 15:24:50 GMT): baoyangc (Thu, 09 Aug 2018 04:57:11 GMT): zerppen (Fri, 10 Aug 2018 01:30:50 GMT): zerppen (Fri, 10 Aug 2018 07:25:57 GMT): zerppen (Fri, 10 Aug 2018 07:28:52 GMT): zerppen (Fri, 10 Aug 2018 07:29:25 GMT): zerppen (Fri, 10 Aug 2018 07:29:35 GMT): aratic (Fri, 10 Aug 2018 10:39:48 GMT): aratic (Fri, 10 Aug 2018 10:40:47 GMT): shiyj (Fri, 10 Aug 2018 11:36:03 GMT): aratic (Fri, 10 Aug 2018 12:03:49 GMT): aratic (Fri, 10 Aug 2018 12:14:40 GMT): aratic (Sat, 11 Aug 2018 06:06:00 GMT): YuanOwen (Sun, 12 Aug 2018 09:28:23 GMT): davidhu (Mon, 13 Aug 2018 01:16:34 GMT): davidhu (Mon, 13 Aug 2018 01:17:02 GMT): aratic (Mon, 13 Aug 2018 02:10:52 GMT): DinghaoLI 1 (Mon, 13 Aug 2018 03:13:22 GMT): davidhu (Wed, 15 Aug 2018 00:50:35 GMT): aratic (Wed, 15 Aug 2018 01:55:12 GMT): aratic (Wed, 15 Aug 2018 01:56:26 GMT): zerppen (Wed, 15 Aug 2018 02:32:33 GMT): aratic (Wed, 15 Aug 2018 03:07:00 GMT): ByteHero (Thu, 16 Aug 2018 04:44:42 GMT): huangliping (Fri, 17 Aug 2018 04:04:35 GMT): huangliping (Fri, 17 Aug 2018 09:09:10 GMT): huangliping (Fri, 17 Aug 2018 09:43:11 GMT): larry618 (Sun, 19 Aug 2018 07:44:07 GMT): larry618 (Sun, 19 Aug 2018 07:52:20 GMT): zerppen (Mon, 20 Aug 2018 02:49:38 GMT): memphisw (Mon, 20 Aug 2018 10:27:07 GMT): baohua (Tue, 21 Aug 2018 01:36:56 GMT): baohua (Tue, 21 Aug 2018 01:36:56 GMT): davidkhala (Tue, 21 Aug 2018 02:02:04 GMT): memphisw (Tue, 21 Aug 2018 02:07:31 GMT): davidkhala (Tue, 21 Aug 2018 03:18:33 GMT): davidkhala (Tue, 21 Aug 2018 03:20:46 GMT): OzWang (Tue, 21 Aug 2018 06:19:38 GMT): memphisw (Tue, 21 Aug 2018 06:32:03 GMT): memphisw (Tue, 21 Aug 2018 06:32:03 GMT): memphisw (Wed, 22 Aug 2018 02:02:41 GMT): zerppen (Wed, 22 Aug 2018 05:57:47 GMT): zerppen (Wed, 22 Aug 2018 05:59:00 GMT): memphisw (Wed, 22 Aug 2018 06:48:14 GMT): memphisw (Wed, 22 Aug 2018 06:48:14 GMT): zerppen (Wed, 22 Aug 2018 07:17:09 GMT): memphisw (Wed, 22 Aug 2018 07:37:39 GMT): wangrangli (Wed, 22 Aug 2018 07:38:14 GMT): memphisw (Wed, 22 Aug 2018 07:43:34 GMT): larry618 (Wed, 22 Aug 2018 12:19:40 GMT): larry618 (Wed, 22 Aug 2018 12:34:39 GMT): wangrangli (Wed, 22 Aug 2018 12:41:39 GMT): szewong (Wed, 22 Aug 2018 18:50:18 GMT): baohua (Thu, 23 Aug 2018 01:47:00 GMT): zerppen (Thu, 23 Aug 2018 03:41:14 GMT): memphisw (Thu, 23 Aug 2018 05:22:10 GMT): KevinBai (Thu, 23 Aug 2018 05:45:07 GMT): zerppen (Thu, 23 Aug 2018 05:49:17 GMT): zerppen (Thu, 23 Aug 2018 05:49:22 GMT): zerppen (Thu, 23 Aug 2018 05:50:09 GMT): OzWang (Thu, 23 Aug 2018 06:11:12 GMT): zerppen (Thu, 23 Aug 2018 07:53:21 GMT): zerppen (Thu, 23 Aug 2018 07:53:47 GMT): zerppen (Thu, 23 Aug 2018 07:55:56 GMT): wangrangli (Thu, 23 Aug 2018 13:46:26 GMT): wangrangli (Thu, 23 Aug 2018 13:48:03 GMT): memphisw (Thu, 23 Aug 2018 16:48:44 GMT): wangrangli (Thu, 23 Aug 2018 20:08:13 GMT): qiangjiyi (Tue, 28 Aug 2018 02:15:45 GMT): huangliping (Wed, 29 Aug 2018 02:20:52 GMT): kevinli (Wed, 29 Aug 2018 02:36:16 GMT): demonkm (Thu, 30 Aug 2018 08:22:14 GMT): demonkm (Thu, 30 Aug 2018 08:22:21 GMT): demonkm (Thu, 30 Aug 2018 08:23:39 GMT): demonkm (Thu, 30 Aug 2018 08:28:32 GMT): baohua (Thu, 30 Aug 2018 14:45:38 GMT): kevinli (Fri, 31 Aug 2018 00:49:33 GMT): kevinli (Fri, 31 Aug 2018 00:51:54 GMT): kevinli (Fri, 31 Aug 2018 00:58:43 GMT): baohua (Fri, 31 Aug 2018 02:07:32 GMT): baohua (Fri, 31 Aug 2018 02:08:09 GMT): houqian (Fri, 31 Aug 2018 04:18:17 GMT): kirin13 (Fri, 31 Aug 2018 06:15:17 GMT): BenZhang (Fri, 31 Aug 2018 15:32:38 GMT): BenZhang (Fri, 31 Aug 2018 15:33:07 GMT): kevinli (Sat, 01 Sep 2018 04:20:26 GMT): kevinli (Sat, 01 Sep 2018 04:21:45 GMT): BenZhang (Sat, 01 Sep 2018 15:49:40 GMT): BenZhang (Sat, 01 Sep 2018 15:50:34 GMT): wangrangli (Sun, 02 Sep 2018 16:15:18 GMT): demonkm (Tue, 04 Sep 2018 03:15:14 GMT): demonkm (Tue, 04 Sep 2018 03:16:24 GMT): kevinli (Tue, 04 Sep 2018 03:26:08 GMT): BenZhang (Tue, 04 Sep 2018 04:52:00 GMT): OzWang (Tue, 04 Sep 2018 06:53:32 GMT): xixuejia (Tue, 04 Sep 2018 11:16:03 GMT): xixuejia (Tue, 04 Sep 2018 11:16:03 GMT): xixuejia (Tue, 04 Sep 2018 11:16:15 GMT): baohua (Wed, 05 Sep 2018 01:43:09 GMT): demonkm (Wed, 05 Sep 2018 06:17:45 GMT): demonkm (Wed, 05 Sep 2018 06:18:23 GMT): demonkm (Wed, 05 Sep 2018 06:19:53 GMT): baohua (Thu, 06 Sep 2018 02:34:19 GMT): demonkm (Thu, 06 Sep 2018 03:01:18 GMT): baohua (Thu, 06 Sep 2018 03:23:31 GMT): zerppen (Thu, 06 Sep 2018 06:32:34 GMT): zerppen (Thu, 06 Sep 2018 06:32:34 GMT): zerppen (Thu, 06 Sep 2018 06:32:42 GMT): zerppen (Thu, 06 Sep 2018 06:32:42 GMT): demonkm (Thu, 06 Sep 2018 11:32:58 GMT): Pillar (Mon, 10 Sep 2018 05:52:50 GMT): Pillar (Mon, 10 Sep 2018 05:55:38 GMT): Pillar (Mon, 10 Sep 2018 05:57:24 GMT): Randyshu2018 (Mon, 10 Sep 2018 15:39:06 GMT): davidkhala (Tue, 11 Sep 2018 09:57:36 GMT): davidkhala (Tue, 11 Sep 2018 09:59:00 GMT): demonkm (Tue, 11 Sep 2018 23:00:24 GMT): BenZhang (Wed, 12 Sep 2018 01:42:28 GMT): davidkhala (Wed, 12 Sep 2018 01:58:10 GMT): baohua (Wed, 12 Sep 2018 01:58:19 GMT): davidkhala (Wed, 12 Sep 2018 01:58:36 GMT): Pillar (Wed, 12 Sep 2018 03:14:25 GMT): davidkhala (Wed, 12 Sep 2018 06:19:01 GMT): ping40 (Wed, 12 Sep 2018 14:27:57 GMT): ping40 (Wed, 12 Sep 2018 14:27:57 GMT): ping40 (Wed, 12 Sep 2018 14:29:14 GMT): ping40 (Wed, 12 Sep 2018 14:29:14 GMT): ping40 (Wed, 12 Sep 2018 14:37:49 GMT): baoyangc (Thu, 13 Sep 2018 02:16:44 GMT): Pillar (Thu, 13 Sep 2018 14:57:14 GMT): Pillar (Thu, 13 Sep 2018 14:57:19 GMT): ping40 (Fri, 14 Sep 2018 03:52:00 GMT): BenZhang (Fri, 14 Sep 2018 06:26:22 GMT): Pillar (Fri, 14 Sep 2018 08:37:51 GMT): Pillar (Fri, 14 Sep 2018 08:38:19 GMT): Pillar (Fri, 14 Sep 2018 08:39:15 GMT): Pillar (Fri, 14 Sep 2018 08:40:07 GMT): ping40 (Fri, 14 Sep 2018 13:53:41 GMT): jackyu66 (Mon, 17 Sep 2018 06:16:01 GMT): OzWang (Wed, 19 Sep 2018 07:51:50 GMT): baohua (Thu, 27 Sep 2018 08:46:26 GMT): guoger (Thu, 27 Sep 2018 08:48:39 GMT): guoger (Thu, 27 Sep 2018 09:37:50 GMT): guoger (Thu, 27 Sep 2018 09:37:50 GMT): davidkhala (Thu, 27 Sep 2018 09:47:25 GMT): Mindey (Sun, 30 Sep 2018 19:11:10 GMT): niuhw (Thu, 04 Oct 2018 03:28:28 GMT): Everymans.ai (Thu, 04 Oct 2018 17:19:42 GMT): Perebor (Sat, 06 Oct 2018 03:11:50 GMT): yljgo (Mon, 08 Oct 2018 02:47:08 GMT): ping40 (Mon, 08 Oct 2018 03:08:01 GMT): yljgo (Mon, 08 Oct 2018 03:15:53 GMT): ping40 (Mon, 08 Oct 2018 03:56:49 GMT): ping40 (Mon, 08 Oct 2018 03:57:09 GMT): yljgo (Mon, 08 Oct 2018 06:50:10 GMT): davidhu (Tue, 09 Oct 2018 01:27:21 GMT): labcoinpoc (Tue, 09 Oct 2018 01:32:37 GMT): davidhu (Tue, 09 Oct 2018 01:34:46 GMT): labcoinpoc (Tue, 09 Oct 2018 01:34:57 GMT): davidhu (Tue, 09 Oct 2018 01:35:46 GMT): labcoinpoc (Tue, 09 Oct 2018 01:37:58 GMT): labcoinpoc (Tue, 09 Oct 2018 01:41:11 GMT): labcoinpoc (Tue, 09 Oct 2018 01:41:27 GMT): labcoinpoc (Tue, 09 Oct 2018 01:41:27 GMT): davidhu (Tue, 09 Oct 2018 01:45:04 GMT): labcoinpoc (Tue, 09 Oct 2018 01:47:20 GMT): davidhu (Tue, 09 Oct 2018 01:48:59 GMT): labcoinpoc (Tue, 09 Oct 2018 01:51:31 GMT): labcoinpoc (Tue, 09 Oct 2018 01:53:24 GMT): labcoinpoc (Tue, 09 Oct 2018 01:53:44 GMT): davidhu (Tue, 09 Oct 2018 01:53:52 GMT): labcoinpoc (Tue, 09 Oct 2018 01:56:48 GMT): labcoinpoc (Tue, 09 Oct 2018 01:59:44 GMT): baohua (Tue, 09 Oct 2018 05:37:11 GMT): rcviauall (Wed, 10 Oct 2018 01:30:36 GMT): raccoonrat (Wed, 10 Oct 2018 02:52:19 GMT): dexhunter (Wed, 10 Oct 2018 06:40:09 GMT): dexhunter (Wed, 10 Oct 2018 07:02:33 GMT): davidhu (Wed, 10 Oct 2018 07:16:36 GMT): davidhu (Wed, 10 Oct 2018 07:26:09 GMT): dexhunter (Wed, 10 Oct 2018 08:30:06 GMT): davidhu (Wed, 10 Oct 2018 08:43:27 GMT): labcoinpoc (Thu, 11 Oct 2018 02:27:43 GMT): labcoinpoc (Thu, 11 Oct 2018 02:43:12 GMT): dexhunter (Thu, 11 Oct 2018 12:42:09 GMT): labcoinpoc (Fri, 12 Oct 2018 01:39:46 GMT): labcoinpoc (Fri, 12 Oct 2018 01:55:22 GMT): davidhu (Mon, 15 Oct 2018 01:36:45 GMT): wuhen (Mon, 15 Oct 2018 07:51:45 GMT): tahaf10 (Mon, 15 Oct 2018 09:44:31 GMT): davidkhala (Mon, 15 Oct 2018 10:34:33 GMT): labcoinpoc (Tue, 16 Oct 2018 02:47:47 GMT): labcoinpoc (Tue, 16 Oct 2018 02:47:47 GMT): davidkhala (Tue, 16 Oct 2018 07:29:31 GMT): labcoinpoc (Tue, 16 Oct 2018 08:01:32 GMT): labcoinpoc (Tue, 16 Oct 2018 08:01:32 GMT): labcoinpoc (Tue, 16 Oct 2018 08:10:47 GMT): davidkhala (Tue, 16 Oct 2018 08:43:53 GMT): wuhen (Wed, 17 Oct 2018 06:15:40 GMT): wuhen (Wed, 17 Oct 2018 06:17:25 GMT): dexhunter (Thu, 18 Oct 2018 06:36:06 GMT): yljgo (Thu, 18 Oct 2018 09:11:07 GMT): davidkhala (Fri, 19 Oct 2018 10:39:45 GMT): shuailaotou (Mon, 22 Oct 2018 03:48:15 GMT): shuailaotou (Mon, 22 Oct 2018 03:48:25 GMT): shuailaotou (Mon, 22 Oct 2018 03:49:41 GMT): davidkhala (Mon, 22 Oct 2018 04:00:07 GMT): richzhao (Mon, 22 Oct 2018 05:03:14 GMT): richzhao (Mon, 22 Oct 2018 05:03:28 GMT): richzhao (Mon, 22 Oct 2018 05:03:42 GMT): shuailaotou (Mon, 22 Oct 2018 07:31:56 GMT): shuailaotou (Mon, 22 Oct 2018 07:33:02 GMT): shuailaotou (Mon, 22 Oct 2018 07:33:53 GMT): shuailaotou (Tue, 23 Oct 2018 02:43:33 GMT): baohua (Tue, 23 Oct 2018 06:20:37 GMT): iamsteveng (Wed, 24 Oct 2018 09:05:47 GMT): iamsteveng (Wed, 24 Oct 2018 09:20:44 GMT): iamsteveng (Wed, 24 Oct 2018 10:27:27 GMT): baohua (Thu, 25 Oct 2018 05:48:56 GMT): iamsteveng (Thu, 25 Oct 2018 06:59:41 GMT): firechain (Thu, 25 Oct 2018 07:56:58 GMT): wangrangli (Thu, 01 Nov 2018 09:35:20 GMT): Randyshu2018 (Thu, 01 Nov 2018 14:57:53 GMT): lijiachuan (Fri, 02 Nov 2018 01:05:16 GMT): lijiachuan (Fri, 02 Nov 2018 01:26:16 GMT): lijiachuan (Fri, 02 Nov 2018 01:41:23 GMT): davidkhala (Fri, 02 Nov 2018 10:32:57 GMT): davidkhala (Fri, 02 Nov 2018 10:34:51 GMT): davidkhala (Fri, 02 Nov 2018 10:34:51 GMT): davidkhala (Fri, 02 Nov 2018 10:36:20 GMT): davidkhala (Fri, 02 Nov 2018 10:40:02 GMT): davidkhala (Fri, 02 Nov 2018 10:40:02 GMT): lijiachuan (Fri, 02 Nov 2018 11:12:47 GMT): baohua (Fri, 02 Nov 2018 13:54:47 GMT): tolak (Fri, 02 Nov 2018 14:37:37 GMT): guolidong (Sat, 03 Nov 2018 02:41:52 GMT): baohua (Tue, 06 Nov 2018 01:30:05 GMT): baohua (Wed, 07 Nov 2018 03:26:03 GMT): zerppen (Thu, 08 Nov 2018 05:47:53 GMT): dijun (Fri, 09 Nov 2018 13:50:50 GMT): maozhuzi (Mon, 12 Nov 2018 13:48:10 GMT): luke.gold (Tue, 13 Nov 2018 03:08:19 GMT): Randyshu2018 (Wed, 14 Nov 2018 11:15:30 GMT): lcj (Fri, 16 Nov 2018 04:30:58 GMT): baohua (Mon, 19 Nov 2018 03:23:21 GMT): baohua (Mon, 19 Nov 2018 03:23:30 GMT): lcj (Mon, 19 Nov 2018 11:50:32 GMT): marryton007 (Tue, 20 Nov 2018 08:26:28 GMT): thomasland (Tue, 20 Nov 2018 11:40:14 GMT): ping40 (Wed, 21 Nov 2018 01:04:22 GMT): marryton007 (Wed, 21 Nov 2018 01:56:49 GMT): marryton007 (Wed, 21 Nov 2018 02:15:35 GMT): marryton007 (Wed, 21 Nov 2018 02:16:51 GMT): marryton007 (Wed, 21 Nov 2018 02:19:23 GMT): ping40 (Wed, 21 Nov 2018 02:21:25 GMT): ping40 (Wed, 21 Nov 2018 02:21:25 GMT): ping40 (Wed, 21 Nov 2018 02:21:25 GMT): ping40 (Wed, 21 Nov 2018 02:23:08 GMT): marryton007 (Wed, 21 Nov 2018 02:32:07 GMT): marryton007 (Wed, 21 Nov 2018 02:32:27 GMT): marryton007 (Wed, 21 Nov 2018 02:41:28 GMT): marryton007 (Wed, 21 Nov 2018 02:41:55 GMT): flyingbird2017 (Wed, 21 Nov 2018 02:42:22 GMT): marryton007 (Wed, 21 Nov 2018 09:06:16 GMT): ping40 (Thu, 22 Nov 2018 00:48:42 GMT): ttarey (Mon, 26 Nov 2018 02:12:57 GMT): leon.one (Mon, 26 Nov 2018 02:52:56 GMT): leon.one (Mon, 26 Nov 2018 04:15:09 GMT): leon.one (Mon, 26 Nov 2018 04:20:58 GMT): louisliu2048 (Mon, 26 Nov 2018 08:28:24 GMT): zixian5 (Tue, 27 Nov 2018 12:37:11 GMT): baohua (Wed, 28 Nov 2018 01:48:16 GMT): wangkaixuan (Wed, 28 Nov 2018 05:36:43 GMT): aQua (Thu, 29 Nov 2018 03:25:48 GMT): wangkaixuan (Thu, 29 Nov 2018 13:16:01 GMT): baohua (Thu, 29 Nov 2018 15:09:23 GMT): newlife 1 (Fri, 30 Nov 2018 08:36:08 GMT): louisliu2048 (Mon, 03 Dec 2018 01:21:44 GMT): baohua (Tue, 04 Dec 2018 01:48:46 GMT): liutch (Tue, 04 Dec 2018 03:03:01 GMT): wangkaixuan (Wed, 05 Dec 2018 06:28:52 GMT): wangkaixuan (Wed, 05 Dec 2018 06:28:52 GMT): cn-ygf (Wed, 05 Dec 2018 06:47:43 GMT): cn-ygf (Wed, 05 Dec 2018 06:49:01 GMT): cn-ygf (Wed, 05 Dec 2018 06:49:12 GMT): baohua (Thu, 06 Dec 2018 05:49:05 GMT): cn-ygf (Thu, 06 Dec 2018 05:49:56 GMT): cn-ygf (Thu, 06 Dec 2018 05:51:05 GMT): cn-ygf (Thu, 06 Dec 2018 05:51:12 GMT): cn-ygf (Thu, 06 Dec 2018 05:51:42 GMT): stone-ch (Thu, 06 Dec 2018 06:06:19 GMT): labcoinpoc (Thu, 06 Dec 2018 07:29:44 GMT): wangkaixuan (Thu, 06 Dec 2018 08:09:07 GMT): cn-ygf (Thu, 06 Dec 2018 08:12:20 GMT): cn-ygf (Thu, 06 Dec 2018 08:12:26 GMT): wangkaixuan (Thu, 06 Dec 2018 08:16:19 GMT): wangkaixuan (Thu, 06 Dec 2018 08:16:20 GMT): wangkaixuan (Thu, 06 Dec 2018 08:21:59 GMT): cn-ygf (Thu, 06 Dec 2018 11:34:11 GMT): Ulysses (Thu, 06 Dec 2018 12:29:41 GMT): Randyshu2018 (Fri, 07 Dec 2018 09:53:12 GMT): baohua (Fri, 07 Dec 2018 12:51:16 GMT): AlanYang (Tue, 11 Dec 2018 13:23:18 GMT): NickXie (Tue, 18 Dec 2018 07:11:31 GMT): wangrangli (Wed, 19 Dec 2018 09:55:45 GMT): AlanYang (Thu, 20 Dec 2018 07:08:45 GMT): AlanYang (Thu, 20 Dec 2018 07:09:30 GMT): baohua (Fri, 21 Dec 2018 01:50:16 GMT): baohua (Wed, 26 Dec 2018 08:46:24 GMT): wangkaixuan (Sun, 30 Dec 2018 07:53:05 GMT): baohua (Wed, 02 Jan 2019 05:46:51 GMT): gongliaoan (Wed, 02 Jan 2019 09:15:27 GMT): zhilongliu (Wed, 02 Jan 2019 11:23:12 GMT): BingoYan (Thu, 03 Jan 2019 03:54:34 GMT): BingoYan (Thu, 03 Jan 2019 04:04:20 GMT): AlanYang (Fri, 04 Jan 2019 03:23:04 GMT): wangkaixuan (Sat, 05 Jan 2019 14:35:08 GMT): davidkhala (Tue, 08 Jan 2019 14:00:31 GMT): baohua (Wed, 09 Jan 2019 01:37:12 GMT): lcj (Thu, 10 Jan 2019 08:45:24 GMT): Randyshu2018 (Thu, 10 Jan 2019 15:15:15 GMT): BingoYan (Mon, 14 Jan 2019 08:13:44 GMT): moubuns (Wed, 16 Jan 2019 03:46:13 GMT): guaguawa.github.io (Thu, 17 Jan 2019 00:45:05 GMT): guaguawa.github.io (Fri, 18 Jan 2019 02:41:04 GMT): guaguawa.github.io (Fri, 18 Jan 2019 02:42:18 GMT): baohua (Fri, 18 Jan 2019 02:45:14 GMT): baohua (Fri, 18 Jan 2019 02:45:27 GMT): guaguawa.github.io (Fri, 18 Jan 2019 02:47:13 GMT): baohua (Fri, 18 Jan 2019 02:49:23 GMT): guaguawa.github.io (Fri, 18 Jan 2019 02:52:26 GMT): guaguawa.github.io (Fri, 18 Jan 2019 02:52:47 GMT): Cblingh (Sat, 19 Jan 2019 03:22:40 GMT): louisliu2048 (Mon, 21 Jan 2019 11:44:26 GMT): baohua (Wed, 23 Jan 2019 01:03:03 GMT): louisliu2048 (Thu, 24 Jan 2019 09:26:53 GMT): wangkaixuan (Thu, 24 Jan 2019 10:59:49 GMT): allanlee2019 (Thu, 24 Jan 2019 17:12:24 GMT): zxy 2 (Fri, 25 Jan 2019 12:19:57 GMT): baohua (Wed, 30 Jan 2019 21:55:22 GMT): hexiaohu (Sat, 09 Feb 2019 10:11:10 GMT): xjmDM (Sat, 09 Feb 2019 12:26:27 GMT): xjmDM (Sat, 09 Feb 2019 12:26:45 GMT): xjmDM (Sat, 09 Feb 2019 12:30:18 GMT): xjmDM (Sat, 09 Feb 2019 12:30:29 GMT): hexiaohu (Sun, 10 Feb 2019 09:17:10 GMT): baohua (Mon, 11 Feb 2019 02:56:44 GMT): xDxD (Mon, 11 Feb 2019 08:24:05 GMT): xDxD (Mon, 11 Feb 2019 08:29:28 GMT): xDxD (Tue, 12 Feb 2019 03:33:40 GMT): xuxuran (Tue, 12 Feb 2019 03:53:33 GMT): tinywell (Wed, 13 Feb 2019 01:22:22 GMT): xDxD (Wed, 13 Feb 2019 01:31:32 GMT): tinywell (Wed, 13 Feb 2019 01:45:16 GMT): xDxD (Wed, 13 Feb 2019 01:48:08 GMT): guaguawa.github.io (Wed, 13 Feb 2019 02:26:21 GMT): xDxD (Wed, 13 Feb 2019 12:09:39 GMT): guaguawa.github.io (Thu, 14 Feb 2019 01:02:28 GMT): xDxD (Thu, 14 Feb 2019 01:31:19 GMT): guaguawa.github.io (Thu, 14 Feb 2019 01:38:25 GMT): xDxD (Thu, 14 Feb 2019 03:23:51 GMT): hexiaohu (Tue, 19 Feb 2019 02:16:21 GMT): firevenus2019 (Thu, 21 Feb 2019 07:21:10 GMT): VipinB (Thu, 21 Feb 2019 15:18:08 GMT): VipinB (Thu, 21 Feb 2019 15:22:59 GMT): VipinB (Thu, 21 Feb 2019 15:25:46 GMT): VipinB (Thu, 21 Feb 2019 15:56:49 GMT): baohua (Thu, 21 Feb 2019 16:00:21 GMT): VipinB (Thu, 21 Feb 2019 20:01:27 GMT): baohua (Fri, 22 Feb 2019 01:13:59 GMT): baohua (Mon, 25 Feb 2019 13:27:52 GMT): lip-inagora (Thu, 28 Feb 2019 00:44:59 GMT): duwenhui (Fri, 01 Mar 2019 08:48:12 GMT): baohua (Fri, 01 Mar 2019 09:04:29 GMT): wangkaixuan (Mon, 04 Mar 2019 11:00:51 GMT): xDxD (Mon, 04 Mar 2019 11:26:54 GMT): wangkaixuan (Mon, 04 Mar 2019 13:28:17 GMT): james3443112 (Wed, 06 Mar 2019 14:41:49 GMT): baohua (Thu, 07 Mar 2019 03:58:21 GMT): houqinghui (Thu, 07 Mar 2019 06:29:56 GMT): houqinghui (Thu, 07 Mar 2019 06:31:24 GMT): edmundto (Fri, 08 Mar 2019 02:10:34 GMT): iamsteveng (Fri, 08 Mar 2019 02:31:15 GMT): hexiaohu (Fri, 08 Mar 2019 10:11:03 GMT): Tom-Xu-CNXA (Sat, 09 Mar 2019 03:04:52 GMT): richzhao (Mon, 11 Mar 2019 01:44:55 GMT): baohua (Mon, 11 Mar 2019 04:14:11 GMT): baohua (Mon, 11 Mar 2019 04:14:29 GMT): davidkhala (Mon, 11 Mar 2019 05:17:10 GMT): davidkhala (Mon, 11 Mar 2019 05:18:09 GMT): davidkhala (Mon, 11 Mar 2019 06:03:12 GMT): wangkaixuan (Mon, 11 Mar 2019 06:30:23 GMT): XingZhiZhang (Mon, 11 Mar 2019 09:22:03 GMT): XingZhiZhang (Mon, 11 Mar 2019 09:37:07 GMT): Pillar (Tue, 12 Mar 2019 05:47:07 GMT): Pillar (Tue, 12 Mar 2019 05:48:25 GMT): VipinB (Thu, 14 Mar 2019 16:07:29 GMT): RealDeanZhao (Fri, 15 Mar 2019 07:43:06 GMT): XingZhiZhang (Fri, 15 Mar 2019 09:52:02 GMT): XingZhiZhang (Fri, 15 Mar 2019 09:54:51 GMT): hexiaohu (Tue, 19 Mar 2019 02:24:49 GMT): davidkhala (Tue, 19 Mar 2019 08:25:27 GMT): davidkhala (Tue, 19 Mar 2019 08:25:27 GMT): guoger (Tue, 19 Mar 2019 08:51:22 GMT): hexiaohu (Tue, 19 Mar 2019 09:18:47 GMT): guoger (Tue, 19 Mar 2019 09:23:31 GMT): hexiaohu (Tue, 19 Mar 2019 09:25:57 GMT): guoger (Tue, 19 Mar 2019 09:28:29 GMT): guoger (Tue, 19 Mar 2019 09:28:38 GMT): hexiaohu (Tue, 19 Mar 2019 09:29:51 GMT): hexiaohu (Tue, 19 Mar 2019 09:31:15 GMT): hexiaohu (Tue, 19 Mar 2019 09:35:10 GMT): hexiaohu (Tue, 19 Mar 2019 09:36:19 GMT): guoger (Tue, 19 Mar 2019 09:37:29 GMT): guoger (Tue, 19 Mar 2019 09:38:46 GMT): davidkhala (Tue, 19 Mar 2019 10:58:38 GMT): hexiaohu (Tue, 19 Mar 2019 12:22:05 GMT): VipinB (Tue, 19 Mar 2019 20:48:01 GMT): VipinB (Tue, 19 Mar 2019 20:48:28 GMT): sunlidong (Wed, 20 Mar 2019 10:14:18 GMT): sunlidong (Wed, 20 Mar 2019 10:17:46 GMT): baohua (Thu, 21 Mar 2019 08:20:38 GMT): Tom-Xu-CNXA (Fri, 22 Mar 2019 06:42:49 GMT): richzhao (Mon, 25 Mar 2019 22:39:04 GMT): tinywell (Thu, 28 Mar 2019 02:59:50 GMT): tinywell (Thu, 28 Mar 2019 03:31:44 GMT): gdzz (Thu, 28 Mar 2019 07:51:45 GMT): baohua (Thu, 28 Mar 2019 07:55:39 GMT): VipinB (Mon, 01 Apr 2019 13:51:21 GMT): ZichengWang (Mon, 01 Apr 2019 20:47:57 GMT): hexiaohu (Thu, 04 Apr 2019 08:58:22 GMT): baohua (Thu, 04 Apr 2019 13:51:48 GMT): VipinB (Sun, 07 Apr 2019 13:32:11 GMT): VipinB (Sun, 07 Apr 2019 13:32:11 GMT): Cong (Mon, 08 Apr 2019 11:14:54 GMT): guoger (Tue, 09 Apr 2019 03:20:30 GMT): Randyshu2018 (Tue, 09 Apr 2019 07:22:02 GMT): hexiaohu (Tue, 09 Apr 2019 07:59:11 GMT): guoger (Tue, 09 Apr 2019 08:42:00 GMT): guoger (Tue, 09 Apr 2019 08:42:12 GMT): Randyshu2018 (Tue, 09 Apr 2019 10:03:04 GMT): hexiaohu (Tue, 09 Apr 2019 14:12:15 GMT): guoger (Tue, 09 Apr 2019 15:12:53 GMT): guoger (Tue, 09 Apr 2019 15:13:52 GMT): rjones (Tue, 09 Apr 2019 16:47:47 GMT): hexiaohu (Wed, 10 Apr 2019 00:56:44 GMT): baohua (Wed, 10 Apr 2019 02:39:21 GMT): guoger (Wed, 10 Apr 2019 03:41:33 GMT): davidkhala (Wed, 10 Apr 2019 07:11:31 GMT): davidkhala (Wed, 10 Apr 2019 07:14:27 GMT): guoger (Wed, 10 Apr 2019 07:15:41 GMT): davidkhala (Wed, 10 Apr 2019 07:17:29 GMT): guoger (Wed, 10 Apr 2019 07:20:24 GMT): guoger (Wed, 10 Apr 2019 07:20:51 GMT): guoger (Wed, 10 Apr 2019 07:21:08 GMT): davidkhala (Wed, 10 Apr 2019 07:21:35 GMT): guoger (Wed, 10 Apr 2019 07:21:41 GMT): davidkhala (Wed, 10 Apr 2019 07:21:49 GMT): guoger (Wed, 10 Apr 2019 07:22:02 GMT): davidkhala (Wed, 10 Apr 2019 07:23:07 GMT): guoger (Wed, 10 Apr 2019 07:24:39 GMT): davidkhala (Wed, 10 Apr 2019 07:27:31 GMT): guoger (Wed, 10 Apr 2019 07:29:56 GMT): guoger (Wed, 10 Apr 2019 07:29:56 GMT): guoger (Wed, 10 Apr 2019 07:29:56 GMT): davidkhala (Wed, 10 Apr 2019 07:31:36 GMT): guoger (Wed, 10 Apr 2019 07:35:11 GMT): davidkhala (Wed, 10 Apr 2019 07:37:43 GMT): guoger (Wed, 10 Apr 2019 07:39:03 GMT): guoger (Wed, 10 Apr 2019 07:39:18 GMT): davidkhala (Wed, 10 Apr 2019 07:41:29 GMT): guoger (Wed, 10 Apr 2019 07:42:09 GMT): guoger (Wed, 10 Apr 2019 07:42:19 GMT): guoger (Wed, 10 Apr 2019 07:43:54 GMT): guoger (Wed, 10 Apr 2019 07:44:15 GMT): guoger (Wed, 10 Apr 2019 07:44:22 GMT): guoger (Wed, 10 Apr 2019 07:45:36 GMT): guoger (Wed, 10 Apr 2019 07:45:36 GMT): davidkhala (Wed, 10 Apr 2019 07:47:56 GMT): davidkhala (Wed, 10 Apr 2019 07:48:53 GMT): guoger (Wed, 10 Apr 2019 07:49:52 GMT): guoger (Wed, 10 Apr 2019 07:50:31 GMT): guoger (Wed, 10 Apr 2019 07:51:13 GMT): davidkhala (Wed, 10 Apr 2019 07:51:15 GMT): davidkhala (Wed, 10 Apr 2019 07:51:15 GMT): guoger (Wed, 10 Apr 2019 07:51:26 GMT): guoger (Wed, 10 Apr 2019 07:51:49 GMT): guoger (Wed, 10 Apr 2019 07:51:57 GMT): davidkhala (Wed, 10 Apr 2019 07:52:29 GMT): guoger (Wed, 10 Apr 2019 07:53:19 GMT): davidkhala (Wed, 10 Apr 2019 07:53:50 GMT): guoger (Wed, 10 Apr 2019 07:53:58 GMT): davidkhala (Wed, 10 Apr 2019 07:54:54 GMT): guoger (Wed, 10 Apr 2019 07:54:58 GMT): guoger (Wed, 10 Apr 2019 07:55:08 GMT): guoger (Wed, 10 Apr 2019 07:55:12 GMT): guoger (Wed, 10 Apr 2019 07:55:12 GMT): davidkhala (Wed, 10 Apr 2019 07:55:52 GMT): davidkhala (Wed, 10 Apr 2019 08:00:56 GMT): davidkhala (Wed, 10 Apr 2019 08:00:56 GMT): davidkhala (Wed, 10 Apr 2019 08:00:56 GMT): guoger (Wed, 10 Apr 2019 09:00:42 GMT): guoger (Wed, 10 Apr 2019 09:00:42 GMT): guoger (Wed, 10 Apr 2019 09:00:42 GMT): davidkhala (Wed, 10 Apr 2019 10:25:46 GMT): guoger (Wed, 10 Apr 2019 10:44:31 GMT): hexiaohu (Wed, 10 Apr 2019 15:51:59 GMT): hexiaohu (Wed, 10 Apr 2019 15:51:59 GMT): davidkhala (Thu, 11 Apr 2019 11:46:30 GMT): davidkhala (Thu, 11 Apr 2019 11:47:10 GMT): guoger (Fri, 12 Apr 2019 01:50:28 GMT): wangrangli (Fri, 12 Apr 2019 02:55:14 GMT): davidkhala (Fri, 12 Apr 2019 03:03:29 GMT): davidkhala (Fri, 12 Apr 2019 03:04:16 GMT): davidkhala (Fri, 12 Apr 2019 03:04:16 GMT): guoger (Fri, 12 Apr 2019 03:08:55 GMT): davidkhala (Fri, 12 Apr 2019 03:21:35 GMT): davidkhala (Fri, 12 Apr 2019 03:35:59 GMT): guoger (Fri, 12 Apr 2019 03:36:37 GMT): davidkhala (Fri, 12 Apr 2019 03:41:55 GMT): davidkhala (Fri, 12 Apr 2019 03:43:21 GMT): davidkhala (Fri, 12 Apr 2019 03:43:21 GMT): davidkhala (Fri, 12 Apr 2019 03:43:21 GMT): davidkhala (Fri, 12 Apr 2019 03:43:42 GMT): guoger (Fri, 12 Apr 2019 03:47:29 GMT): guoger (Fri, 12 Apr 2019 03:47:35 GMT): davidkhala (Fri, 12 Apr 2019 03:50:51 GMT): davidkhala (Fri, 12 Apr 2019 05:27:40 GMT): guoger (Fri, 12 Apr 2019 06:41:12 GMT): davidkhala (Fri, 12 Apr 2019 07:24:40 GMT): davidkhala (Fri, 12 Apr 2019 07:24:40 GMT): hexiaohu (Fri, 12 Apr 2019 08:10:58 GMT): davidkhala (Fri, 12 Apr 2019 10:23:26 GMT): guoger (Fri, 12 Apr 2019 14:08:21 GMT): davidkhala (Fri, 12 Apr 2019 14:18:53 GMT): davidkhala (Fri, 12 Apr 2019 14:19:53 GMT): hexiaohu (Mon, 15 Apr 2019 05:33:14 GMT): guoger (Mon, 15 Apr 2019 06:27:27 GMT): hexiaohu (Tue, 16 Apr 2019 01:05:46 GMT): tinywell (Tue, 16 Apr 2019 07:03:31 GMT): guoger (Tue, 16 Apr 2019 07:24:57 GMT): guoger (Tue, 16 Apr 2019 07:27:15 GMT): guoger (Tue, 16 Apr 2019 07:27:41 GMT): tinywell (Tue, 16 Apr 2019 07:36:17 GMT): tinywell (Tue, 16 Apr 2019 09:28:01 GMT): davidkhala (Tue, 16 Apr 2019 09:37:34 GMT): davidkhala (Tue, 16 Apr 2019 09:38:05 GMT): hexiaohu (Tue, 16 Apr 2019 15:28:26 GMT): hexiaohu (Tue, 16 Apr 2019 15:35:14 GMT): VipinB (Tue, 16 Apr 2019 20:29:37 GMT): VipinB (Tue, 16 Apr 2019 20:29:37 GMT): davidkhala (Wed, 17 Apr 2019 03:15:33 GMT): hexiaohu (Wed, 17 Apr 2019 05:16:41 GMT): davidkhala (Wed, 17 Apr 2019 05:44:09 GMT): hexiaohu (Wed, 17 Apr 2019 05:50:38 GMT): davidkhala (Wed, 17 Apr 2019 06:44:59 GMT): hexiaohu (Wed, 17 Apr 2019 07:16:13 GMT): davidkhala (Wed, 17 Apr 2019 07:19:23 GMT): davidkhala (Wed, 17 Apr 2019 07:20:20 GMT): davidkhala (Wed, 17 Apr 2019 07:24:26 GMT): davidkhala (Wed, 17 Apr 2019 07:24:26 GMT): davidkhala (Wed, 17 Apr 2019 07:24:54 GMT): hexiaohu (Thu, 18 Apr 2019 13:25:58 GMT): luckforzhang (Thu, 18 Apr 2019 13:25:58 GMT): luckforzhang (Fri, 19 Apr 2019 06:10:36 GMT): guoger (Tue, 23 Apr 2019 06:22:53 GMT): guoger (Tue, 23 Apr 2019 06:22:53 GMT): james3443112 (Thu, 25 Apr 2019 10:15:54 GMT): james3443112 (Thu, 25 Apr 2019 10:19:23 GMT): james3443112 (Thu, 25 Apr 2019 10:19:46 GMT): james3443112 (Thu, 25 Apr 2019 10:20:03 GMT): guoger (Thu, 25 Apr 2019 10:21:44 GMT): james3443112 (Thu, 25 Apr 2019 10:22:59 GMT): james3443112 (Thu, 25 Apr 2019 10:23:31 GMT): guoger (Thu, 25 Apr 2019 10:24:24 GMT): guoger (Thu, 25 Apr 2019 10:24:36 GMT): james3443112 (Thu, 25 Apr 2019 10:24:39 GMT): james3443112 (Thu, 25 Apr 2019 10:25:30 GMT): guoger (Thu, 25 Apr 2019 10:26:07 GMT): james3443112 (Thu, 25 Apr 2019 10:27:20 GMT): james3443112 (Thu, 25 Apr 2019 10:27:41 GMT): guoger (Thu, 25 Apr 2019 10:28:44 GMT): james3443112 (Thu, 25 Apr 2019 10:30:04 GMT): guoger (Thu, 25 Apr 2019 10:34:06 GMT): james3443112 (Thu, 25 Apr 2019 10:37:16 GMT): james3443112 (Thu, 25 Apr 2019 10:38:59 GMT): james3443112 (Thu, 25 Apr 2019 10:39:09 GMT): guoger (Thu, 25 Apr 2019 11:26:19 GMT): james3443112 (Thu, 25 Apr 2019 11:28:12 GMT): cs-wang (Thu, 25 Apr 2019 12:35:16 GMT): stone-ch (Fri, 26 Apr 2019 00:48:51 GMT): james3443112 (Fri, 26 Apr 2019 01:04:55 GMT): stone-ch (Fri, 26 Apr 2019 01:22:58 GMT): lzh 3 (Sat, 27 Apr 2019 06:08:18 GMT): ZLL (Sat, 27 Apr 2019 12:40:38 GMT): ZLL (Sat, 27 Apr 2019 12:42:36 GMT): Randyshu2018 (Sun, 28 Apr 2019 08:45:44 GMT): lepanzhang (Sun, 05 May 2019 04:49:20 GMT): Tom-Xu-CNXA (Sun, 05 May 2019 07:42:24 GMT): guoger (Sun, 05 May 2019 10:03:29 GMT): bruce.shaw (Sun, 05 May 2019 14:34:07 GMT): Tom-Xu-CNXA (Sun, 05 May 2019 14:34:57 GMT): guoger (Mon, 06 May 2019 01:50:57 GMT): Tom-Xu-CNXA (Mon, 06 May 2019 05:24:46 GMT): Tom-Xu-CNXA (Mon, 06 May 2019 05:24:46 GMT): baohua (Mon, 06 May 2019 08:37:56 GMT): Ulysses (Mon, 06 May 2019 08:49:48 GMT): Ulysses (Mon, 06 May 2019 08:49:48 GMT): guoger (Mon, 06 May 2019 14:05:24 GMT): Tom-Xu-CNXA (Tue, 07 May 2019 09:26:46 GMT): bruce.shaw (Thu, 09 May 2019 09:23:18 GMT): baohua (Thu, 09 May 2019 14:34:49 GMT): davidkhala (Fri, 10 May 2019 09:35:10 GMT): davidkhala (Fri, 10 May 2019 09:41:03 GMT): davidkhala (Fri, 10 May 2019 09:42:03 GMT): guoger (Sat, 11 May 2019 02:14:02 GMT): Tom-Xu-CNXA (Sat, 11 May 2019 09:04:22 GMT): Tom-Xu-CNXA (Sat, 11 May 2019 09:16:44 GMT): hawchou (Tue, 14 May 2019 14:34:26 GMT): hawchou (Tue, 14 May 2019 14:34:26 GMT): cs-wang (Wed, 15 May 2019 09:27:16 GMT): cs-wang (Wed, 15 May 2019 09:28:47 GMT): houqinghui (Thu, 16 May 2019 02:10:46 GMT): baohua (Thu, 16 May 2019 06:35:33 GMT): baohua (Thu, 16 May 2019 06:36:29 GMT): cs-wang (Fri, 17 May 2019 01:39:21 GMT): cs-wang (Fri, 17 May 2019 01:52:15 GMT): houqinghui (Fri, 17 May 2019 02:18:26 GMT): Tom-Xu-CNXA (Sun, 19 May 2019 07:53:02 GMT): baohua (Mon, 20 May 2019 02:22:33 GMT): houqinghui (Mon, 20 May 2019 03:53:44 GMT): baohua (Mon, 20 May 2019 05:49:30 GMT): Randyshu2018 (Wed, 22 May 2019 06:13:59 GMT): Henretter (Tue, 28 May 2019 03:02:13 GMT): Henretter (Tue, 28 May 2019 03:02:15 GMT): Henretter (Tue, 28 May 2019 03:02:28 GMT): Henretter (Tue, 28 May 2019 03:03:26 GMT): Henretter (Tue, 28 May 2019 03:03:44 GMT): Henretter (Tue, 28 May 2019 03:04:52 GMT): Henretter (Tue, 28 May 2019 03:05:15 GMT): Henretter (Tue, 28 May 2019 03:05:58 GMT): Henretter (Tue, 28 May 2019 03:14:26 GMT): Henretter (Tue, 28 May 2019 05:53:13 GMT): Silona (Tue, 28 May 2019 18:19:48 GMT): Silona (Tue, 28 May 2019 18:19:49 GMT): Silona (Tue, 28 May 2019 18:20:15 GMT): Silona (Tue, 28 May 2019 18:20:36 GMT): baohua (Wed, 29 May 2019 00:15:26 GMT): Silona (Wed, 29 May 2019 00:22:42 GMT): baohua (Wed, 29 May 2019 03:34:12 GMT): baohua (Wed, 29 May 2019 03:35:34 GMT): baohua (Wed, 29 May 2019 03:37:47 GMT): richzhao (Wed, 29 May 2019 03:56:27 GMT): baohua (Wed, 29 May 2019 03:58:31 GMT): Henretter (Wed, 29 May 2019 07:34:37 GMT): Henretter (Wed, 29 May 2019 07:36:59 GMT): Henretter (Wed, 29 May 2019 07:38:29 GMT): baohua (Thu, 30 May 2019 14:47:10 GMT): baohua (Thu, 30 May 2019 14:47:10 GMT): Henretter (Fri, 31 May 2019 06:34:41 GMT): richzhao (Tue, 04 Jun 2019 00:51:01 GMT): richzhao (Mon, 17 Jun 2019 13:47:56 GMT): baohua (Tue, 18 Jun 2019 01:42:47 GMT): githubcpc (Fri, 21 Jun 2019 07:26:27 GMT): james3443112 (Fri, 28 Jun 2019 03:10:49 GMT): richzhao (Tue, 02 Jul 2019 14:39:50 GMT): james3443112 (Wed, 03 Jul 2019 00:52:04 GMT): cody588 (Thu, 04 Jul 2019 10:52:32 GMT): cody588 (Wed, 10 Jul 2019 05:53:12 GMT): baohua (Wed, 10 Jul 2019 14:01:13 GMT): zhifengliang (Thu, 11 Jul 2019 01:42:14 GMT): Randyshu2018 (Mon, 15 Jul 2019 01:56:12 GMT): VipinB (Mon, 15 Jul 2019 12:14:08 GMT): Relax20190715 (Mon, 15 Jul 2019 12:42:13 GMT): richzhao (Tue, 16 Jul 2019 05:14:27 GMT): richzhao (Tue, 16 Jul 2019 05:14:48 GMT): richzhao (Tue, 16 Jul 2019 05:16:30 GMT): Henretter (Thu, 18 Jul 2019 07:55:20 GMT): baohua (Thu, 18 Jul 2019 17:28:39 GMT): Henretter (Fri, 19 Jul 2019 05:46:49 GMT): qiyun (Fri, 19 Jul 2019 07:05:31 GMT): huxd (Thu, 25 Jul 2019 06:31:27 GMT): richzhao (Mon, 29 Jul 2019 14:26:28 GMT): Henretter (Wed, 31 Jul 2019 07:25:46 GMT): Henretter (Wed, 31 Jul 2019 07:26:21 GMT): Tom-Xu-CNXA (Fri, 16 Aug 2019 02:59:36 GMT): guoger (Fri, 16 Aug 2019 03:47:20 GMT): Tom-Xu-CNXA (Fri, 16 Aug 2019 04:21:02 GMT): Tom-Xu-CNXA (Fri, 16 Aug 2019 04:21:02 GMT): davidkhala (Mon, 19 Aug 2019 13:25:58 GMT): davidkhala (Mon, 19 Aug 2019 13:27:10 GMT): galaxystar (Tue, 20 Aug 2019 01:27:51 GMT): galaxystar (Tue, 20 Aug 2019 01:36:03 GMT): Tom-Xu-CNXA (Tue, 20 Aug 2019 05:55:34 GMT): Tom-Xu-CNXA (Thu, 22 Aug 2019 08:44:15 GMT): Tom-Xu-CNXA (Thu, 22 Aug 2019 08:45:43 GMT): Tom-Xu-CNXA (Thu, 22 Aug 2019 08:46:00 GMT): shitaibin (Thu, 22 Aug 2019 12:19:53 GMT): davidkhala (Fri, 23 Aug 2019 03:48:50 GMT): davidkhala (Fri, 23 Aug 2019 03:49:34 GMT): Tom-Xu-CNXA (Fri, 23 Aug 2019 03:56:57 GMT): Tom-Xu-CNXA (Fri, 23 Aug 2019 04:02:56 GMT): Tom-Xu-CNXA (Fri, 23 Aug 2019 04:02:56 GMT): Tom-Xu-CNXA (Fri, 23 Aug 2019 04:04:09 GMT): Tom-Xu-CNXA (Fri, 23 Aug 2019 04:06:32 GMT): Tom-Xu-CNXA (Fri, 23 Aug 2019 04:07:55 GMT): davidkhala (Fri, 23 Aug 2019 04:26:53 GMT): Tom-Xu-CNXA (Fri, 23 Aug 2019 04:45:40 GMT): Tom-Xu-CNXA (Fri, 23 Aug 2019 04:45:40 GMT): Jasonyou (Fri, 23 Aug 2019 15:29:43 GMT): steveLiuu (Fri, 30 Aug 2019 09:49:46 GMT): steveLiuu (Fri, 30 Aug 2019 09:49:47 GMT): baohua (Wed, 11 Sep 2019 18:26:35 GMT): davidkhala (Tue, 17 Sep 2019 03:47:38 GMT): davidkhala (Tue, 17 Sep 2019 04:03:30 GMT): davidkhala (Tue, 17 Sep 2019 04:03:35 GMT): Silona (Tue, 17 Sep 2019 13:41:30 GMT): Silona (Tue, 17 Sep 2019 13:41:32 GMT): guoger (Wed, 18 Sep 2019 08:20:51 GMT): Tom-Xu-CNXA (Fri, 20 Sep 2019 15:08:21 GMT): Tom-Xu-CNXA (Fri, 20 Sep 2019 15:10:17 GMT): baohua (Wed, 25 Sep 2019 16:23:13 GMT): chenchongswjtu (Sun, 29 Sep 2019 06:42:35 GMT): chenchongswjtu (Sun, 29 Sep 2019 06:42:36 GMT): Tom-Xu-CNXA (Tue, 15 Oct 2019 09:07:32 GMT): Tom-Xu-CNXA (Tue, 15 Oct 2019 09:07:32 GMT): githubcpc (Mon, 28 Oct 2019 08:19:48 GMT): githubcpc (Mon, 28 Oct 2019 08:20:26 GMT): guoger (Mon, 28 Oct 2019 08:24:37 GMT): githubcpc (Mon, 28 Oct 2019 08:27:20 GMT): baohua (Thu, 31 Oct 2019 18:18:18 GMT): kylehsieh (Fri, 01 Nov 2019 07:30:19 GMT): davidkhala (Wed, 06 Nov 2019 02:05:25 GMT): hcg1314 (Fri, 08 Nov 2019 03:49:59 GMT): Randyshu2018 (Sat, 09 Nov 2019 08:56:13 GMT): githubcpc (Mon, 11 Nov 2019 07:34:03 GMT): githubcpc (Mon, 11 Nov 2019 07:34:38 GMT): Fabiozh (Thu, 21 Nov 2019 13:39:35 GMT): Hengming (Fri, 22 Nov 2019 12:39:40 GMT): dexhunter (Fri, 29 Nov 2019 02:25:33 GMT): dexhunter (Fri, 29 Nov 2019 02:28:35 GMT): GabrielEngel (Mon, 02 Dec 2019 08:27:45 GMT): davidkhala (Wed, 04 Dec 2019 02:04:39 GMT): Silona (Wed, 11 Dec 2019 21:10:05 GMT): Silona (Wed, 11 Dec 2019 21:45:36 GMT): Silona (Wed, 11 Dec 2019 22:02:56 GMT): Hengming (Fri, 13 Dec 2019 04:07:58 GMT): githubcpc (Tue, 17 Dec 2019 01:51:31 GMT): Randyshu2018 (Thu, 19 Dec 2019 10:43:33 GMT): wuyanpig (Wed, 01 Jan 2020 15:42:28 GMT): ice-fire-x (Sun, 12 Jan 2020 05:53:37 GMT): Silona (Tue, 14 Jan 2020 16:51:09 GMT): Silona (Tue, 14 Jan 2020 17:06:39 GMT): ArthurYongShi (Wed, 15 Jan 2020 07:14:05 GMT): Silona (Mon, 27 Jan 2020 22:28:06 GMT): dexhunter (Thu, 06 Feb 2020 08:32:08 GMT): Silona (Thu, 13 Feb 2020 18:26:31 GMT): Silona (Mon, 17 Feb 2020 22:19:38 GMT): frankouyang (Sat, 22 Feb 2020 04:33:43 GMT): davidkhala (Wed, 26 Feb 2020 04:12:23 GMT): baohua (Fri, 28 Feb 2020 00:53:28 GMT): dexhunter (Fri, 28 Feb 2020 01:30:00 GMT): dexhunter (Sun, 01 Mar 2020 03:30:36 GMT): dexhunter (Sun, 01 Mar 2020 03:30:52 GMT): baohua (Wed, 04 Mar 2020 17:20:24 GMT): Tom-Xu-CNXA (Sun, 08 Mar 2020 14:39:35 GMT): Tom-Xu-CNXA (Sun, 08 Mar 2020 15:36:34 GMT): baohua (Fri, 13 Mar 2020 22:07:50 GMT): cctv 1 (Sun, 15 Mar 2020 04:15:36 GMT): cctv 1 (Sun, 15 Mar 2020 04:15:52 GMT): cctv 1 (Sun, 15 Mar 2020 04:16:33 GMT): cctv 1 (Sun, 15 Mar 2020 04:17:14 GMT): cctv 1 (Sun, 15 Mar 2020 04:32:03 GMT): duwenhui (Sun, 15 Mar 2020 13:45:49 GMT): tinywell (Tue, 17 Mar 2020 03:28:12 GMT): Tom-Xu-CNXA (Mon, 23 Mar 2020 09:41:17 GMT): Tom-Xu-CNXA (Mon, 23 Mar 2020 09:41:17 GMT): tinywell (Tue, 24 Mar 2020 03:23:57 GMT): Tom-Xu-CNXA (Tue, 24 Mar 2020 15:22:39 GMT): Tom-Xu-CNXA (Tue, 24 Mar 2020 15:23:02 GMT): Tom-Xu-CNXA (Tue, 24 Mar 2020 15:34:47 GMT): feiyang_tan (Tue, 31 Mar 2020 12:18:21 GMT): xiedezi (Fri, 10 Apr 2020 08:51:01 GMT): xiedezi (Fri, 10 Apr 2020 08:51:03 GMT): githubcpc (Fri, 24 Apr 2020 09:22:22 GMT): githubcpc (Fri, 24 Apr 2020 09:23:21 GMT): githubcpc (Fri, 24 Apr 2020 09:27:38 GMT): stone-ch (Sun, 26 Apr 2020 01:57:56 GMT): randyshu (Thu, 07 May 2020 06:12:15 GMT): hello2mao (Fri, 15 May 2020 14:32:40 GMT): rjones (Tue, 16 Jun 2020 17:19:08 GMT): rjones (Tue, 16 Jun 2020 17:19:33 GMT): stone-ch (Wed, 17 Jun 2020 01:07:08 GMT): Mopack (Wed, 17 Jun 2020 03:39:09 GMT): rjones (Wed, 17 Jun 2020 06:08:45 GMT): rjones (Wed, 17 Jun 2020 06:09:04 GMT): DavidBoswell (Wed, 17 Jun 2020 06:09:04 GMT): rjones (Thu, 18 Jun 2020 17:26:30 GMT): rjones (Thu, 18 Jun 2020 19:25:06 GMT): davidkhala (Fri, 19 Jun 2020 02:54:40 GMT): davidkhala (Fri, 19 Jun 2020 02:57:36 GMT): stone-ch (Fri, 19 Jun 2020 03:08:36 GMT): stone-ch (Fri, 19 Jun 2020 03:14:24 GMT): nauqnew (Fri, 19 Jun 2020 06:20:45 GMT): davidkhala (Wed, 24 Jun 2020 09:39:06 GMT): zhubao315 (Wed, 24 Jun 2020 22:35:50 GMT): zhubao315 (Thu, 25 Jun 2020 13:29:29 GMT): rjones (Thu, 25 Jun 2020 14:18:53 GMT): davidkhala (Fri, 26 Jun 2020 05:18:43 GMT): zhubao315 (Fri, 26 Jun 2020 05:23:36 GMT): flytofly (Thu, 02 Jul 2020 03:20:30 GMT): flytofly (Thu, 02 Jul 2020 03:20:45 GMT): flytofly (Thu, 02 Jul 2020 03:21:38 GMT): flytofly (Thu, 02 Jul 2020 03:22:15 GMT): flytofly (Thu, 02 Jul 2020 03:22:55 GMT): flytofly (Thu, 02 Jul 2020 03:24:54 GMT): ever-upwards (Tue, 07 Jul 2020 11:45:19 GMT): davidkhala (Thu, 09 Jul 2020 16:04:33 GMT): stone-ch (Fri, 10 Jul 2020 01:48:00 GMT): lvjm (Mon, 13 Jul 2020 03:42:27 GMT): lvjm (Mon, 13 Jul 2020 03:42:28 GMT): davidkhala (Mon, 13 Jul 2020 06:46:26 GMT): flytofly (Wed, 15 Jul 2020 03:20:54 GMT): davidkhala (Sun, 19 Jul 2020 02:46:09 GMT): ysai (Wed, 29 Jul 2020 06:11:41 GMT): duwenhui (Thu, 30 Jul 2020 01:30:49 GMT): davidkhala (Wed, 05 Aug 2020 04:38:01 GMT): davidkhala (Wed, 05 Aug 2020 04:38:36 GMT): weiliy (Sat, 15 Aug 2020 07:52:07 GMT): davidkhala (Sun, 16 Aug 2020 14:16:32 GMT): randyshu (Fri, 21 Aug 2020 02:59:48 GMT): randyshu (Fri, 21 Aug 2020 03:00:06 GMT): davidkhala (Mon, 24 Aug 2020 05:10:54 GMT): davidkhala (Mon, 24 Aug 2020 05:11:27 GMT): davidkhala (Mon, 24 Aug 2020 05:11:43 GMT): rjones (Wed, 26 Aug 2020 14:12:17 GMT): rjones (Wed, 26 Aug 2020 14:12:17 GMT): rjones (Wed, 26 Aug 2020 14:14:01 GMT): davidkhala (Sun, 30 Aug 2020 08:37:31 GMT): davidkhala (Sun, 30 Aug 2020 08:41:49 GMT): davidkhala (Sun, 30 Aug 2020 08:44:04 GMT): rjones (Sun, 30 Aug 2020 19:21:34 GMT): rjones (Sun, 30 Aug 2020 20:05:20 GMT): rjones (Sun, 30 Aug 2020 20:05:45 GMT): Flyyellow (Fri, 04 Sep 2020 07:04:26 GMT): Flyyellow (Fri, 04 Sep 2020 07:20:51 GMT): davidkhala (Thu, 10 Sep 2020 15:32:03 GMT): hexiaohu (Thu, 17 Sep 2020 12:26:29 GMT): baohua (Thu, 17 Sep 2020 16:30:58 GMT): vioking (Fri, 18 Sep 2020 16:53:51 GMT): davidkhala (Mon, 21 Sep 2020 14:55:39 GMT): cs-wang (Fri, 25 Sep 2020 02:17:42 GMT): cs-wang (Fri, 25 Sep 2020 02:19:24 GMT): cs-wang (Fri, 25 Sep 2020 02:20:09 GMT): davidkhala (Sun, 27 Sep 2020 01:25:30 GMT): cctv 1 (Mon, 12 Oct 2020 05:16:05 GMT): davidkhala (Tue, 13 Oct 2020 01:57:40 GMT): paul-lee-attorney (Tue, 20 Oct 2020 04:01:37 GMT): paul-lee-attorney (Tue, 20 Oct 2020 04:01:37 GMT): davidkhala (Tue, 20 Oct 2020 14:48:02 GMT): davidkhala (Tue, 20 Oct 2020 14:49:08 GMT): Steiner 1 (Sun, 15 Nov 2020 05:20:44 GMT): Steiner 1 (Sun, 15 Nov 2020 05:20:45 GMT): Steiner 1 (Sun, 15 Nov 2020 05:29:34 GMT): Steiner 1 (Sun, 15 Nov 2020 07:46:00 GMT): Steiner 1 (Sun, 15 Nov 2020 13:49:09 GMT): Steiner 1 (Sun, 15 Nov 2020 13:49:41 GMT): Steiner 1 (Sun, 15 Nov 2020 13:49:43 GMT): Steiner 1 (Sun, 15 Nov 2020 13:50:09 GMT): stone-ch (Wed, 18 Nov 2020 09:18:06 GMT): stone-ch (Wed, 18 Nov 2020 09:18:54 GMT): stone-ch (Wed, 18 Nov 2020 09:20:46 GMT): stone-ch (Wed, 18 Nov 2020 09:20:46 GMT): stone-ch (Wed, 18 Nov 2020 09:24:08 GMT): stone-ch (Wed, 18 Nov 2020 09:25:56 GMT): zhangshuai (Thu, 19 Nov 2020 06:34:45 GMT): zhangshuai (Fri, 20 Nov 2020 06:11:03 GMT): stone-ch (Fri, 20 Nov 2020 06:34:48 GMT): zhangshuai (Fri, 20 Nov 2020 10:15:29 GMT): stone-ch (Fri, 20 Nov 2020 12:11:08 GMT): zhangshuai (Mon, 23 Nov 2020 08:29:31 GMT): zhangshuai (Mon, 23 Nov 2020 08:29:36 GMT): zhangshuai (Wed, 25 Nov 2020 07:10:22 GMT): zhangshuai (Wed, 25 Nov 2020 07:10:36 GMT): zhangshuai (Wed, 25 Nov 2020 07:10:59 GMT): githubckgoh1439 (Tue, 08 Dec 2020 03:15:26 GMT): stone-ch (Tue, 08 Dec 2020 03:48:28 GMT): stone-ch (Tue, 08 Dec 2020 03:49:21 GMT): yixinhuo (Tue, 22 Dec 2020 16:18:10 GMT): rjones (Thu, 14 Jan 2021 22:28:16 GMT): davidkhala (Sun, 31 Jan 2021 07:05:05 GMT): shyxuxu1 (Wed, 07 Apr 2021 09:54:53 GMT): shyxuxu1 (Wed, 07 Apr 2021 09:55:19 GMT): shyxuxu1 (Fri, 09 Apr 2021 04:12:40 GMT): rjones (Fri, 09 Apr 2021 16:10:01 GMT): shyxuxu1 (Sat, 10 Apr 2021 04:03:33 GMT): zenilvaghasiya (Wed, 28 Jul 2021 22:41:31 GMT): zenilvaghasiya (Wed, 28 Jul 2021 22:41:32 GMT): SamYuan1990 (Fri, 13 Aug 2021 13:50:03 GMT): JJeffrey (Tue, 31 Aug 2021 14:36:36 GMT): sunchiye (Wed, 01 Sep 2021 07:49:09 GMT): Fang.Fang (Fri, 10 Sep 2021 02:17:51 GMT): SeanBohan (Fri, 17 Dec 2021 20:06:19 GMT): rjones (Fri, 11 Feb 2022 23:14:11 GMT):
分别是最大允许的消息个数，最大允许的总字节数，以及尽量满足的最大字节数（比如单个消息很大，prefer
@baohua ，那是不是只要满足其中一个最大的，就要生成block了。
不能超过 嗯 满足了就生成区块
@baohua 明白了。THX
我想问下，如何用chaincode实现生成随机数字的功能？
1. 例如4个peer都执行chiancode的随机方法，但是生成出来的随机数字各自不相同。
2. 如何避免，如果我在peer执行chiancode后返回的随机数字，我抛弃。我再次调用peer执行chaincode生成随机数字，直到那个数字是我想要的，我再提交到orderer。
随机数不符合determinstic规范，区块链里面无法使用
@here 官方要发布alpha3了?
Has joined the channel.
it's going to be a beta release.
hyperledger fabric just releases its beta version, welcome to try! https://github.com/hyperledger/fabric/releases/tag/v1.0.0-beta
已经下载在跑了。sdk-java也有了beta了。
@baohua fabric-sdk-java里面的那个runChannel里面的channel.sendTransaction(successful, orderers) 为什么要给successful
因为你要把所有peer的endoser返回的结果，发送到orderer，这样orderer验证后才会去做广播。
Ok
Sending proposal to peer0.org1.example.com failed because of gRPC failure=Status{code=UNKNOWN, description=failed to obtain cds for cc_go_1 - could not find chaincode with name 'cc_go_1', cause=null}
这个是？
明明我都实例化是可以的啊
在fabric java sdk 当中channel.sendTransaction(successful, orderers).thenApply(transactionEvent -> {
我看了这个successful 是Instantiate的时候返回的
但是install Instantiate 和 发起交易都应该是独立开来的啊
@baohua
pls share the question at #fabric-sdk-java thanks
GA版是这个月发布吗
@jimthematrix 这样调用GetStateByRange有什么问题嘛, 为什么总是报错
invoke GetStateByRange method , got the error :
*runtime error: invalid memory address or nil pointer dereference*
Case:
invoke PutState() use keys:
ACCOUNT~00001302
ACCOUNT~00001309
ACCOUNT~00001310
ACCOUNT~00001322
GetStateByRange(startKey, endKey)
startKey: ACCOUNT~00000000
endKey: ACCOUNT~99999999
[ ](https://chat.hyperledger.org/channel/twg-china?msg=chsK4t3TbTy4XuBGo) @zhangchao 能不能具体介绍一下你的想法？注意加密货币的本身用途是为了鼓励参与挖矿（见中本聪原著），fabric既然不是公有链，就不需要token。
[ ](https://chat.hyperledger.org/channel/twg-china?msg=chsK4t3TbTy4XuBGo) @zhangchao 能不能具体介绍一下你的想法？注意加密货币的本身用途是为了鼓励参与提供共识服务（见中本聪原著），fabric既然不是公有链，就不需要token。
@CarlXK 试一下
```
startKey: ACCOUNT~ 00001302
endKey: ACCOUNT~ 00001323
@jimthematrix 隔壁的burrow是基于ethereum的，他集成了ethereum的理念，也包含了token在他们的数据结构中，详见我跟silasdavis的thread。不过我没有太深入的研究过burrow，不知道他们是否有mining的过程（如果按照以太坊的体系，应该是有mining的）。既然fabric并不需要矿工来保证链的算力安全，那是否可以有其他机制来生成货币，比如使用mint方法。我觉得有些时候有token能大大简化很多场景下的交易过程，提高交易的自动化，个人想法供参考。
@zhangchao burrow应该是在进行去token的工作。你提到的——有些时候有token能大大简化很多场景下的交易过程，提高交易的自动化——可以讲具体一点吗？
请问，目前如何查询一个channel的transaction记录(包括valid和invalid），另外有没有方便的接口进行一些统计？比如channel的交易总数，有效交易总数，按chaincode划分的交易总数等等？ 目前想到的是通过注册transaction event来进行手工统计，但如果有某个system chaincode能提供这种功能就更好了
比如说，交易里面包含交易金额的，可以自动在收货的时候按照一定规则将货币发给对方
如果使用网银来操作，那就得链完调用，复杂多了
[ ](https://chat.hyperledger.org/channel/twg-china?msg=PkZY5XvrxxosZHGd3) @jimthematrix
还是失败了
\[Keys:
account~ 00000000
account~ 99999999
返回结果:
Code = 5000 Message = 查询账本数据失败! Result =
AccountChainCode Operation exception! runtime error: invalid memory address or nil pointer dereference]\
[ ](https://chat.hyperledger.org/channel/twg-china?msg=PkZY5XvrxxosZHGd3) @jimthematrix
还是失败了
Keys:
account~ 00000000
account~ 99999999
返回结果:
Code = 5000 Message = 查询账本数据失败! Result =
AccountChainCode Operation exception! runtime error: invalid memory address or nil pointer dereference
我的理解是数字货币还只是数字资产，也就是说最终还是要通过法币结算才实现价值，所以数字货币是需要定价的（比如今天1btc=$2700），而这个定价波动会很大，导致用数字货币做主流商用交易结算恐怕短期内还不可行。群里面不知道有没有对金融行业很熟的，希望赐教
我的理解是加密货币还只是数字资产，也就是说最终还是要通过法币结算才实现价值，所以数字货币是需要定价的（比如今天1btc=$2700），而这个定价波动会很大，导致用数字货币做主流商用交易结算恐怕短期内还不可行。群里面不知道有没有对金融行业很熟的，希望赐教
我的理解是加密货币还只是数字资产，也就是说最终还是要通过法币结算才实现价值，所以数字货币是需要定价的（比如今天1btc=$2700），而这个定价波动会很大，导致用加密货币做主流商用交易结算恐怕短期内还不可行。群里面不知道有没有对金融行业很熟的，希望赐教
我的理解是加密货币还只是数字资产，也就是说最终还是要通过法币结算才实现价值，所以加密货币是需要定价的（比如今天1btc=$2700），而这个定价波动会很大，导致用加密货币做主流商用交易结算恐怕短期内还不可行。群里面不知道有没有对金融行业很熟的，希望赐教
@CarlXK 建议到#fabric-ledger群里问一下
好的
@zhangchao 还有，我问过burrow的开发者，所有交易的gas price都是零，所以每个smart contract账户不需要有余额，也不需要挖矿来维持货币的供给
@jimthematrix ,我们这边就是做金融，感觉需求会很多。具体到定价可以有别的办法，比如金融机构发行数字货币，同时做储备法币，数字货币就能完全跟踪法币
只要银行储备的法币足够刚性兑付就完全没问题
嗯我知道日本政府很鼓励民间发行数字货币，但目前基本都是以一家银行或者几家形成的网络范围内适用的
这个只要交易双方都承认并且发行银行在链上支持就行了，但是跟加密货币还是不一样
恩，有需求，主要看政策，hyperledger如果没有原生token的话，只能在chaincode里面去做了
@jimthematrix 用 stub.CreateCompositeKey("ACCOUNT~", []string{"00001302"}) , PutState, 然后 GetStateByRange 不能使用 stub.CreateCompositeKey(indexName, []string{"00000000"}) stub.CreateCompositeKey(indexName, []string{"99999999"})
报 First character of the key [account00000000] contains a null character which is not allowed
应该是GetStateByRange 不能使用stub.CreateCompositeKey出来的Key
@jimthematrix 用 stub.CreateCompositeKey("ACCOUNT~", []string{"00001302"}) , PutState, 然后 GetStateByRange 不能使用 stub.CreateCompositeKey(indexName, []string{"00000000"}) stub.CreateCompositeKey(indexName, []string{"99999999"})
报 First character of the key [account00000000] contains a null character which is not allowed
GetStateByRange 不能使用stub.CreateCompositeKey出来的Key, 改成GetStateByPartialCompositeKey 就可以了
Has joined the channel.
Dear all, the TWGC session at linuxcon next Monday morning will be a great opportunity to share the works/status in local community. We now have two topics for the session: 1) I will give brief introduction on the community works; 2) Volunteers share their experience on developments, documentations, adoption cases... Pls feel free to let me know if we wanna add more topics to share, thanks!
https://lc3china2017.sched.com/event/09d40224b20f830957a2165093dfd5b4
@zhangchao Burrow是基于Tendermint做共识的，不需要挖矿。 @jimthematrix 说的Gas没问题，Burrow里面使用Gas主要还是作为控制恶意攻击的手段
orderer.example.com | 2017-06-14 07:07:40.507 UTC [orderer/kafka] setupProducerForChannel -> DEBU 0e6 [channel: testchainid] Connecting to Kafka cluster: [127.0.0.1:9092]
@baohua
@here fabric可以动态添加删除peer、order节点吗？
可以
@baohua 可以说下大概的做法吗？
升级channel配置？
不用的 只要是 channel 内组织签发的 peer 直接用 admin 身份对其执行 join 命令即可
Has joined the channel.
Has joined the channel.
多谢 如何动态增删order呢？
Has joined the channel.
Has joined the channel.
目前支持多order节点吗？
Has joined the channel.
Has joined the channel.
Querying chaincode on org1/peer0...
===================== Querying on PEER0 on channel 'mychannel'... =====================
CORE_PEER_TLS_ROOTCERT_FILE=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org1.example.com/peers/peer0.org1.example.com/tls/ca.crt
CORE_PEER_TLS_KEY_FILE=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org1.example.com/peers/peer0.org1.example.com/tls/server.key
CORE_PEER_LOCALMSPID=Org1MSP
CORE_VM_ENDPOINT=unix:///host/var/run/docker.sock
CORE_PEER_TLS_CERT_FILE=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org1.example.com/peers/peer0.org1.example.com/tls/server.crt
CORE_PEER_TLS_ENABLED=true
CORE_PEER_MSPCONFIGPATH=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org1.example.com/users/Admin@org1.example.com/msp
CORE_PEER_ID=cli
CORE_LOGGING_LEVEL=DEBUG
CORE_PEER_ADDRESS=peer0.org1.example.com:7051
Attempting to Query PEER0 ...3 secs
Attempting to Query PEER0 ...6 secs
Attempting to Query PEER0 ...9 secs
Attempting to Query PEER0 ...12 secs
Attempting to Query PEER0 ...16 secs
Attempting to Query PEER0 ...19 secs
Attempting to Query PEER0 ...22 secs
Attempting to Query PEER0 ...25 secs
Attempting to Query PEER0 ...28 secs
Attempting to Query PEER0 ...31 secs
Attempting to Query PEER0 ...34 secs
Attempting to Query PEER0 ...37 secs
我吧peer0.org.example.com 给提取出来放到了另外的一台机器上了 在这里机器上执行cli的时候
执行e2e的时候遇到了这个问题
在peer0.org1.example.com 这台机器里面join 和install 都是可以的
query的时候并没有启动容器
@baohua
我使用alpha版本的时候是可以的 但是我的配置都是docker里面的
Has joined the channel.
@here 各位好，我想基于kafka配置保护多个order的ordering服务，我想问下有配置手册吗？目前我只搜到一个A Kafka-based Ordering Service for Fabric文档，但是这个文档主要侧重实现，没有具体的配置方式，谢谢~
@here 各位好，我想基于kafka配置包含多个order的ordering服务，我想问下有配置手册吗？目前我只搜到一个A Kafka-based Ordering Service for Fabric文档，但是这个文档主要侧重实现，没有具体的配置方式，谢谢~
多个order?
@here 各位好，我想基于kafka配置包含多个order的ordering服务，我想问下有配置手册吗？目前我只搜到一个A Kafka-based Ordering Service for Fabric文档，但是这个文档主要侧重实现，没有具体的配置方式，谢谢~
对的，不好意思，打错字了
请问有配置文档可以参考吗？
有的
我吧我的接一个图给你看看
多谢多谢:grinning:
@HuangLijun https://github.com/guoger/fabric-deployment
最近刚做了一个，打算慢慢在这个repo里放一些部署方法的例子，如有有比较典型的例子，也欢迎贡献
貌似network_setup.sh里面包含错误
COMPOSE_FILE=docker-compose-cli.yaml
COMPOSE_FILE_COUCH=docker-compose-couch.yaml
哪里有这个两个文件了
哦，直接用docker-compose起，忘了把那两个脚本删掉了
基本上就是照着bddtests里边改的
这些配置都是一台机器上面跑的
如果要拆分呢
底层topology对配置是透明的，只要能解析域名访问揪心过了
底层topology对配置是透明的，只要能解析域名访问就行了
对的
但是我使用beta的时候
query超市了
你用什么方式query的
@guoger 谢谢~~~
就是跑e2e的query
没有是用ｓｄｋ
e2e下面不是有一个script.sh脚本艾玛
@chenxuan 多机测试吗？我也是，tls_enable就查询超时
en
你可以试试，tls_enable=false是可以过
不知道为什么
你成功了
@qiushaoxi
tls_enable=false是可以的
这样就是传输不加密
我试试
是我配置错了地方
请大家忽略
tls_enable 的确要设置成false
Message Attachments
这里(https://github.com/hyperledger/fabric/blob/master/protos/peer/configuration.proto)注释说还有peer certificate, 咋定义里没有呢？
Has joined the channel.
Has joined the channel.
个人建议吧dc-orderer-kafka.yaml 当中的peer单独拿出来
@guoger
2017-06-16 09:54:03,506:INFO http-nio-8080-exec-4 (Utils.java:34) - ending transactionProposal to all peers with arguments:[Ljava.lang.String;@3cbfe9c9
send proposal spend:18
2017-06-16 09:54:03,524:INFO http-nio-8080-exec-4 (Utils.java:34) - Successful transaction proposal response Txid: 914ce5bd4c9a72accec54c0218fe7eb1365749b4ee979e3ed6a13cbe66c451b7 from peer peer1.org1.example.com
2017-06-16 09:54:03,524:INFO http-nio-8080-exec-4 (Utils.java:34) - Successful transaction proposal response Txid: 914ce5bd4c9a72accec54c0218fe7eb1365749b4ee979e3ed6a13cbe66c451b7 from peer peer0.org1.example.com
2017-06-16 09:54:03,524:INFO http-nio-8080-exec-4 (Utils.java:34) - Received 2 transaction proposal responses. Successful+verified: 2 . Failed: 0
2017-06-16 09:54:03,525:INFO http-nio-8080-exec-4 (Utils.java:34) - Successfully received transaction proposal responses.
2017-06-16 09:54:03,525:INFO http-nio-8080-exec-4 (Utils.java:34) - Sending chaincode transaction(add,a,1,) to orderer.
send transaction spend:2042
@baohua 每一个交易几乎花了2秒
？
xuan, pls help post ur steps and necessary system info for the question, that would help people repeat ur process and verify the result, thanks!
想问一下大家，下周一的hyperledger hackfest和linuxCon有什么关系么
同一个时间举办
not much relationship except the time :)
btw, hyperledger is an important lF founding project!
可惜啊，想同时参加是不行了
感觉都很精彩
yeap, linuxcon is more wider, including cloud, container and other open-source technologies.
我的测试很简单的 就是在我的机器上启动了fabric network 不过是kafka order
Message Attachments
然后使用java 的sdk 通过发送http请求的方式就产生交易
2017-06-16 09:54:03,506:INFO http-nio-8080-exec-4 (Utils.java:34) - ending transactionProposal to all peers with arguments:[Ljava.lang.String;@3cbfe9c9
send proposal spend:18
2017-06-16 09:54:03,524:INFO http-nio-8080-exec-4 (Utils.java:34) - Successful transaction proposal response Txid: 914ce5bd4c9a72accec54c0218fe7eb1365749b4ee979e3ed6a13cbe66c451b7 from peer peer1.org1.example.com
2017-06-16 09:54:03,524:INFO http-nio-8080-exec-4 (Utils.java:34) - Successful transaction proposal response Txid: 914ce5bd4c9a72accec54c0218fe7eb1365749b4ee979e3ed6a13cbe66c451b7 from peer peer0.org1.example.com
2017-06-16 09:54:03,524:INFO http-nio-8080-exec-4 (Utils.java:34) - Received 2 transaction proposal responses. Successful+verified: 2 . Failed: 0
2017-06-16 09:54:03,525:INFO http-nio-8080-exec-4 (Utils.java:34) - Successfully received transaction proposal responses.
2017-06-16 09:54:03,525:INFO http-nio-8080-exec-4 (Utils.java:34) - Sending chaincode transaction(add,a,1,) to orderer.
send transaction spend:2042
我大概循环了100次
几乎每一笔交易都花费了２秒多
这个谁受得了
suggest u have a look at test/tools/PTE/ if you wanna have some perf test.
PTE?
i see it
@baohua 我在hackfest wiki上提交了一个topic, 请问ppt有什么要求吗？ppt上有公司名字和logo没什么问题吧？ 另外，如果有其他注意事项，也请告知。谢谢！
好的 最好是英文
好的
slides 可以提前放到 wiki 上，加上 link
ok
Has joined the channel.
Has joined the channel.
@baohua 账本可以删除？
err := stub.DelState(A)
couchdb当中的确是没有了
多了一个block
那跟应用场景不符合啊
sorry, but what kind of scenario do not allow delete a value?
sorry, but what kind of scenario do not allow deleting a value?
sorry, but what kind of scenarios do not allow deleting a value?
那和oracle有上面区别
什么区别
@jimthematrix 问一个问题 麻烦看看test/tools/PTE目录下面执行shell的时候是没有node的模块的
怎么解决
？
[ ](https://chat.hyperledger.org/channel/twg-china?msg=e7W2Na9KHi9C9Grfs) @chenxuan 这个延迟主要是为了等生成区块，是可以设置的：
```
Orderer: &OrdererDefaults
# Orderer Type: The orderer implementation to start.
# Available types are "solo" and "kafka".
OrdererType: solo
Addresses:
- 127.0.0.1:7050
# Batch Timeout: The amount of time to wait before creating a batch.
BatchTimeout: 2s
[ ](https://chat.hyperledger.org/channel/twg-china?msg=e7W2Na9KHi9C9Grfs) @chenxuan 这个延迟主要是为了等生成区块，是可以在每个channel设置的：
```
Orderer: &OrdererDefaults
# Orderer Type: The orderer implementation to start.
# Available types are "solo" and "kafka".
OrdererType: solo
Addresses:
- 127.0.0.1:7050
# Batch Timeout: The amount of time to wait before creating a batch.
BatchTimeout: 2s
已经比比特币的10分钟和以太坊的17秒好多了，关键是可以根据需要自行设置
[ ](https://chat.hyperledger.org/channel/twg-china?msg=8C4vwJNPcrqiKADYq) @chenxuan 需要澄清一个理解误区，就是levelDB或者couchDB只不过是个cache，存放的是所以state的最新赋值，每一个状态（包括被删掉的）的历史都存放在账本里面
而账本本身是以文件形式存放的，跟状态数据库（levelDB，couchDB）是分开的
[ ](https://chat.hyperledger.org/channel/twg-china?msg=cwn9bqALRSmLsFr8a) @chenxuan 这个我不太熟悉，可以去#fabric channel里问 @dongming
Has joined the channel.
[ ](https://chat.hyperledger.org/channel/twg-china?msg=eXdBjN4yCTCo2w285) @jimthematrix 这个我理解的确是可以找到历史版本的
[ ](https://chat.hyperledger.org/channel/twg-china?msg=bRjrExhZEFTcYpmCA) @jimthematrix 如果我吧文件给删除了后果是？
我使用couchdb 我通过sdk去放了数据
Message Attachments
我通过查询是可以看到数据的
但是我去使用sdk去调用resultsIterator, err := stub.GetQueryResult(queryString)
这个方法的时候得不到数据
- getQueryResultForQueryString queryString:
{"selector":{"_id":{"$eq":"cc_go\u00002"}}}
- getQueryResultForQueryString queryResult:
[]
chaincode容器查询出来的结果是这个
@jimthematrix
@guoger
我看文档中给出的例子 貌似是没有调用这个方法过
if arg0 == "initMarble" { //create a new marble
return t.initMarble(stub, args2)
} else if arg0 == "transferMarble" { //change owner of a specific marble
return t.transferMarble(stub, args2)
} else if arg0 == "transferMarblesBasedOnColor" { //transfer all marbles of a certain color
return t.transferMarblesBasedOnColor(stub, args2)
} else if arg0 == "delete" { //delete a marble
return t.delete(stub, args2)
} else if arg0 == "readMarble" { //read a marble
return t.readMarble(stub, args2)
} else if arg0 == "queryMarblesByOwner" { //find marbles for owner X using rich query
return t.queryMarblesByOwner(stub, args2)
} else if arg0 == "queryMarbles" { //find marbles based on an ad hoc rich query
return t.queryMarbles(stub, args2)
} else if arg0 == "getHistoryForMarble" { //get history of values for a marble
return t.getHistoryForMarble(stub, args2)
} else if arg0 == "getMarblesByRange" { //get marbles based on range query
return t.getMarblesByRange(stub, args2)
}
else if arg0 == "queryMarbles" { //find marbles based on an ad hoc rich query
return t.queryMarbles(stub, args2)
例子当中没有调用过这种方法
Message Attachments
请问你们有碰到过这个错误吗？
@baohua 在编译crytogen这个工具时，出现了下图中的错误。可是我去看了pkcs11.go里对应的地方是被注释掉的。那为什么编译器还会去编译它呢？
Message Attachments
不好意思，收回刚刚这个问题，忘了这是go调用c的语法了。。。。。。:sweat_smile:
我再check一下找不到ltdl.h的原因。。。
这是由于没有安装libtool libltdl-dev 这两个包导致，在这里找到了答案：https://jira.hyperledger.org/browse/FAB-2854?page=com.atlassian.streams.streams-jira-plugin%3Aactivity-stream-issue-tab
Has joined the channel.
[ ](https://chat.hyperledger.org/channel/twg-china?msg=s6i9Su9fr6nkCM64q) @jimthematrix 但是我在两秒内产生的肯定不止一笔交易啊
使用的java sdk去发送交易的
@tolak 可以参考这里如何编译：https://github.com/yeasy/docker-hyperledger-fabric-base/blob/master/Dockerfile
https://wiki.hyperledger.org/groups/twgc/hackfest-beijing
Brian is giving the 1st speak on hypeledger projects
Brian is giving the 1st speach on hypeledger projects
live broadcasting: https://m.douyu.com/2337020
[ ](https://chat.hyperledger.org/channel/twg-china?msg=tZx4nuThgnA7Qv6Do) @chenxuan 这个很细节的容错问题还要问ledger的开发者，找 @manish-sethi @dave.enyeart 问一下
Has joined the channel.
Has joined the channel.
@jimthematrix 但是我在两秒内产生的肯定不止一笔交易啊
@chenxuan 可以同时提交很多笔交易，我说的2秒是每笔交易的延迟，并发的交易是可以同时处理到一个区块的
@jimthematrix 但是我通过 System.out.println(System.currentTimeMillis());
String[] args_ = new String[]{"init", "a", "1"};
fabricService.takeTransaction(clientMap.get(name), name, username, "peerOrg1", args_, chaincodeID);
args_ = new String[]{"init", "b", "1"};
fabricService.takeTransaction(clientMap.get(name), name, username, "peerOrg1", args_, chaincodeID);
args_ = new String[]{"add", "a", "1"};
fabricService.takeTransaction(clientMap.get(name), name, username, "peerOrg1", args_, chaincodeID);
args_ = new String[]{"add", "b", "1"};
fabricService.takeTransaction(clientMap.get(name), name, username, "peerOrg1", args_, chaincodeID);
System.out.println(System.currentTimeMillis());
居然每一笔交易都是block
[
{
"id": "5",
"dataHash": "b21d54f7406ca44de7dc7525e41d6c9647c0b2cc8628d1707827d50266545e8f",
"preHash": "532a1fe0596f1b60052b9a9d266418ec112934f849114f6dccf3978b0d8d0022",
"blockHash": "b10f44221a3c05fd356d80873921ae28a56ce2166ad28c358062b0cdca2f5af1",
"transactionCount": 1,
"transactions": []
},
{
"id": "4",
"dataHash": "91b2b8520b5ba1348aab260b2a8e07e5018fcfccd331ba15b39a4abd7a410350",
"preHash": "4ef31d5c25c59893c5d57aeee4ff0edb926d04ba6c78196cadf617f411fbce64",
"blockHash": "532a1fe0596f1b60052b9a9d266418ec112934f849114f6dccf3978b0d8d0022",
"transactionCount": 1,
"transactions": []
},
{
"id": "3",
"dataHash": "9a134ffefbe8aa5e1ea9b2179dd32b1aaf6a7100048f52ecd1a3bea6d9dd8ead",
"preHash": "ed59f0fad97add325e21f89040f5ccb824681649a283559f5927086bcec2e891",
"blockHash": "4ef31d5c25c59893c5d57aeee4ff0edb926d04ba6c78196cadf617f411fbce64",
"transactionCount": 1,
"transactions": []
},
{
"id": "2",
"dataHash": "c97791bd3844971e16d6f22eb83918d332ac4a27cadbf6daa8934a84750143d1",
"preHash": "20ffec928337dfd0eaf5564301a9d59ac2da86dc0a4acb532015b5c0128c007d",
"blockHash": "ed59f0fad97add325e21f89040f5ccb824681649a283559f5927086bcec2e891",
"transactionCount": 1,
"transactions": []
},
{
"id": "1",
"dataHash": "84aa5e31ca050b9611f7f329560f96447764c4d313398bfb0ebd69e17b3cae0c",
"preHash": "d15bf926c7e3f0eeeae0c0f92ea15da118573fdc68bfd0a74956b28a9ff1213a",
"blockHash": "20ffec928337dfd0eaf5564301a9d59ac2da86dc0a4acb532015b5c0128c007d",
"transactionCount": 1,
"transactions": []
}
]
@baohua 麻烦看看
大家好，我们这边在1.0.0-beta上作压力测试的时候，发现orderer的内存到了128G之后，就挂掉了，机器的整个内存也就128G，有碰到过类似的问题吗？
@chenxuan 提交速度（并发量）是多少？
我就是一个线程去跑这个 @jimthematrix
你能把交易里的timestamp也打印出来吗？
Block和交易对象结构可以参照https://fabric-sdk-node.github.io/global.html#Block__anchor
可以
＝＝
@jimthematrix 麻烦看看邮件
请问这里的BatchTimeOut是指把交易打包成block的timeout吗？
Message Attachments
恩
这是在configtx.yaml里定义的。
哦，谢谢
Message Attachments
@guoger
我看起的peer里面是有的
Message Attachments
貌似哪里的配置的还是有点问题
@guoger 你的peer1.org0.example.com:这个peer的节点配置要修改成这样
peer1.org0.example.com:
container_name: peer1.org0.example.com
extends:
file: dc-peer-base.yml
service: peer-base
environment:
- CORE_PEER_ID=peer1.org0.example.com
- CORE_PEER_ADDRESS=peer1.org0.example.com:7051
- CORE_PEER_GOSSIP_EXTERNALENDPOINT=peer1.org0.example.com:7051
- CORE_PEER_LOCALMSPID=Org0MSP
volumes:
- /var/run/:/host/var/run/
- ./crypto-config/peerOrganizations/org0.example.com/peers/peer1.org0.example.com/msp:/etc/hyperledger/fabric/msp
- ./crypto-config/peerOrganizations/org0.example.com/peers/peer1.org0.example.com/tls:/etc/hyperledger/fabric/tls
ports:
- '7051'
- '7053'
volumes 配置错了
建议修改
Has joined the channel.
@chenxuan 貌似镜像里写错了。。我github上那个应该是ok的
在用fabric写智能合约的时候可以在合约里面维护一个自增的id吗？往world stat里面每查一条记录id都加1，如果这样的话并发请求的情况下，前一个请求的结果还没有commit，后面的请求拿到的自增id还是加1之前的值吧，有什么办法能维护一个自增id吗？
@chenxuan 哦不会
哦不对
看到了
多谢
没事 @guoger
for today's hackfest, and welcome for more to join!
Message Attachments
Message Attachments
Message Attachments
Message Attachments
Message Attachments
2017-06-19 08:55:06.814 UTC [chaincode] Launch -> ERRO 34f launchAndWaitForRegister failed Timeout expired while starting chaincode mycc:1.0(networkid:dev,peerid:peer0.org2.example.com,tx:f8f6d2fd32abcafee5dfb192be278394a48720f58104c3e640f0e1229ebeefa0)
实例化的时候超时了
2017-06-19 09:00:56.658 UTC [shim] userChaincodeStreamGetter -> ERRO 001 Error trying to connect to local peer: context deadline exceeded
Error starting Simple chaincode: Error trying to connect to local peer: context deadline exceeded
@jimthematrix
Error: Error endorsing chaincode: rpc error: code = Unknown desc = Timeout expired while starting chaincode mycc:1.0(networkid:dev,peerid:peer0.org2.example.com,tx:3bc87d2b28ad465eb7ffa91cd82022782e29e368cd5a8757fbb358c20067b0db)
2017-06-19 09:23:16.948 UTC [deliveryClient] StartDeliverForChannel -> DEBU 346 This peer will pass blocks from orderer service to other peers for channel mychannel
2017-06-19 09:23:16.951 UTC [deliveryClient] RequestBlocks -> DEBU 347 Starting deliver with block [1] for channel mychannel
2017-06-19 09:23:26.148 UTC [dockercontroller] deployImage -> DEBU 348 Created image: dev-peer0.org2.example.com-mycc-1.0
2017-06-19 09:23:26.148 UTC [dockercontroller] Start -> DEBU 349 start-recreated image successfully
2017-06-19 09:23:26.148 UTC [dockercontroller] createContainer -> DEBU 34a Create container: dev-peer0.org2.example.com-mycc-1.0
2017-06-19 09:23:26.250 UTC [dockercontroller] createContainer -> DEBU 34b Created container: dev-peer0.org2.example.com-mycc-1.0
2017-06-19 09:23:26.480 UTC [dockercontroller] Start -> DEBU 34c Started container dev-peer0.org2.example.com-mycc-1.0
2017-06-19 09:23:26.480 UTC [container] unlockContainer -> DEBU 34d container lock deleted(dev-peer0.org2.example.com-mycc-1.0)
2017-06-19 09:28:26.480 UTC [chaincode] launchAndWaitForRegister -> DEBU 34e stopping due to error while launching Timeout expired while starting chaincode mycc:1.0(networkid:dev,peerid:peer0.org2.example.com,tx:3bc87d2b28ad465eb7ffa91cd82022782e29e368cd5a8757fbb358c20067b0db)
2017-06-19 09:28:26.480 UTC [container] lockContainer -> DEBU 34f waiting for container(dev-peer0.org2.example.com-mycc-1.0) lock
2017-06-19 09:28:26.480 UTC [container] lockContainer -> DEBU 350 got container (dev-peer0.org2.example.com-mycc-1.0) lock
2017-06-19 09:28:26.481 UTC [dockercontroller] stopInternal -> DEBU 351 Stop container dev-peer0.org2.example.com-mycc-1.0(Container not running: dev-peer0.org2.example.com-mycc-1.0)
2017-06-19 09:28:26.482 UTC [dockercontroller] stopInternal -> DEBU 352 Kill container dev-peer0.org2.example.com-mycc-1.0 (API error (500): {"message":"Cannot kill container dev-peer0.org2.example.com-mycc-1.0: Container e09e80a1eadd9012e31d9ddac43ae82fa032dda0b9b6305e8e0cefb73e730e4b is not running"}
)
2017-06-19 09:28:26.506 UTC [dockercontroller] stopInternal -> DEBU 353 Removed container dev-peer0.org2.example.com-mycc-1.0
2017-06-19 09:28:26.506 UTC [container] unlockContainer -> DEBU 354 container lock deleted(dev-peer0.org2.example.com-mycc-1.0)
2017-06-19 09:28:26.506 UTC [chaincode] Launch -> ERRO 355 launchAndWaitForRegister failed Timeout expired while starting chaincode mycc:1.0(networkid:dev,peerid:peer0.org2.example.com,tx:3bc87d2b28ad465eb7ffa91cd82022782e29e368cd5a8757fbb358c20067b0db)
2017-06-19 09:28:26.506 UTC [endorser] callChaincode -> DEBU 356 Exit
2017-06-19 09:28:26.506 UTC [endorser] simulateProposal -> ERRO 357 failed to invoke chaincode name:"lscc" on transaction 3bc87d2b28ad465eb7ffa91cd82022782e29e368cd5a8757fbb358c20067b0db, error: Timeout expired while starting chaincode mycc:1.0(networkid:dev,peerid:peer0.org2.example.com,tx:3bc87d2b28ad465eb7ffa91cd82022782e29e368cd5a8757fbb358c20067b0db)
2017-06-19 09:28:26.506 UTC [endorser] simulateProposal -> DEBU 358 Exit
2017-06-19 09:28:26.506 UTC [lockbasedtxmgr] Done -> DEBU 359 Done with transaction simulation / query execution [5ae9a232-02c0-43b6-b773-13d71f7f60bb]
2017-06-19 09:28:26.506 UTC [endorser] ProcessProposal -> DEBU 35a Exit
- CORE_PEER_ADDRESS=peer1.org0.example.com:7051 如果实在不同的自己上部署应该是怎么配置IP 能不能举一个例子啊?
为什么环境变量里面的端口号都是docker内部的端口号 如果要在真实的环境下部署 这里的core_peer_address 是不是就是宿主机的IP+外部端口号
@baohua
@guoger
take a lokk
take a look
Dear all, we will have group meeting at 10AM this Wednesday morning, pls help update the agenda/attendee at https://wiki.hyperledger.org/groups/twgc/meeting/2017-06-21, thanks!
xuan, can i have ur steps to repeat the problem?
ok
我使用是一个orderer基于kafka de
的
仅仅只是修改了这个一个地方
首先可以确认的是network启动是没有问题
但是我去e2e的时候
实例化chaincode的时候就一直不动了
echo "Instantiating chaincode on org2/peer2..."
instantiateChaincode 2
也就是这个方法
我看到我的cc容器是启动了的
但是又退出了
然后我看了一下容器的log
就是这个
请问如果container已经运行了，怎样通过chaincode动态的向channel里添加org和peer？
@baohua
so u're using the latest master branch code and following the e2e script?
yes
2017-06-19 10:43:42.893 UTC [container] lockContainer -> DEBU 33f waiting for container(dev-peer0.org2.example.com-mycc-1.0) lock
2017-06-19 10:43:42.893 UTC [container] lockContainer -> DEBU 340 got container (dev-peer0.org2.example.com-mycc-1.0) lock
2017-06-19 10:43:42.893 UTC [dockercontroller] Start -> DEBU 341 Cleanup container dev-peer0.org2.example.com-mycc-1.0
2017-06-19 10:43:42.894 UTC [dockercontroller] stopInternal -> DEBU 342 Stop container dev-peer0.org2.example.com-mycc-1.0(No such container: dev-peer0.org2.example.com-mycc-1.0)
2017-06-19 10:43:42.894 UTC [dockercontroller] stopInternal -> DEBU 343 Kill container dev-peer0.org2.example.com-mycc-1.0 (No such container: dev-peer0.org2.example.com-mycc-1.0)
2017-06-19 10:43:42.895 UTC [dockercontroller] stopInternal -> DEBU 344 Remove container dev-peer0.org2.example.com-mycc-1.0 (No such container: dev-peer0.org2.example.com-mycc-1.0)
2017-06-19 10:43:42.895 UTC [dockercontroller] Start -> DEBU 345 Start container dev-peer0.org2.example.com-mycc-1.0
2017-06-19 10:43:42.895 UTC [dockercontroller] getDockerHostConfig -> DEBU 346 docker container hostconfig NetworkMode: linuxamd64_default
2017-06-19 10:43:42.896 UTC [dockercontroller] createContainer -> DEBU 347 Create container: dev-peer0.org2.example.com-mycc-1.0
2017-06-19 10:43:42.897 UTC [dockercontroller] Start -> DEBU 348 start-could not find image ...attempt to recreate image no such image
2017-06-19 10:43:42.898 UTC [chaincode-platform] generateDockerfile -> DEBU 349
FROM hyperledger/fabric-baseos:x86_64-0.3.1
ADD binpackage.tar /usr/local/bin
LABEL org.hyperledger.fabric.chaincode.id.name="mycc" \
org.hyperledger.fabric.chaincode.id.version="1.0" \
org.hyperledger.fabric.chaincode.type="GOLANG" \
org.hyperledger.fabric.version="1.0.0-beta" \
org.hyperledger.fabric.base.version="0.3.1"
ENV CORE_CHAINCODE_BUILDLEVEL=1.0.0-beta
ENV CORE_PEER_TLS_ROOTCERT_FILE=/etc/hyperledger/fabric/peer.crt
COPY peer.crt /etc/hyperledger/fabric/peer.crt
2017-06-19 10:43:42.899 UTC [util] DockerBuild -> DEBU 34a Attempting build with image hyperledger/fabric-ccenv:x86_64-1.0.0-beta
2017-06-19 10:43:44.497 UTC [deliveryClient] StartDeliverForChannel -> DEBU 34b This peer will pass blocks from orderer service to other peers for channel mychannel
2017-06-19 10:43:44.503 UTC [deliveryClient] RequestBlocks -> DEBU 34c Starting deliver with block [1] for channel mychannel
2017-06-19 10:43:54.783 UTC [dockercontroller] deployImage -> DEBU 34d Created image: dev-peer0.org2.example.com-mycc-1.0
2017-06-19 10:43:54.783 UTC [dockercontroller] Start -> DEBU 34e start-recreated image successfully
正常的启动是
这样的
我解决了
CORE_VM_DOCKER_HOSTCONFIG_NETWORKMODE @baohua 你能解释一下这个是干嘛的吗
？
@guoger
this part will be set as the config for the new created chaincode container, to indicate which network type it should use. u can see the network mode in docker for reference.
Has joined the channel.
@baohua 请问如下图所示（这是官方e2e例子docker-compose-cli.yaml文件里截取的），这一堆的environment设置为什么只针对peer0.org1.example.com，那其他peer不需要设置吗？
Message Attachments
by default, this uses cli as to operate for peer0, feel free to update accordingly
那如果我进入这个cli容器能否向同一个org的其他peer或者其他org的peer部署chaincode呢？
@tolak 可以的 cli中操作其它peer时会根据相应peer对环境变量重新设置
为什么环境变量里面的端口号都是docker内部的端口号 如果要在真实的环境下部署 这里的core_peer_address 是不是就是宿主机的IP+外部端口号
yeap, should map out
同一台机器container是可以相互访问的
所以想知道 在不同的机子上怎么配置
不同的机器可以使用docker swarm部署 创建 overlay network
https://github.com/ChoiSD/hyperledger_on_swarm
Error: Got unexpected status: SERVICE_UNAVAILABLE
Usage:
peer channel create [flags]
Global Flags:
-b, --blockpath string Path to file containing genesis block
--cafile string Path to file containing PEM-encoded trusted certificate(s) for the ordering endpoint
-c, --chain string In case of a newChain command, the chain ID to create.
-f, --file string Configuration transaction file generated by a tool such as configtxgen for submitting to orderer
--logging-level string Default logging level and overrides, see core.yaml for full syntax
-o, --orderer string Ordering service endpoint
--test.coverprofile string Done (default "coverage.cov")
-t, --timeout int Channel creation timeout (default 5)
--tls Use TLS when communicating with the orderer endpoint
-v, --version Display current version of fabric peer server
!!!!!!!!!!!!!!! Channel creation failed !!!!!!!!!!!!!!!!
================== ERROR !!! FAILED to execute End-2-End Scenario ==================
@baohua
@jimthematrix
please take a look
[ ](https://chat.hyperledger.org/channel/twg-china?msg=iFjFkuByDi5JiKHzT) @yahtoo 谢谢 我看看
[ ](https://chat.hyperledger.org/channel/twg-china?msg=iFjFkuByDi5JiKHzT) @yahtoo 是确定不能直接用外网IP+外部接口对吧
Has joined the channel.
Has joined the channel.
Has joined the channel.
Message Attachments
北京的小伙伴好安逸，可以参加这些活动
100000 条交易 10 thread 61个交易是有效的
正常吗？
2017-06-20 11:59:57.498 UTC [gossip/comm] GossipStream -> ERRO 19d Authentication failed: Peer Identity [0a 07 4f 72 67 31 4d 53 50 12 d5 06 2d 2d 2d 2d 2d 42 45 47 49 4e 20 2d 2d 2d 2d 2d 0a 4d 49 49 43 57 54 43 43 41 67 43 67 41 77 49 42 41 67 49 51 56 53 5a 63 53 6d 47 77 74 77 2f 79 56 32 68 43 79 62 39 78 47 6a 41 4b 42 67 67 71 68 6b 6a 4f 50 51 51 44 41 6a 42 7a 4d 51 73 77 0a 43 51 59 44 56 51 51 47 45 77 4a 56 55 7a 45 54 4d 42 45 47 41 31 55 45 43 42 4d 4b 51 32 46 73 61 57 5a 76 63 6d 35 70 59 54 45 57 4d 42 51 47 41 31 55 45 42 78 4d 4e 55 32 46 75 49 45 5a 79 0a 59 57 35 6a 61 58 4e 6a 62 7a 45 5a 4d 42 63 47 41 31 55 45 43 68 4d 51 62 33 4a 6e 4d 53 35 6c 65 47 46 74 63 47 78 6c 4c 6d 4e 76 62 54 45 63 4d 42 6f 47 41 31 55 45 41 78 4d 54 59 32 45 75 0a 62 33 4a 6e 4d 53 35 6c 65 47 46 74 63 47 78 6c 4c 6d 4e 76 62 54 41 65 46 77 30 78 4e 7a 41 32 4d 54 55 77 4e 6a 51 35 4e 54 6c 61 46 77 30 79 4e 7a 41 32 4d 54 4d 77 4e 6a 51 35 4e 54 6c 61 0a 4d 46 73 78 43 7a 41 4a 42 67 4e 56 42 41 59 54 41 6c 56 54 4d 52 4d 77 45 51 59 44 56 51 51 49 45 77 70 44 59 57 78 70 5a 6d 39 79 62 6d 6c 68 4d 52 59 77 46 41 59 44 56 51 51 48 45 77 31 54 0a 59 57 34 67 52 6e 4a 68 62 6d 4e 70 63 32 4e 76 4d 52 38 77 48 51 59 44 56 51 51 44 45 78 5a 77 5a 57 56 79 4d 53 35 76 63 6d 63 78 4c 6d 56 34 59 57 31 77 62 47 55 75 59 32 39 74 4d 46 6b 77 0a 45 77 59 48 4b 6f 5a 49 7a 6a 30 43 41 51 59 49 4b 6f 5a 49 7a 6a 30 44 41 51 63 44 51 67 41 45 6b 41 48 52 78 49 37 69 2f 72 61 6e 44 54 46 62 69 65 2f 58 65 32 75 33 4a 41 76 75 65 4e 71 69 0a 69 55 51 45 62 33 45 46 58 37 41 55 55 6e 6f 66 74 67 79 30 31 46 38 62 57 39 33 65 55 73 43 62 51 6f 47 46 45 65 72 49 59 42 37 6c 74 4a 34 44 48 78 52 64 4c 36 4f 42 6a 54 43 42 69 6a 41 4f 0a 42 67 4e 56 48 51 38 42 41 66 38 45 42 41 4d 43 42 61 41 77 45 77 59 44 56 52 30 6c 42 41 77 77 43 67 59 49 4b 77 59 42 42 51 55 48 41 77 45 77 44 41 59 44 56 52 30 54 41 51 48 2f 42 41 49 77 0a 41 44 41 72 42 67 4e 56 48 53 4d 45 4a 44 41 69 67 43 44 38 39 30 55 32 55 59 76 49 73 44 4c 73 71 68 6f 50 5a 36 43 54 44 4c 39 38 63 64 56 4c 38 66 76 49 4e 34 38 6c 63 4b 71 33 55 44 41 6f 0a 42 67 4e 56 48 52 45 45 49 54 41 66 67 68 5a 77 5a 57 56 79 4d 53 35 76 63 6d 63 78 4c 6d 56 34 59 57 31 77 62 47 55 75 59 32 39 74 67 67 56 77 5a 57 56 79 4d 54 41 4b 42 67 67 71 68 6b 6a 4f 0a 50 51 51 44 41 67 4e 48 41 44 42 45 41 69 42 6c 33 56 4a 70 46 49 53 7a 73 5a 58 64 32 6f 2f 53 58 79 6a 33 56 74 7a 43 58 70 69 4a 6a 79 49 49 53 6d 54 6f 52 38 61 39 59 41 49 67 63 4b 59 45 0a 4f 66 74 41 41 50 2f 68 58 32 7a 6d 45 57 73 44 41 66 39 39 7a 5a 4e 73 2f 54 30 6e 59 6b 2f 74 72 71 66 4d 67 70 4d 3d 0a 2d 2d 2d 2d 2d 45 4e 44 20 2d 2d 2d 2d 2d 0a] cannot be validated. No MSP found able to do that.
@baohua
接着SERVICE_UNAVAILABLE
peer0.org1.example.com的log
2017-06-20 12:06:04.206 UTC [gossip/comm] authenticateRemotePeer -> WARN 1ba Identity store rejected 172.16.10.211:33996 : Peer Identity [0a 07 4f 72 67 31 4d 53 50 12 d5 06 2d 2d 2d 2d 2d 42 45 47 49 4e 20 2d 2d 2d 2d 2d 0a 4d 49 49 43 57 54 43 43 41 67 43 67 41 77 49 42 41 67 49 51 56 53 5a 63 53 6d 47 77 74 77 2f 79 56 32 68 43 79 62 39 78 47 6a 41 4b 42 67 67 71 68 6b 6a 4f 50 51 51 44 41 6a 42 7a 4d 51 73 77 0a 43 51 59 44 56 51 51 47 45 77 4a 56 55 7a 45 54 4d 42 45 47 41 31 55 45 43 42 4d 4b 51 32 46 73 61 57 5a 76 63 6d 35 70 59 54 45 57 4d 42 51 47 41 31 55 45 42 78 4d 4e 55 32 46 75 49 45 5a 79 0a 59 57 35 6a 61 58 4e 6a 62 7a 45 5a 4d 42 63 47 41 31 55 45 43 68 4d 51 62 33 4a 6e 4d 53 35 6c 65 47 46 74 63 47 78 6c 4c 6d 4e 76 62 54 45 63 4d 42 6f 47 41 31 55 45 41 78 4d 54 59 32 45 75 0a 62 33 4a 6e 4d 53 35 6c 65 47 46 74 63 47 78 6c 4c 6d 4e 76 62 54 41 65 46 77 30 78 4e 7a 41 32 4d 54 55 77 4e 6a 51 35 4e 54 6c 61 46 77 30 79 4e 7a 41 32 4d 54 4d 77 4e 6a 51 35 4e 54 6c 61 0a 4d 46 73 78 43 7a 41 4a 42 67 4e 56 42 41 59 54 41 6c 56 54 4d 52 4d 77 45 51 59 44 56 51 51 49 45 77 70 44 59 57 78 70 5a 6d 39 79 62 6d 6c 68 4d 52 59 77 46 41 59 44 56 51 51 48 45 77 31 54 0a 59 57 34 67 52 6e 4a 68 62 6d 4e 70 63 32 4e 76 4d 52 38 77 48 51 59 44 56 51 51 44 45 78 5a 77 5a 57 56 79 4d 53 35 76 63 6d 63 78 4c 6d 56 34 59 57 31 77 62 47 55 75 59 32 39 74 4d 46 6b 77 0a 45 77 59 48 4b 6f 5a 49 7a 6a 30 43 41 51 59 49 4b 6f 5a 49 7a 6a 30 44 41 51 63 44 51 67 41 45 6b 41 48 52 78 49 37 69 2f 72 61 6e 44 54 46 62 69 65 2f 58 65 32 75 33 4a 41 76 75 65 4e 71 69 0a 69 55 51 45 62 33 45 46 58 37 41 55 55 6e 6f 66 74 67 79 30 31 46 38 62 57 39 33 65 55 73 43 62 51 6f 47 46 45 65 72 49 59 42 37 6c 74 4a 34 44 48 78 52 64 4c 36 4f 42 6a 54 43 42 69 6a 41 4f 0a 42 67 4e 56 48 51 38 42 41 66 38 45 42 41 4d 43 42 61 41 77 45 77 59 44 56 52 30 6c 42 41 77 77 43 67 59 49 4b 77 59 42 42 51 55 48 41 77 45 77 44 41 59 44 56 52 30 54 41 51 48 2f 42 41 49 77 0a 41 44 41 72 42 67 4e 56 48 53 4d 45 4a 44 41 69 67 43 44 38 39 30 55 32 55 59 76 49 73 44 4c 73 71 68 6f 50 5a 36 43 54 44 4c 39 38 63 64 56 4c 38 66 76 49 4e 34 38 6c 63 4b 71 33 55 44 41 6f 0a 42 67 4e 56 48 52 45 45 49 54 41 66 67 68 5a 77 5a 57 56 79 4d 53 35 76 63 6d 63 78 4c 6d 56 34 59 57 31 77 62 47 55 75 59 32 39 74 67 67 56 77 5a 57 56 79 4d 54 41 4b 42 67 67 71 68 6b 6a 4f 0a 50 51 51 44 41 67 4e 48 41 44 42 45 41 69 42 6c 33 56 4a 70 46 49 53 7a 73 5a 58 64 32 6f 2f 53 58 79 6a 33 56 74 7a 43 58 70 69 4a 6a 79 49 49 53 6d 54 6f 52 38 61 39 59 41 49 67 63 4b 59 45 0a 4f 66 74 41 41 50 2f 68 58 32 7a 6d 45 57 73 44 41 66 39 39 7a 5a 4e 73 2f 54 30 6e 59 6b 2f 74 72 71 66 4d 67 70 4d 3d 0a 2d 2d 2d 2d 2d 45 4e 44 20 2d 2d 2d 2d 2d 0a] cannot be validated. No MSP found able to do that.
我的ip明明是172.16.10.210
怎么变成了172.16.10.211
@baohua :thumbsup: 看到武城宫也去了，Iroha有发布什么新进展吗？
期待cello composer
介绍了架构和一些应用案例 内容比较丰富 回头会把 slides link 放到 agenda wikipage
@jimthematrix
Today's meeting we will try to use the new uberconf system, while the legacy call number is still available (deprecating soon).
https://wiki.hyperledger.org/groups/twgc/meeting/2017-06-21?&#agenda
@yahtoo 这个docker swarm的可以么
@CarlXK 使用docker swarm 可以部署
@yahtoo 好, 我试试, 谢谢!
@baohua @jimthematrix cauthdsl模块的作用是什么?
支持策略实现的包 policy相关的基础功能都在里面实现
@baohua 多谢
问个问题：World State中的数据缺省是加密的吗？还是需要在Chaincode代码中自己用加密算法加密？
@baohua 在创建channel时出现这个错误“Error: Got unexpected status: BAD_REQUEST” 。 这可能时什么原因造成的呢？我是拿的fabric/sample/release/linux-amd64添加了自己的一些东西后执行的。
但从这个信息上不好判断 只能猜测是最后发出的请求不合法
单从这个信息上不好判断 猜测是发出的请求不合法
如果我使用generateArtifacts.sh 生成好的CA信息启动网络。我想再增加一个节点进来。怎么操作？
所有peer和org的topology 都是在crypto-config.yaml 和 configtx.yaml里定义的，所以你应该从这里入手改。然后对应的再改generateArtifacts.sh
在container里动态新增peer不知道行不行
讨论个问题，hackfest大会的时候忘了哪位speaker说过，现在kafka只是做fault tolerant而没有consensus，如果没有consensus怎么保证数据不被恶意篡改
还是说现在干脆不考虑consensus了
Has joined the channel.
部署example04遇到找不到github.com/hyperledger/fabric/common/util包的错误，请问如何解决，自己写的cc，import别的包也是找不到。
但是为什么example02的shim和proto/peer就能找到呢？进cli容器里找了一下，也没看到goroot或gopath下有这两个包啊。所以有人能帮忙解释下cc在intall的时候import的包是从哪里获取的吗？谢谢
Has joined the channel.
@baohua 现在v1.0 beta上有没有那些现成的stress test 可以跑的呢？
想问下，foo.tx 这个用来创建channel 的配置文件，是怎么写的。如果我要自己写一个channel的tx配置文件，要怎么写的。
Has joined the channel.
@aaronzheng 这里有个tx config file语法简介。你也可以参照example下各例程的config.tx文件写。
Message Attachments
sorry，是configtx.yaml文件
Message Attachments
@baohua 上图是generateArtifacts.sh中的一段，请问replacePrivateKey()有和作用？
@baohua 上图是generateArtifacts.sh中的一段，请问replacePrivateKey()有何作用？
另外其中对docker-compose-e2e.yaml的操作是必须的吗？这个文件里的定义有何作用？
seems it's to update the right private key file into the docker-compose-e2e.yaml, which helps boot up the fabric network.
大家在instantitate chaincode时有遇到过这个错误吗：Error: Error endorsing chaincode: rpc error: code = Unknown desc = Timeout expired while starting chaincode peer0-assetmanager-cc:1.0(networkid:dev,peerid:peer0.assetManagerOrg.example.com,tx:0c062ca88239151f7a7f09517dc9c7b99b11618a84f188e8b107b8061826b328)
stackoverflow上有人使用官方例程也遇到过同样的问题：https://stackoverflow.com/questions/44325840/hyperledger-fabric-1-0-alpha2-timeout-expired-while-starting-chaincode。
可以看一下你的image列表吗？看起来是合约chaincode启动失败
@tolak
Message Attachments
Message Attachments
@jiangyaoguo 分别是images 和 container的截图，麻烦帮忙看下，谢谢了哈！
是不是在peer0.assetManagerOrg上没有安装chaincode？ @tolak
是安装成功的哈
至少安装过程没报错，不过有命令可以看是否安装成功了吗？
2017-06-26 10:20:07,481:INFO http-nio-8080-exec-2 (Util.java:39) - Created channel channel
2017-06-26 10:20:07,621:INFO http-nio-8080-exec-2 (Channel.java:413) - Peer peer1.org1.example.com joined into channel channel
2017-06-26 10:20:07,622:INFO http-nio-8080-exec-2 (Util.java:39) - Peer peer1.org1.example.com joined channle channel
2017-06-26 10:20:07,648:ERROR http-nio-8080-exec-2 (Channel.java:2138) - Sending proposal to peer0.org1.example.com failed because of gRPC failure=Status{code=UNKNOWN, description=chaincode error (status: 500, message: Cannot create ledger from genesis block, due to LedgerID already exists), cause=null}
java.lang.Exception: io.grpc.StatusRuntimeException: UNKNOWN: chaincode error (status: 500, message: Cannot create ledger from genesis block, due to LedgerID already exists)
@baohua
take a look
@guoger
Has joined the channel.
如果想增加一个组织(org)怎么操作?
有人在做吗
大家一起搞一些
有人在搞composer嘛
想搞什么？
Compiling all doT templates...
Compiling HyperlegerExplorer.jst to file
{ Error: connect ECONNREFUSED 127.0.0.1:7050
at Object.exports._errnoException (util.js:1018:11)
at exports._exceptionWithHostPort (util.js:1041:20)
at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1086:14)
code: 'ECONNREFUSED',
errno: 'ECONNREFUSED',
syscall: 'connect',
address: '127.0.0.1',
port: 7050 }
@baohua
take a look
动态添加组织
Has joined the channel.
想问一下，我现在把chaincode都install和instantiate了，我进入了docker下的chaincode，我想问要怎么查看这个容器chaincode里面的内容？例如我想验证一下 这个chaincode容器和我安装的chaincode是一致的。
在你的代码里添加个函数专门打印你的chaincode的名字
composer identity issue -p MyProfile -n 'carauction-network' -i ChaiAdmin -s abcd -u chai4@gmail.com -a "org.acme.vehicle.auction.Member#chai4@gmail.com"
Error: fabric-ca request register failed with errors [[{"code":400,"message":"Authorization failure"}]]
Command failed.
谁用过composer
我这个报错大家见过没
各位，是不是要向fabric提交一个patch，都得先在JIRA上创建一个issue？
@chenxuan BE does not support fabric 1.0 yet. Cello will support fabric 1.0 soon.
@baohua ok
@liuwenliang0632 静态添加只需要修改configtx.yaml配置文件，系统运行时动态添加可以参考 fabric/example/configtxupdate/reconfig_membership
@yahtoo 3q
@baohua @jimthematrix 使用example/configtxupdate/reconfig_membership 基于e2e_cli动态添加org，以下为错误信息
Message Attachments
channel动态添加org报错
怎么还要启动端口configtxupdate.怎么使用？
里面有个readme
大家编译fabric源码有没有报错，我执行make gotool时都会报错，单元测试等也会。看上去是网络原因，你们是怎么解决的？
你直接去下载那个玩意 放到某一个目录就可以了
但是有时候（比如提交patch之前）需要编译源码，所以就恼火了
有人在看composer吗
https://hyperledger.github.io/composer/integrating/call-out.html
这一页的
搞错了
https://hyperledger.github.io/composer/integrating/enabling-rest-authentication.html
The REST server can be optionally configured to authenticate clients. Once authenticated, a client can add Blockchain identities to a wallet. The wallet is private to that client, and is not accessible to other clients. When a client makes a request to the REST server, a Blockchain identity in the clients wallet is used to digitally sign all transactions made by that client.
Please note that this feature requires that clients trust the REST server. This trust is required because this feature requires that the REST server stores the clients Blockchain identities, including the private keys. Therefore, it is strongly recommended that clients only use REST servers that are managed by a trusted party, such as an administrator within their organization.
我咋觉得这些话有些矛盾啊
Once authenticated, a client can add Blockchain identities to a wallet. 一旦通过认证 一个客户端就会添加区块链身份到钱包中
如果身份是私钥和证书的话 这个私钥难道不是客户端自己生成吗
This trust is required because this feature requires that the REST server stores the clients Blockchain identities, including the private keys
这句话又说rest server来保存客户端的区块链身份 包括私钥
现在按照API doc写的rest server还不存在吧？？？
@baoyangc 按照我理解，private key确实不是客户端生成的，而是服务端按照配置预先分配了
用户的私钥和公钥都归他管
用户的生成本身就在服务端做的，感觉客户只做了登陆的动作
composer rest-server把公钥和私钥存放到内存里了
？
我感觉是是crypto material那些地方
composer identity issue -n 'digitalproperty-network' -i admin -s Xurw3yU9zI0l -u maeid1 -a "net.biz.digitalPropertyNetwork.Person#mae@biznet.org"
这个有人执行成功吗
问一下，kafka模式下启动多个orderer，测试下来只有一个orderer能够create channel。这样正常吗？
http://hyperledger-fabric.readthedocs.io/en/latest/txflow.html?highlight=transaction{The MSP is a peer component that allows them to verify transaction requests arriving from clients and to sign transaction results(endorsements). The *Writing policy is defined at channel creation time, and determines which user is entitled to submit a transaction to that channel.}*
这句话现在还适用吗
channel在创建时在哪配置那个user可以提交交易了？
你可以关注下configtx 和 crypto-config.yaml这两个文件。
看过了
没发现哪个是是
只有对anchorPeer的定义
没啥那个user做提交
感觉fabric没有user的概念吧，提交这些动作都是peer通过chaincode发起，再通过签名背书等一系列流程最后送到orderer peer那做排序。
有人遇到rc1 开发模式下 up时遇到http请求超时的错误吗
fabric现在对国密算法的支持，比如SM2，做的怎么样了，什么时候能有release出来
@zhangchao 正在计划中，您那已经有明确的需求了吗对这一块?
有，有银行客户明确提出要用sm2做链路加密
他们也是因为央行的强制要求
有时间表吗 @xixuejia
目前还没有明确的时间表，正在计划阶段
有人研究composer吗
composer的权限控制谁写过
``` "message": "error trying invoke chaincode. Error: chaincode error (status: 500, message: Error: Participant 'org.bqj.cn.BanquanjiaUser#chai1' does not have 'CREATE' access to resource 'org.bqj.cn.CopyrightPackageTransfer#d0b1b996-bd42-406a-a310-1be760c5f3a8')",```
碰到这样的错误
@here Dear all, we will have group meeting at 10AM this Wednesday morning, pls help update the agenda/attendee at https://wiki.hyperledger.org/groups/twgc/meeting/2017-07-05, thanks
想问一下，fabric 有备份和恢复的方案吗
is there an api to make a transaction with an identity file?
@baohua 现在BlockChainExplorer这个项目有继续在维护么
@CarlXK Not too many updates recently. Feel free to contact those project maintainers: https://github.com/hyperledger/blockchain-explorer/blob/master/MAINTAINERS.rst
Meeting will be start at 10AM, pls get familiar with our new conf tool: https://www.uberconference.com/hyperledger-community. Thanks!
Phone Number (Deprecate soon):
800-820-0027 (toll free)
400-821-0751 (caller paid)
Passcode: 71173794
听不到声音
@baohua @jimthematrix 现在fabric测试都是用bridge的网络, 可以用overlay么, 有没有用例
是担心overlay带来哪些方面的问题呢？
cello之前支持swarm，底下是overlay。功能上没有问题，但没有测试过性能。
就是想试试哈, 也没看到有用例, 那就自己改改试试看吧
哦 overlay应该不会带来太多问题
Has joined the channel.
https://github.com/litong01/fabric-deploy
this is the project we will be using to deploy fabric either on one node or multiple node. I am using flanneld overlay network. Take a look. If any of you have some script to test performance, I like to run your script against the network. Please let me know.
@baohua 杨老师，请问下在同一个通道里的节点如何做到节点之间的数据隐私问题，fabric 有这样的机制吗
@所有人 请问下在同一个通道里的节点如何做到节点之间的数据隐私问题，fabric 有这样的机制吗
@zhuxubin01 fabric目前没有这种机制，不过你可以看一下这两个未来的issue，提供了两种思路。https://jira.hyperledger.org/browse/FAB-1151 and https://jira.hyperledger.org/browse/FAB-5131
看哪个更符合你的需求
@jiangyaoguo 非常感谢 你发的这个正是我们想要解决的问题
Has joined the channel.
Has joined the channel.
Has joined the channel.
[shim] userChaincodeStreamGetter -> ERRO 001 Error trying to connect to local peer: context deadline exceeded
Error starting Simple chaincode: Error trying to connect to local peer: context deadline exceeded 有人遇到过这个问题么？
@ylsGit 貌似是你的在channel.tx里的 orderer address配置的不对
看错了.. 你是chaincode连不上peer?
看报错信息的意思是 chaincode与peer连接出的问题
哦，那可能是docker network配置的原因
是的啊，chaincode容器启动不起来，看其log显示改错
我猜也是，但docker network那几个选项我还没太明白。你清楚么？
`CORE_VM_DOCKER_HOSTCONFIG_NETWORKMODE=e2ecli_default` 看一下你的网络名字和所在目录对应不
`e2ecli` 是目录名字
文件目录？？
嗯，你是用docker-compose吧?
是啊
你的docker-compose yaml所在的目录
https://docs.docker.com/compose/networking/
好的
我试试，多谢
@xixuejia 果然可以，多谢:pray:
ca用户的密码有修改的办法没
目前来看ca的用户密码没法修改
一旦泄露 只能吊销用户啊
Has joined the channel.
@baoyangc 可以用ldap做Fabric-ca 的user registry, 这样可以通过ldap来改密码 http://hyperledger-fabric-ca.readthedocs.io/en/latest/users-guide.html#configuring-ldap
thanks
@baohua 请教个问题, 如果用swarm + compose file, 那还能继续用orderer.example.com 这种本地域名么
比如两台机器, 一个跑orderer和ca , 一台跑peer, 这样能玩? 还是说只能用ip的方式
@CarlXK domain name does not necessarily reflect the machine name.
as long as the orderer and peer can reach each other.
sorry, the question was to @baohua. please do confirm.
@tongli 没太明白你说的意思, 域名跟机器名字没有关系, order和peer在不同机器上面用域名还是可以互相访问?
还是说在dns或者hosts里面配置了然后互通?
yes.
https://github.com/litong01/fabric-deploy
this is the project I have been working on,
we will be using this for multi node deployment
you can choose to have one node (everything runs on one node) or multiple nodes (things will spread out).
in this project, I defined things, the domain name does not have to match the machine name.
also, peers, orderers all eventually are containers,
they may have different IP addresses.
which will be very true when you use overlay network like the project does.
sorry for doing it in English, way too slow for me to input Chinese. (it is not that I do not like Chinese).
@tongli many thanks , i will try it ~
sure. the project does a lot such as provisioning VM from OpenStack cloud.
soon, I will add provisioning VM from AWS.
and plan to add provisioning from VirtualBox as well.
so that you can start really from scratch.
currently working on k8s setup, so that fabric runs on k8s.
all these will come very soon.
if you like to contribute, that will be even better.
@CarlXK thanks @tongli 's help answering. if u are using container, then the local name is actually inside the container. to reach each other, need to have the dns records.
https://github.com/litong01/fabric-deploy
that project provides that
One case need to take care is when u enable tls, then there may be some name checking, to match the cert record.
it sets up dns services and registrator.
containers automatically get registered in the dns services and all can be referenced by name.
@chawlanikhil24 great, chaw is also working on the k8s deployment.
Has joined the channel.
@chawlanikhil24 if we can work on the same project, that will be nice.
we would like to use same tool and same project.
not so many different and duplicate effort.
Hi everyone, @here
sorry for being a bit late
@tongli , Yupp, I do like to work with you
@chawlanikhil24 awesome.
here is the link.
https://github.com/litong01/fabric-deploy
@tongli here is my work I've done so far!
https://github.com/chawlanikhil24/hyperledger-fabric-k8s/tree/master/fabric-1.0
I'll go through your work tonight
sure,sure
Please do a take a look at my work and let me know if you find any bugs and errors
please do come forward with them
:)
i was
probably pull few yaml files into mine to speed up the project.
such as this one . https://github.com/chawlanikhil24/hyperledger-fabric-k8s/blob/master/fabric-1.0/local/orderer.yaml
of course, files like this will be automatically generated.
need to use k8s policies to spread out the containers to multiple nodes.
@chawlanikhil24 :thumbsup:
我 分享 部分 fabric 的术语 https://mp.weixin.qq.com/s?__biz=MzI5MDQzMjgwOQ==&tempkey=NDmxZqq0fPxouPS9f4XwWJj3i0Md9tSiUllyRcmkVh%2Fdbtn73l6nbZGy%2F5WYpI8394yiQvPO2u573cuI4zhPO4k2i8JY9df2EPM6nAojmmc0teVO4q%2FabU3H%2BPCbtNDyQi0dQ9uiNigian%2Fp%2BkRXag%3D%3D&chksm=6c1eb3785b693a6e5aa91b8299f92ba04f4aec3bfaa72de92b212a20a84b84aa991e4c80d2ed#rd
@baohua 我最近准备提议 Apache RocketMQ 实现共识，kafka 在消息堆积太多，容易丢交易消息，在金融领域是没有办法忍受的。
nice
当初选kafka是因为它的性能比较好。rocketmq也比较成熟，但是性能应该不如kafka。
但社区是非常欢迎提各种新的plugin机制的。
性能差不多，因为之前在阿里我们的支付使用的 Apache RocketMQ ，主要是金融领域使用fabric 记录关键消息，消息是是不能丢失的。
啊 sorry 我看错了 我以为你说的是rabbitmq
欢迎提出啊，rocketmq相对比较年轻一些 但是有一些有趣的特性
@tongli , for now, I am using minikube + weavenet for developement
@tongli , for now, I am using minikube + weavenet for development
想问下，大家用leveldb什么客户端来查看数据的？
@chawlanikhil24 fabric-deploy project will deploy real k8s on top of a cloud such as OS, AWS, Azure.
weavenet can be an option but I am using flanneld.
canel is the future!
@baohua , for now, should I continue to weavenet
?
canel is a deployment tool.
mixes calico and flannel, I do not consider it as a real network plugin.
@chawlanikhil24 there're several network plugins for k8s, if it is supported, then u can feel free to use the one u feel most familiar with. I personally heard that the calico and flannel ones are popular. but u can have some evaluations.
[ ](https://chat.hyperledger.org/channel/twg-china?msg=yduqaAHrN2yq4ExpT) @qiushaoxi 备份恢复请参考：https://jira.hyperledger.org/browse/FAB-3017
[ ](https://chat.hyperledger.org/channel/twg-china?msg=ccEs9WFzdRjx9L5sS) @qiushaoxi 我也遇到类似的问题，2个orderer，orderer1上创建channel一直不成功，报的错误如下，在orderer2上就成功了。有人能解释原因下吗^_^？
``` 2017-07-11 08:13:31.292 UTC [orderer/common/broadcast] Handle -> WARN 104f Rejecting CONFIG_UPDATE because: Error authorizing update: Error validating DeltaSet: Policy for [Groups] /Channel/Application not satisfied: Failed to reach implicit threshold of 1 sub-policies, required 1 remaining ```
[ ](https://chat.hyperledger.org/channel/twg-china?msg=ccEs9WFzdRjx9L5sS) @qiushaoxi 我也遇到类似的问题，2个orderer，orderer1上创建channel一直不成功，报的错误如下，在orderer2上就成功了。有人能解释原因下吗^_^？
···2017-07-11 08:13:31.292 UTC [orderer/common/broadcast] Handle -> WARN 104f Rejecting CONFIG_UPDATE because: Error authorizing update: Error validating DeltaSet: Policy for [Groups] /Channel/Application not satisfied: Failed to reach implicit threshold of 1 sub-policies, required 1 remaining···
@HuangLijun that's because u need OrderMSP's Admin role to make config update tx.
feel free to ref https://github.com/yeasy/docker-compose-files/blob/master/hyperledger/1.0/docs/configtxlator-usage.md
Thank you @baohua , I will take a look.
Hi people!
I've created channel on Kubernetes
But now only one issue is persisting
Peers are not joining channel
``````
2017-07-13 06:24:32.985 UTC [msp] GetLocalMSP -> DEBU 005 Returning existing local MSP
2017-07-13 06:24:32.986 UTC [msp] GetDefaultSigningIdentity -> DEBU 006 Obtaining default signing identity
2017-07-13 06:24:32.986 UTC [channelCmd] InitCmdFactory -> INFO 007 Endorser and orderer connections initialized
2017-07-13 06:24:32.987 UTC [msp/identity] Sign -> DEBU 008 Sign: plaintext: 0A8A070A5C08011A0C08A0A49CCB0510...EDF55FE0E72A1A080A000A000A000A00
2017-07-13 06:24:32.987 UTC [msp/identity] Sign -> DEBU 009 Sign: digest: D5DE97D82BA14CDBEFF7AF3E1034194576B6AD908669FF1E413BC3CEAB6EADF9
Error: proposal failed (err: rpc error: code = Unimplemented desc = unknown service protos.Endorser)
``````
2017-07-13 06:24:32.985 UTC [msp] GetLocalMSP -> DEBU 005 Returning existing local MSP
2017-07-13 06:24:32.986 UTC [msp] GetDefaultSigningIdentity -> DEBU 006 Obtaining default signing identity
2017-07-13 06:24:32.986 UTC [channelCmd] InitCmdFactory -> INFO 007 Endorser and orderer connections initialized
2017-07-13 06:24:32.987 UTC [msp/identity] Sign -> DEBU 008 Sign: plaintext: 0A8A070A5C08011A0C08A0A49CCB0510...EDF55FE0E72A1A080A000A000A000A00
2017-07-13 06:24:32.987 UTC [msp/identity] Sign -> DEBU 009 Sign: digest: D5DE97D82BA14CDBEFF7AF3E1034194576B6AD908669FF1E413BC3CEAB6EADF9
Error: proposal failed (err: rpc error: code = Unimplemented desc = unknown service protos.Endorser)``
``````
2017-07-13 06:24:32.985 UTC [msp] GetLocalMSP -> DEBU 005 Returning existing local MSP
2017-07-13 06:24:32.986 UTC [msp] GetDefaultSigningIdentity -> DEBU 006 Obtaining default signing identity
2017-07-13 06:24:32.986 UTC [channelCmd] InitCmdFactory -> INFO 007 Endorser and orderer connections initialized
2017-07-13 06:24:32.987 UTC [msp/identity] Sign -> DEBU 008 Sign: plaintext: 0A8A070A5C08011A0C08A0A49CCB0510...EDF55FE0E72A1A080A000A000A000A00
2017-07-13 06:24:32.987 UTC [msp/identity] Sign -> DEBU 009 Sign: digest: D5DE97D82BA14CDBEFF7AF3E1034194576B6AD908669FF1E413BC3CEAB6EADF9
Error: proposal failed (err: rpc error: code = Unimplemented desc = unknown service protos.Endorser)```
can anyone help to debug this ?
我已经用swarm在多机器上面部署和创建channel成功了, 为什么选择用Kubernetes , 是因为更成熟? @chawlanikhil24
We are creating support for more orchestration tools like Kubernetes
Then the user will have choice to continue with swarm or k8s
@tongli can you help with this error ?
What error?
```
```
2017-07-13 06:24:32.985 UTC [msp] GetLocalMSP -> DEBU 005 Returning existing local MSP
2017-07-13 06:24:32.986 UTC [msp] GetDefaultSigningIdentity -> DEBU 006 Obtaining default signing identity
2017-07-13 06:24:32.986 UTC [channelCmd] InitCmdFactory -> INFO 007 Endorser and orderer connections initialized
2017-07-13 06:24:32.987 UTC [msp/identity] Sign -> DEBU 008 Sign: plaintext: 0A8A070A5C08011A0C08A0A49CCB0510...EDF55FE0E72A1A080A000A000A000A00
2017-07-13 06:24:32.987 UTC [msp/identity] Sign -> DEBU 009 Sign: digest: D5DE97D82BA14CDBEFF7AF3E1034194576B6AD908669FF1E413BC3CEAB6EADF9
Error: proposal failed (err: rpc error: code = Unimplemented desc = unknown service protos.Endorser)```
I've created channel successfully
but now my peer is not joining that channel !
Has left the channel.
https://github.com/litong01/fabric-deploy/blob/master/roles/deploy_compose/fabricsetup/templates/dochannel.j2#L22
@chawlanikhil24 take a look at that.
to join a channel, you will need to setup few env variables.
and make sure that these variables point to the right thing.
take a look at that section on how many env varilables that you need.
of course your env will be different from mine. but the idea is the same.
I am going through it!
and comparing it with my files
cello 启动报错。jinja2.exceptions.TemplateNotFound
cello 的文档太那个了
期待cello可以好用。
@tongli I've checked all the environment variables like twice or thrive
@tongli I've checked all the environment variables like twice or thrice
I've updated some stuff here, since I read the whole source code of Fabric-1.0
Please see , if this rings any bell
https://jira.hyperledger.org/browse/FAB-3250?focusedCommentId=28451&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-28451
@tongli
@chawlanikhil24 on k8s, I was able to create channel and join peers in.
The issue I have now is instantiate chaincode. I will look into that when comes back to work on Monday . Good weekend.
@tongli Thanks a lot for your response
:)
@chawlanikhil24 no problems at all. I will update you and share the link when I resolve the last issue
@tongli Thanks again for your help and your advance warning about the chaincode issue :) !
@here Dear all, we will have group meeting at 10AM this Wednesday morning, pls help update the agenda/attendee at https://wiki.hyperledger.org/groups/twgc/meeting/2017-07-19, thanks!
@chawlanikhil24 hi, after looking at the code and traffic when instantiate chaincode, I realized that the peer container tried to create chaincode container using docker command directly.
@chawlanikhil24 that does not work well in k8s env, since the dns service is not hooked up to the container created by the peer.
the right way of doing this is that the peer container need to have a way to be configured to setup dns when trying to use docker creating chaincode container or peer gets smart enough to know that it is running in k8s env and containers should be created within a pod rather than a bare container.
@chawlanikhil24 I think this problem needs to be resolved by the team who actually instantiate the chaincode container.
let me figure out who is doing that part of work.
@tongli , thank you so much for your efforts ! It really means a lot :)
I also think that the earlier problem that you had while trying to join peer to channel may due to the similar network issues in k8s env.
and one more thing I want to ask is that, how did you solve the tls handshake issue in K8s, since, I created services for each deployment , and that service name has a restriction, that we can't use "orderer.example.com"
correct, k8s does not allow dot in the service name, sigh!
I had to replace the dot with dash, replace('.', '-')
before I did anything.
I dynamically generate configtx.yaml file, so that I have control there.
But, config.yaml and crypto-config.yaml , works only in format of {hostname}.{domainname}
no.
well, not necessarily.
@tongli , You just said the right point !
let me show you mine
[ ](https://chat.hyperledger.org/channel/twg-china?msg=uDjkZneYNTkjDp6jq) @tongli Can you tell me how did you do that ?
Sure :)
```---
Organizations:
- &orga
Name: orga
ID: orga
MSPDir: /opt/gopath/bc1st/fabric/keyfiles/orga/msp
AdminPrincipal: Role.ADMIN
AnchorPeers:
- Host: peer1st-orga
Port: 7051
- &orgb
Name: orgb
ID: orgb
MSPDir: /opt/gopath/bc1st/fabric/keyfiles/orgb/msp
AdminPrincipal: Role.ADMIN
AnchorPeers:
- Host: peer1st-orgb
Port: 7051
- &orgc
Name: orgc
ID: orgc
MSPDir: /opt/gopath/bc1st/fabric/keyfiles/orgc/msp
AdminPrincipal: Role.ADMIN
- &orgd
Name: orgd
ID: orgd
MSPDir: /opt/gopath/bc1st/fabric/keyfiles/orgd/msp
AdminPrincipal: Role.ADMIN
Orderer: &OrdererDefaults
OrdererType: kafka
Addresses:
- orderer1st-orgc:7050
- orderer2nd-orgc:7050
- orderer1st-orgd:7050
- orderer2nd-orgd:7050
BatchTimeout: 2s
BatchSize:
MaxMessageCount: 10
AbsoluteMaxBytes: 98 MB
PreferredMaxBytes: 512 KB
Kafka:
Brokers:
- kafka1st:9092
- kafka2nd:9092
- kafka3rd:9092
Organizations:
- *orgc
- *orgd
Application: &ApplicationDefaults
Organizations:
- *orga
- *orgb
Profiles:
OrgChannel:
Consortium: FabricConsortium
Application:
<<: *ApplicationDefaults
OrdererGenesis:
Orderer:
<<: *OrdererDefaults
Consortiums:
FabricConsortium:
Organizations:
- *orga
- *orgb```
that file is generated based on this configuration.
https://github.com/litong01/fabric-deploy/blob/master/vars/bc1st.yml
starting here. https://github.com/litong01/fabric-deploy/blob/master/vars/bc1st.yml#L21
ohk ! I got it a bit!.. and who is running it? bash/python/golang ? or anything else ?
this project does everything.
https://github.com/litong01/fabric-deploy
I've been working on this since month and half ago.
You helped me a lot with this!. ..uptill now , I've to skip the tls handshakes to continue development
I'll figure this out in my kubernetes !
the project provision VMs on a cloud (OpenStack, AWS), then setup all the necessary env, then build, deploy fabric onto it.
I suggest that you start looking into the project that I work on.
I use AWS ... EC2 microinstance is well enough ?
we do not want many duplicate effort.
no.
I had a look through you code, but didn't deploy it !
microinstance is too small.
then a medium instance ?
I tried it and it blows up.
you probably need 4gb of memory at least and 20 GB of diskspace
smaller than that, It may not work.
when you get k8s on these nodes, it asks for a lot.
duplicate effort is really bad.
in that case, I'll deploy a VM on my bare-metal machine!
got 12GB of RAM on my machine !
sounds good?
?
so you will use virtualbox to provision few VMs on your machine?
then setup things?
umm... I know ! bit tideous !
I'll do whatever best I can do at my end to deploy !
and will share the progress
@chawlanikhil24 please look at the comments that I added to this https://jira.hyperledger.org/browse/FAB-3339
请问目前fabric只能合约有没有event机制，比如：我在nodejs这一端监听一个智能合约的事件，只能合约触发时能够异步通知nodejs这边
请问目前fabric智能合约有没有event机制，比如：我在nodejs这一端监听一个智能合约的事件，智能合约触发时能够异步通知nodejs这边
@tongli , yupp I had a look at your comment!.. Can we also do an experiment, like running a pod which further deploy a docker container ? I guess then we could verify it ... Nginx container will be best to check!
I just added nginx container as dns forwarder.
you can look at the latest patch set.
nginx dns forwarder, as in ingress ?
but still have some issues instantiate chaincode.
well, docker can only be configured to use dns IP address, not a port. the port has to be at 53.
k8s dns services can not run at that port unless I set up the k8s service node port range to be really low, which I do not want to do.
so I run nginx container at port 53.
so that new docker containers can point to the dns server, with that hack, containers can figure out the IPs. but still connection broken.
at this point, I am not sure what else can be done.
My ideas was,
client -> service proxy -> pod running nginx container -> nginxcontainer running Inside POD
nginx container can not run inside a pod.
I do not think that will work.
have you tried ? I never tried it yet !
you will still have to expose the port 53 somewhere.
container running inside a pod needs a service to expose its port.
exactly, i'll expose, port to 10000 of POD, and service will expose to Nodeport 32000
services by default can only use the port between 30000-325xx
Gimme, few minutes!.. Let me try this !
I do not want to expand that range to include 53
that is why I said earlier running nginx inside a pod won't work.
SO you want the NodePort or ClusterIP to be 53
if you want to try, you need to run it as a bare container.
no clusterIP does not matter.
NodePort matters, but you can not set it to 53 for above said reasons.
nodePort has to be in the service node port range which is 30000-325xx.
do not remember the upper number.
exactly, infact for minikube it is 32000
yeah. so the best solution is that chaincode container gets created using k8s apis.
that way everything will work.
if peer container creates chaincode container directly using docker api, that is bad in k8s env.
ohk ! Now got your point clearly ! ..
haha.
Instead of creating container from docker-api ,
you are suggesting, create a container pod from Kube-api
peer container needs to use k8s api like create -f deploy.yml
which can be managed to listen on port 53
in which you define a pod with container etc.
the net is that you can not really just run a container in k8s env when that container is not part of any pods.
or a service, that won't work well.
that is not how k8s is for.
yupp,,, chaincode should be able to create a pod with a service
instead of docker-engine doing that!
chaincode should be able to exploit Kube-Api, correct ?
exactly,
thinking about if k8s is not using docker as the container engine
it will completely break.
but we can map the host docker-engine to pod's docker-engine
like
the volumes are mounted in k8s
这里可以说中文，这里可以说中文
@tolak chaincode可以通过`stub.SetEvent()`来发布事件，node SDK里有支持，具体参见https://github.com/hyperledger/fabric-sdk-node/blob/release/test/integration/events.js
@jimthematrix Thanks!
stub.GetStateByRange(startKey, endKey)，startkey和endkey的值设成一样可以吗？
@chawlanikhil24 after messing with dns and some of docker settings, I was able to get everything working on my k8s env.
@chawlanikhil24 instantiate chaincode and query the chaincode.
Please see the conversation I had with @greg.haskins on what I did to resolve the issue.
Has joined the channel.
that conversation was in channel #fabric-kubernetes
@baohua @jimthematrix @tongli 现在的证书生成工具, 生成了证书后可以扩展么, 没看到命令帮助里面有写?
@CarlXK I actually do not know how that is done. Next task to figure out. If you know how, please share here.
@CarlXK 目前不能扩展，一锤子买卖:slight_smile:
看工具类的代码是new的ca证书然后根据这个证书生成 节点证书, 那是不是可以改下代码, 把ca证书加载进去再然后生成其他节点证书
@jimthematrix so there is no way at all to add a user or an orderer or a peer?
@tongli no with the cryptogen tool right now. but you can use the resulting ca certs and key to initialize a fabric-ca server to issue additional certs for user/orderer/peer identities, or use a tool like openssl to do the same
@tongli not with the cryptogen tool right now. but you can use the resulting ca certs and key to initialize a fabric-ca server to issue additional certs for user/orderer/peer identities, or use a tool like openssl to do the same
@CarlXK 对的，想支持扩展就需要这么做
@jimthematrix right, I guess the missing pieces are after ca got your what needed, how do you make a new peer joining in an existing channel? can we do that? and how do you make an orderer join?
adding a new peer of an existing org to a channel is pretty straightforward: you get the latest channel config from the orderer and send that to the peer. this doesn't require modifying the channel. If you want to add a whole new org to the channel, then you first have to follow a process to update the channel config with the orderer, then send the updated channel config to the new peers of the new org
i actually don't know what is involved in adding new orderers to an existing network. it's a some combination of starting the new orderer node with the genesis block, and updating the consortium definition in the system channel. for details you'd have to ask @jyellick
Has joined the channel.
> you get the latest channel config from the orderer and send that to the peer.
This actually isn't true. The peer only supports joining through the genesis block.
> i actually don't know what is involved in adding new orderers to an existing network.
Generally, simply start the orderer with the same genesis block that the other orderers were started with. The orderer will catch up from the Kafka broker logs. Then, once the orderer is up to date, second a reconfiguration transaction on any channels you wish to use the new orderer updating the set of orderer addresses.
@baohua peer 节点的/etc/hyperledger/fabric是怎么制定的
哦 可以通过配置指定：$FABRIC_CFG_PATH
当我执行make docker的时候 我看到里面的里面指定了
FABRIC_CFG_PATH 是不是这个环境变量打包到了镜像当中去
？
if in dockerfile, then it is.
@jyellick thanks for your explanation on how the orderer joining the party. That actually makes a lot of sense to me.
@jyellick jason, what if the orderer comes from different org which was never part of the genesis block when it was created?
When genesis block gets created, it uses Orderer profile , I assumed that takes in the organizations which orderers belong to.
when a new orderer from a new org wants to jump in, the genesis block would not have any idea about the new org, right?
For now, you would still bootstrap the new orderer with the old genesis block. And the new orderer would play the chain forward until it got to the current state.
This approach has many drawbacks, and it is a planned feature in the future to allow the orderer to be bootstrapped from a later config block (and to generally allow data pruning)
But for v1, the only option is to start with the true genesis block.
As an alternative, you may copy the ledger from an already current orderer, and use that as the seed for a new orderer, this might be preferable in some devops scenarios.
@jyellick thanks, but I do not think I am clear on how the authentication is done for the new orderer, I mean how does everybody in the party already know this new guy and consider the new orderer legit? I mean how is the authentication done? or it does not really matter?
The Kafka orderers do not speak directly to eachother. They only interact via Kafka. So, if Kafka authorizes the new orderer (generally because of TLS), then this new orderer will be able to participate in ordering. Peers also authenticate via TLS, but additionally, when receiving a block, they verify that it has been signed by one of the ordering orgs per the BlockValidation policy. By default, this policy allows anyone from the ordering orgs to sign the blocks. Adding a new orderer org would extend this policy to allow this new org to sign blocks.
Excellent. Thanks so much!
@here 我在swarm mode下面启动了ca order在blockchain-master节点上, root.org1.xnqkl.com在另外一个blockchain-root节点上, 然后通过sdk install和instantiate, 在 install和instantiate一个cc完成后, 就开始报错
```
2017-07-20 10:01:30.934 CST [ConnProducer] NewConnection -> ERRO 3f8 Failed connecting to orderer.xnqkl.com:7050 , error: context deadline exceeded
2017-07-20 10:01:30.934 CST [deliveryClient] connect -> ERRO 3f9 Failed obtaining connection: Could not connect to any of the endpoints: [orderer.xnqkl.com:7050]
2017-07-20 10:01:34.937 CST [ConnProducer] NewConnection -> ERRO 3fa Failed connecting to orderer.xnqkl.com:7050 , error: context deadline exceeded
2017-07-20 10:01:34.937 CST [deliveryClient] connect -> ERRO 3fb Failed obtaining connection: Could not connect to any of the endpoints: [orderer.xnqkl.com:7050]
2017-07-20 10:01:39.939 CST [ConnProducer] NewConnection -> ERRO 3fc Failed connecting to orderer.xnqkl.com:7050 , error: context deadline exceeded
2017-07-20 10:01:39.940 CST [deliveryClient] connect -> ERRO 3fd Failed obtaining connection: Could not connect to any of the endpoints: [orderer.xnqkl.com:7050]
2017-07-20 10:01:46.942 CST [ConnProducer] NewConnection -> ERRO 3fe Failed connecting to orderer.xnqkl.com:7050 , error: context deadline exceeded
2017-07-20 10:01:46.942 CST [deliveryClient] connect -> ERRO 3ff Failed obtaining connection: Could not connect to any of the endpoints: [orderer.xnqkl.com:7050]
2017-07-20 10:01:57.943 CST [ConnProducer] NewConnection -> ERRO 400 Failed connecting to orderer.xnqkl.com:7050 , error: context deadline exceeded
2017-07-20 10:01:57.944 CST [deliveryClient] connect -> ERRO 401 Failed obtaining connection: Could not connect to any of the endpoints: [orderer.xnqkl.com:7050]
2017-07-20 10:02:16.946 CST [ConnProducer] NewConnection -> ERRO 402 Failed connecting to orderer.xnqkl.com:7050 , error: context deadline exceeded
2017-07-20 10:02:16.946 CST [deliveryClient] connect -> ERRO 403 Failed obtaining connection: Could not connect to any of the endpoints: [orderer.xnqkl.com:7050]
```
@here 我在swarm mode下面启动了ca order在blockchain-master节点上, root.org1.xnqkl.com在另外一个blockchain-root节点上, 然后通过sdk install和instantiate, 在 install和instantiate一个cc完成后, 就开始报错
```
2017-07-20 10:01:30.934 CST [ConnProducer] NewConnection -> ERRO 3f8 Failed connecting to orderer.xnqkl.com:7050 , error: context deadline exceeded
2017-07-20 10:01:30.934 CST [deliveryClient] connect -> ERRO 3f9 Failed obtaining connection: Could not connect to any of the endpoints: [orderer.xnqkl.com:7050]
2017-07-20 10:01:34.937 CST [ConnProducer] NewConnection -> ERRO 3fa Failed connecting to orderer.xnqkl.com:7050 , error: context deadline exceeded
2017-07-20 10:01:34.937 CST [deliveryClient] connect -> ERRO 3fb Failed obtaining connection: Could not connect to any of the endpoints: [orderer.xnqkl.com:7050]
2017-07-20 10:01:39.939 CST [ConnProducer] NewConnection -> ERRO 3fc Failed connecting to orderer.xnqkl.com:7050 , error: context deadline exceeded
2017-07-20 10:01:39.940 CST [deliveryClient] connect -> ERRO 3fd Failed obtaining connection: Could not connect to any of the endpoints: [orderer.xnqkl.com:7050]
2017-07-20 10:01:46.942 CST [ConnProducer] NewConnection -> ERRO 3fe Failed connecting to orderer.xnqkl.com:7050 , error: context deadline exceeded
2017-07-20 10:01:46.942 CST [deliveryClient] connect -> ERRO 3ff Failed obtaining connection: Could not connect to any of the endpoints: [orderer.xnqkl.com:7050]
2017-07-20 10:01:57.943 CST [ConnProducer] NewConnection -> ERRO 400 Failed connecting to orderer.xnqkl.com:7050 , error: context deadline exceeded
2017-07-20 10:01:57.944 CST [deliveryClient] connect -> ERRO 401 Failed obtaining connection: Could not connect to any of the endpoints: [orderer.xnqkl.com:7050]
2017-07-20 10:02:16.946 CST [ConnProducer] NewConnection -> ERRO 402 Failed connecting to orderer.xnqkl.com:7050 , error: context deadline exceeded
2017-07-20 10:02:16.946 CST [deliveryClient] connect -> ERRO 403 Failed obtaining connection: Could not connect to any of the endpoints: [orderer.xnqkl.com:7050]
```
@tongli @chawlanikhil24 在做kubernets的时候遇到过这种问题么?
@here 我在swarm mode下面启动了ca order在blockchain-master节点上, root.org1.xnqkl.com在另外一个blockchain-root节点上, 然后通过sdk install和instantiate, 在 install和instantiate一个cc完成后, 就开始报错
```
2017-07-20 10:01:27.931 CST [deliveryClient] StartDeliverForChannel -> DEBU 3f7 This peer will pass blocks from orderer service to other peers for channel xnchannel
2017-07-20 10:01:30.934 CST [ConnProducer] NewConnection -> ERRO 3f8 Failed connecting to orderer.xnqkl.com:7050 , error: context deadline exceeded
2017-07-20 10:01:30.934 CST [deliveryClient] connect -> ERRO 3f9 Failed obtaining connection: Could not connect to any of the endpoints: [orderer.xnqkl.com:7050]
2017-07-20 10:01:34.937 CST [ConnProducer] NewConnection -> ERRO 3fa Failed connecting to orderer.xnqkl.com:7050 , error: context deadline exceeded
2017-07-20 10:01:34.937 CST [deliveryClient] connect -> ERRO 3fb Failed obtaining connection: Could not connect to any of the endpoints: [orderer.xnqkl.com:7050]
2017-07-20 10:01:39.939 CST [ConnProducer] NewConnection -> ERRO 3fc Failed connecting to orderer.xnqkl.com:7050 , error: context deadline exceeded
2017-07-20 10:01:39.940 CST [deliveryClient] connect -> ERRO 3fd Failed obtaining connection: Could not connect to any of the endpoints: [orderer.xnqkl.com:7050]
2017-07-20 10:01:46.942 CST [ConnProducer] NewConnection -> ERRO 3fe Failed connecting to orderer.xnqkl.com:7050 , error: context deadline exceeded
2017-07-20 10:01:46.942 CST [deliveryClient] connect -> ERRO 3ff Failed obtaining connection: Could not connect to any of the endpoints: [orderer.xnqkl.com:7050]
2017-07-20 10:01:57.943 CST [ConnProducer] NewConnection -> ERRO 400 Failed connecting to orderer.xnqkl.com:7050 , error: context deadline exceeded
2017-07-20 10:01:57.944 CST [deliveryClient] connect -> ERRO 401 Failed obtaining connection: Could not connect to any of the endpoints: [orderer.xnqkl.com:7050]
2017-07-20 10:02:16.946 CST [ConnProducer] NewConnection -> ERRO 402 Failed connecting to orderer.xnqkl.com:7050 , error: context deadline exceeded
2017-07-20 10:02:16.946 CST [deliveryClient] connect -> ERRO 403 Failed obtaining connection: Could not connect to any of the endpoints: [orderer.xnqkl.com:7050]
2017-07-20 10:02:51.947 CST [ConnProducer] NewConnection -> ERRO 404 Failed connecting to orderer.xnqkl.com:7050 , error: context deadline exceeded
2017-07-20 10:02:51.947 CST [deliveryClient] connect -> ERRO 405 Failed obtaining connection: Could not connect to any of the endpoints: [orderer.xnqkl.com:7050]
2017-07-20 10:03:58.948 CST [ConnProducer] NewConnection -> ERRO 406 Failed connecting to orderer.xnqkl.com:7050 , error: context deadline exceeded
2017-07-20 10:03:58.949 CST [deliveryClient] connect -> ERRO 407 Failed obtaining connection: Could not connect to any of the endpoints: [orderer.xnqkl.com:7050]
2017-07-20 10:06:09.950 CST [ConnProducer] NewConnection -> ERRO 408 Failed connecting to orderer.xnqkl.com:7050 , error: context deadline exceeded
2017-07-20 10:06:09.950 CST [deliveryClient] connect -> ERRO 409 Failed obtaining connection: Could not connect to any of the endpoints: [orderer.xnqkl.com:7050]
2017-07-20 10:10:28.951 CST [ConnProducer] NewConnection -> ERRO 40a Failed connecting to orderer.xnqkl.com:7050 , error: context deadline exceeded
2017-07-20 10:10:28.952 CST [deliveryClient] connect -> ERRO 40b Failed obtaining connection: Could not connect to any of the endpoints: [orderer.xnqkl.com:7050]
2017-07-20 10:10:28.952 CST [blocksProvider] DeliverBlocks -> WARN 40c [xnchannel] Receive error: Attempts (10) or elapsed time (9m1.019540916s) exhausted
```
@tongli @chawlanikhil24 在做kubernets的时候遇到过这种问题么?
@baohua 请问一下，最新版本，我查了区块信息，previous hash和上一个区块的data hash 对应不起来？
这俩不是一回事
previous hash：上一个区块的区块hash（实际上是区块头的）；
data hash：仅data部分
那要怎么去验证？
Message Attachments
对上个区块头做hash
了解了，有没有fabric有没有提供接口？
你要这个？common/util/utils.go
想验证一下是否是对够对应上
@qiushaoxi 你用的是哪个sdk？ java-sdk是有做这个工具
现在用node
我还在研究中
@qiushaoxi 肯定能对上，我这边都试过了
我也试了
只是nodesdk，根据区块号查区块，返回里面没有当前区块hash
The tsc annual voting will start early next month. Every HLP contributor should already receive an email. Everyone can check the process and the contributor list at https://docs.google.com/document/d/1uAAiv7xkFlgwDKpkxy7xOrG6WqrP1uB6NufBCM17Q1o/. If some contributor cannot find his name, pls feel free to let me know, thanks!
The tsc annual voting will start early next month. Every HLP contributor should already receive an email. Everyone can check the process and the contributor list at https://docs.google.com/document/d/1uAAiv7xkFlgwDKpkxy7xOrG6WqrP1uB6NufBCM17Q1o/. If any contributor cannot find his name in the list, pls feel free to let me know, thanks!
```
2017-07-20 20:28:12.664 UTC [kvledger] NewProvider -> INFO 016 ledger provider Initialized
2017-07-20 20:28:12.664 UTC [kvledger] recoverUnderConstructionLedger -> DEBU 017 Recovering under construction ledger
2017-07-20 20:28:12.664 UTC [kvledger] recoverUnderConstructionLedger -> DEBU 018 No under construction ledger found. Quitting recovery
2017-07-20 20:28:12.664 UTC [ledgermgmt] initialize -> INFO 019 ledger mgmt initialized
2017-07-20 20:28:12.664 UTC [eventhub_producer] AddEventType -> DEBU 01a Registering BLOCK
2017-07-20 20:28:12.665 UTC [eventhub_producer] AddEventType -> DEBU 01b Registering CHAINCODE
2017-07-20 20:28:12.665 UTC [eventhub_producer] AddEventType -> DEBU 01c Registering REJECTION
2017-07-20 20:28:12.665 UTC [eventhub_producer] AddEventType -> DEBU 01d Registering REGISTER
2017-07-20 20:28:12.665 UTC [eventhub_producer] start -> INFO 01e Event processor started
panic: listen tcp 10.0.0.98:7052: bind: cannot assign requested address
goroutine 1 [running]:
github.com/hyperledger/fabric/peer/node.createChaincodeServer(0x144d880, 0xc4201b87e0, 0xc4201d9930, 0xc, 0x0, 0x0, 0x0)
/go/src/github.com/hyperledger/fabric/peer/node/start.go:294 +0x2af
github.com/hyperledger/fabric/peer/node.serve(0x1499f90, 0x0, 0x0, 0x0, 0x0)
/go/src/github.com/hyperledger/fabric/peer/node/start.go:136 +0x56f
github.com/hyperledger/fabric/peer/node.glob..func1(0x1430ac0, 0x1499f90, 0x0, 0x0, 0x0, 0x0)
/go/src/github.com/hyperledger/fabric/peer/node/start.go:75 +0x3f
github.com/hyperledger/fabric/vendor/github.com/spf13/cobra.(*Command).execute(0x1430ac0, 0x1499f90, 0x0, 0x0, 0x1430ac0, 0x1499f90)
/go/src/github.com/hyperledger/fabric/vendor/github.com/spf13/cobra/command.go:599 +0x3e9
github.com/hyperledger/fabric/vendor/github.com/spf13/cobra.(*Command).ExecuteC(0x1431120, 0xf, 0xc42000c035, 0x7)
/go/src/github.com/hyperledger/fabric/vendor/github.com/spf13/cobra/command.go:689 +0x339
github.com/hyperledger/fabric/vendor/github.com/spf13/cobra.(*Command).Execute(0x1431120, 0x1b, 0xc42000c035)
/go/src/github.com/hyperledger/fabric/vendor/github.com/spf13/cobra/command.go:648 +0x2b
main.main()
/go/src/github.com/hyperledger/fabric/peer/main.go:118 +0x54d
Logs from 7/20/17 8:28 PM to 7/
```
please can anyone help me with this !
pls check whether some other process already occupy the address.
@chawlanikhil24 your port has been taken. do a netstat -ntlp to see what process is taking that port.
you can not have two processes trying to bind to one port.
大侠们，fabric 1.0.0里面有没有接口去取过去一段实现执行的tx数和生成的block数？
大侠们都蜀山论剑去啦~~
:wink: 目前没有直接按照时间区间的查询 但是可以自己获取区块然后比较
Has joined the channel.
Has left the channel.
大热天的应该去游泳，论什么剑啊。自己取区块再比较就复杂多了，我再想想。
@liutc 你可以监听block的生成，然后记录在本地数据库，同时加上时间，这样本地可以快速统计实现执行的tx数和生成的block数？
Message Attachments
@pandabcai 多谢，这确实是个招
@tongli Thanks!. I'll just check it
@tongli the program is occuring due to this : ``` # - name: CORE_PEER_CHAINCODELISTENADDRESS
# value: "peer1-org2:7052"```
All the peers are not working with this environment variable
@chawlanikhil24 @jimthematrix @tongli 区块链网络中有ca/order, peer root, 现在动态增加一个peer的时候, 给这个peer安装完chaincode后, cc容器没有启动, 用java sdk调用cc报错, cc容器也没有启动
```
07-21 08:57:11.083 DEBUG o.h.f.s.Peer - peer.sendProposalAsync name: tcl.org1.xnqkl.com, url: grpc://123.207.3.152:7056
07-21 08:57:11.159 ERROR o.h.f.s.Channel - Sending proposal to tcl.org1.xnqkl.com failed because of: gRPC failure=Status{code=UNKNOWN, description=Failed to deserialize creator identity, err MSP Org1MSP is unknown, cause=null}
java.lang.Exception: io.grpc.StatusRuntimeException: UNKNOWN: Failed to deserialize creator identity, err MSP Org1MSP is unknown
at org.hyperledger.fabric.sdk.Channel.sendProposalToPeers(Channel.java:2029)
at org.hyperledger.fabric.sdk.Channel.sendProposal(Channel.java:1955)
at org.hyperledger.fabric.sdk.Channel.queryByChaincode(Channel.java:1930)
at com.xiangna.jd.sdk.ChainCodeService.query(ChainCodeService.java:181)
at com.xiangna.jd.sdk.ChainCodeService.query(ChainCodeService.java:318)
at com.xiangna.jd.sdk.ChainTemplate.query(ChainTemplate.java:259)
```
@chawlanikhil24 @jimthematrix @tongli 区块链网络中有ca/order, peer root, 现在动态增加一个peer的时候, 给这个peer安装完chaincode后, cc容器没有启动, 用java sdk调用cc报错, cc容器也没有启动, 有遇到过这种问题么
```
07-21 08:57:11.083 DEBUG o.h.f.s.Peer - peer.sendProposalAsync name: tcl.org1.xnqkl.com, url: grpc://123.207.3.152:7056
07-21 08:57:11.159 ERROR o.h.f.s.Channel - Sending proposal to tcl.org1.xnqkl.com failed because of: gRPC failure=Status{code=UNKNOWN, description=Failed to deserialize creator identity, err MSP Org1MSP is unknown, cause=null}
java.lang.Exception: io.grpc.StatusRuntimeException: UNKNOWN: Failed to deserialize creator identity, err MSP Org1MSP is unknown
at org.hyperledger.fabric.sdk.Channel.sendProposalToPeers(Channel.java:2029)
at org.hyperledger.fabric.sdk.Channel.sendProposal(Channel.java:1955)
at org.hyperledger.fabric.sdk.Channel.queryByChaincode(Channel.java:1930)
at com.xiangna.jd.sdk.ChainCodeService.query(ChainCodeService.java:181)
at com.xiangna.jd.sdk.ChainCodeService.query(ChainCodeService.java:318)
at com.xiangna.jd.sdk.ChainTemplate.query(ChainTemplate.java:259)
```
No! I'vent encountered to such an error
上面的问题解决了, 是因为peer没有加入, 现在又遇到一个错误, 我是分开安装cc到各个peer上, 结果就是 fingerprint mismatch
```
2017-07-21 17:54:30.948 CST [chaincode] ExecuteChaincode -> ERRO 460 Error executing chaincode: Could not get deployment transaction from LSCC for account_cc_go:1 - Get ChaincodeDeploymentSpec for account_cc_go/xnchannel from LSCC error: chaincode fingerprint mismatch data mismatch
2017-07-21 17:54:30.948 CST [endorser] callChaincode -> DEBU 461 Exit
```
@CarlXK 对，新的peer需要先送genesis block加入channel。上面的报错是在说本地的chaincode内容和链上已经instantiate了的有出入。你确定chaincode在安装到新peer时没有被修改过？要是确定没有改过，可能是java sdk的问题，请开一个JIRA bug
@chawlanikhil24 the error you had above is because your dns service was not working or your peer container does not know where to find dns service.
各位，我这里遇到个问题：下图是我的chaincode。我如果传入“createAccount”， 会执行失败，错误信息告诉我传入的函数名不正确（Error: chaincode error (status: 500, message: Invalid invoke function name.）。但是我如果改成“createUserAsset”这个就可以执行成功。（这个createUserAsset是我先前用过的函数名），我怀疑是以前部署的docker容器对现在有影响。可是我每次都是kill掉容器重新部署的啊。
Message Attachments
@jimthematrix 不是很懂这里的fcn的解释，假如我有一个chaincode function：test， 我该如何给”fcn“ 和 ”args“ 赋值才能call到它。我尝试了{fcn: “test", args: ["args of function test"]} 和 {fcn: "invoke", args:["test", "args of function test"]} 都失败了。
Message Attachments
@tolak 只干掉容器还不够，还需要清除掉image
@tolak 只干掉容器还不够，还需要清除掉peer构建的chaincode image
看来是这样哦，我发现我下命令peer chaincode install/instantiate 时 -n指定的chaincode id还是原来的没变，看来是跑的原来的image。谢谢哈
@jimthematrix 确认没有修改过, 我用的同样的代码和脚本来执行的, 我又重新做了一遍还是一样的结果, 我去提一个JIRA吧
启动ca, order
启动第一个Peer节点, install & instantiate cc
启动第二个Peer节点, install cc
调用第一个Peer的cc成功, 调用第二个Peer的cc失败
@jimthematrix 确认没有修改过, 我用的同样的代码和脚本来执行的, 我又重新做了一遍还是一样的结果, 我去提一个JIRA吧
启动ca, order
启动第一个Peer节点, install & instantiate cc
启动第二个Peer节点, install cc
调用第一个Peer的cc成功, 调用第二个Peer的cc失败
可以让谁先帮忙看看给一个workaround_?
@jimthematrix 确认没有修改过, 我用的同样的代码和脚本来执行的, 我又重新做了一遍还是一样的结果, 我去提一个JIRA吧
启动ca, order
启动第一个Peer节点, install & instantiate cc
启动第二个Peer节点, install cc
调用第一个Peer的cc成功, 调用第二个Peer的cc失败
我检查了两个Peer的容器, md5sum的结果是不同的
可以让谁先帮忙看看给一个workaround_?
@jimthematrix 确认没有修改过, 我用的同样的代码和脚本来执行的, 我又重新做了一遍还是一样的结果, 是不是因为我用了两个不同的容器来部署的cc, 相当于用不同的机器来部署cc
启动ca, order
启动第一个Peer节点, install & instantiate cc
启动第二个Peer节点, install cc
调用第一个Peer的cc成功, 调用第二个Peer的cc失败
我检查了两个Peer的容器, md5sum的结果是不同的
可以让谁先帮忙看看给一个workaround_?
一个channel中的其他peer实例化chaincode之后还有必要让其他peer实例化chaincode吗
如果预知要调用这个cc，建议提前实例化
@baohua 如果已经实例化过了的, 还能再实例化嘛, 会不会报错
本地cli重复会报错。重复实例化的意义是？
[ ](https://chat.hyperledger.org/channel/twg-china?msg=cpi8q6pLnPMEsaoFD) @CarlXK 很难判断为什么会先后两个package内容不一样，麻烦你开一个JIRA bug，好把前后两个在容器中的／var／hyperledger／production／chaincodes里的文件附件上，谢谢
[ ](https://chat.hyperledger.org/channel/twg-china?msg=C33qram3YNHeNtrpT) @baohua 比如cc1, 在Peer1上install&instantiate, 在peer2上又install&instantiate, 会报错嘛?
不同peer上不影响
instantiate 只能一次吧，
这个是正常步骤。怎么会报错[ ](https://chat.hyperledger.org/channel/twg-china?msg=vZTFnaiLuE5AC3Dfm)
已经实例化再次实例化会报400错误
[ ](https://chat.hyperledger.org/channel/twg-china?msg=YHvFu2nJj2J2FM6fh) @liuwenliang0632 不同Peer上面不影响 , @baohua 是对的
[ ](https://chat.hyperledger.org/channel/twg-china?msg=kvxb2mLNzcgPRjrfc) @CarlXK 也不知道是javasdk的问题还是怎么滴, 现在用javasdk在其他节点instantiate就是会报错
[ ](https://chat.hyperledger.org/channel/twg-china?msg=kvxb2mLNzcgPRjrfc) @CarlXK 也不知道是javasdk的问题还是怎么滴, 现在用javasdk在其他节点instantiate就是会报错, 试一下看看install完了直接调用是不是可以把容器拉起来
@CarlXK 每个chaincode在每个channel只能实例化一次，所以在peer1里install／instantiate了，然后在peer2里install了，就直接可以调用了（前提是peer2已经加入了channel）
install是针对peer的操作，instantiate是针对channel的操作
[ ](https://chat.hyperledger.org/channel/twg-china?msg=px5eigwsnsmhsNwcq) @jimthematrix 是的, 已经实验过了, 非常感谢!!!
Message Attachments
Failed to reach implicit threshold of 1 sub-policies, required 1 remaining 这个错误怎么理解？
Has joined the channel.
有人用nodejssdk 注册block event吗，，fabric通过event发的block里面没有交易的实际数据，，通过getblock获取的块中就有交易的实际数据。
Has joined the channel.
@baohua @jimthematrix order kafka模式, zk搭建三个节点, kafka一般几个节点?
@CarlXK I normally setup 3 nodes. according to some doc, more than three zk cluster is normally overkill.
so go with 3 for both.
yeap, zk's consensus algorithm is like the paxos, usually 3 nodes are used.
@liuwenliang0632 channel更新必须搜集足够签名，具体见http://hyperledger-fabric.readthedocs.io/en/latest/configtxlator.html或者用node SDK的话见https://fabric-sdk-node.github.io/tutorial-channel-create.html
@liuwenliang0632 channel更新必须搜集足够签名，具体见http://hyperledger-fabric.readthedocs.io/en/latest/configtxlator.html，或者用node SDK的话见https://fabric-sdk-node.github.io/tutorial-channel-create.html
@tongli @baohua many thanks
Hi people !
can anyone explain me the building of chaincode contianer ?
Since, I need to add my few environment variables ... how to do it ?
moreover, how does the chaincode container comes to know about the peer ? I checked the environment variables, there were no such indicattions about peer0
```
nikhil@nikhil-wicked-machine:~/CONTRIBUTION/Hyperledger/yeasy/docker-compose-files/hyperledger/1.0$ docker exec dev-peer0.org1.example.com-mycc-1.0 printenv
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
HOSTNAME=27539bc738ec
CORE_CHAINCODE_ID_NAME=mycc:1.0
CORE_PEER_TLS_ENABLED=true
CORE_CHAINCODE_LOGGING_LEVEL=info
CORE_CHAINCODE_LOGGING_SHIM=warning
CORE_CHAINCODE_LOGGING_FORMAT=%{color}%{time:2006-01-02 15:04:05.000 MST} [%{module}] %{shortfunc} -> %{level:.4s} %{id:03x}%{color:reset} %{message}
CORE_CHAINCODE_BUILDLEVEL=1.0.0-rc1
CORE_PEER_TLS_ROOTCERT_FILE=/etc/hyperledger/fabric/peer.crt
HOME=/root
```
when you instantiate chaincode, you need to specify the peer id, and peer credentials.
these pieces of information get passed to the chaincode eventually, that is how newly created chaincode container finds the way back to peer.
@baohua 看过protos/peer/proposal.proto这个文件吗
这里面说的我不是很明白
这个是protobuf定义文件
我想问的是里面的数据结构
我知道这是fabric自己定义的数据结构
这个文件是关于client 去背书的流程
里面的数据结构有点没有看懂
@baohua 想问一下有没有配置多channel配置文件的示例？
@jimthematrix
@qiushaoxi 你说应用channel么 这个可以启动后自行添加 `peer channel create`
@chawlanikhil24 the peer address is passed to the chaincode container in the command line as an argument: `--peer.address`:
```
"Cmd": [
"/bin/sh",
"-c",
"cd /usr/local/src; node chaincode.js --peer.address grpc://9.27.92.128:7051"
],
@chenxuan 具体哪一个数据结构不清楚？
ChaincodeProposalPayload
这个
message Proposal {
// The header of the proposal. It is the bytes of the Header
bytes header = 1;
// The payload of the proposal as defined by the type in the proposal
// header.
bytes payload = 2;
// Optional extensions to the proposal. Its content depends on the Header's
// type field. For the type CHAINCODE, it might be the bytes of a
// ChaincodeAction message.
bytes extension = 3;
}
还有这个extension
@jimthematrix Thanks ! got the thing
:)
@baohua 如果用zk + kafka来设置orderer集群, orderer设置两个OK么, 平常只用一个orderer, 另外一个orderer是为了备份?
orderer 可以设置任意多个，横向扩展作用
@here Dear all, we will have group meeting at 10AM this Wednesday morning, pls help update the agenda/attendee at https://wiki.hyperledger.org/groups/twgc/meeting/2017-08-02, thanks!
@baohua @here 为什么kafka模式的时候order启动的时候没问题, 但是order被连接后就一直重启
@baohua chaincode可以跨channel相互调用吗？
[ ](https://chat.hyperledger.org/channel/twg-china?msg=zuHkxRTP2PQP5Msdd) @baohua kafka启动后要等待一段时间才能启动order, order1 和 order2 启动有间隔嘛, 我现在总是有一个会报错
[ ](https://chat.hyperledger.org/channel/twg-china?msg=zuHkxRTP2PQP5Msdd) @baohua kafka启动后要等待一段时间才能启动order, order1 和 order2 启动有间隔嘛, 我现在总是有一个order会报错
```
2017-07-31 16:13:12.339 CST [orderer/kafka] try -> DEBU 0d9 [channel: testchainid] Retrying every 1s for a total of 10m0s
2017-07-31 16:13:13.339 CST [orderer/kafka] try -> DEBU 0da [channel: testchainid] Connecting to the Kafka cluster
[sarama] 2017/07/31 16:13:13.339349 config.go:329: ClientID is the default of 'sarama', you should consider setting it to something application-specific.
fatal error: unexpected signal during runtime execution
[signal SIGSEGV: segmentation violation code=0x1 addr=0x63 pc=0x7f432a4dc259]
runtime stack:
runtime.throw(0xc6da92, 0x2a)
/opt/go/src/runtime/panic.go:566 +0x95
runtime.sigpanic()
/opt/go/src/runtime/sigpanic_unix.go:12 +0x2cc
goroutine 52 [syscall, locked to thread]:
runtime.cgocall(0x9efc20, 0xc420021df8, 0xc400000000)
/opt/go/src/runtime/cgocall.go:131 +0x110 fp=0xc420021db0 sp=0xc420021d70
net._C2func_getaddrinfo(0x7f431c0008c0, 0x0, 0xc420294b70, 0xc420148548, 0x0, 0x0, 0x0)
??:0 +0x68 fp=0xc420021df8 sp=0xc420021db0
net.cgoLookupIPCNAME(0xc420386b40, 0x6, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0)
/opt/go/src/net/cgo_unix.go:146 +0x37c fp=0xc420021f18 sp=0xc420021df8
net.cgoIPLookup(0xc42005c4e0, 0xc420386b40, 0x6)
/opt/go/src/net/cgo_unix.go:198 +0x4d fp=0xc420021fa8 sp=0xc420021f18
runtime.goexit()
/opt/go/src/runtime/asm_amd64.s:2086 +0x1 fp=0xc420021fb0 sp=0xc420021fa8
```
感觉kafka启动的order非常不稳定啊, 一连就报错
```
2017-07-31 16:34:13.921 CST [orderer/kafka] try -> DEBU 0d9 [channel: testchainid] Retrying every 1s for a total of 10m0s
[sarama] 2017/07/31 16:34:14.921781 config.go:329: ClientID is the default of 'sarama', you should consider setting it to something application-specific.
2017-07-31 16:34:14.921 CST [orderer/kafka] try -> DEBU 0da [channel: testchainid] Connecting to the Kafka cluster
fatal error: unexpected signal during runtime execution
[signal SIGSEGV: segmentation violation code=0x1 addr=0x63 pc=0x7fcfc59f7259]
runtime stack:
runtime.throw(0xc6da92, 0x2a)
/opt/go/src/runtime/panic.go:566 +0x95
runtime.sigpanic()
/opt/go/src/runtime/sigpanic_unix.go:12 +0x2cc
goroutine 39 [syscall, locked to thread]:
runtime.cgocall(0x9efc20, 0xc42001fdf8, 0xc400000000)
/opt/go/src/runtime/cgocall.go:131 +0x110 fp=0xc42001fdb0 sp=0xc42001fd70
net._C2func_getaddrinfo(0x7fcfb80008c0, 0x0, 0xc420193c50, 0xc420116628, 0x0, 0x0, 0x0)
??:0 +0x68 fp=0xc42001fdf8 sp=0xc42001fdb0
net.cgoLookupIPCNAME(0xc4201e4a50, 0x6, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0)
/opt/go/src/net/cgo_unix.go:146 +0x37c fp=0xc42001ff18 sp=0xc42001fdf8
net.cgoIPLookup(0xc420378a20, 0xc4201e4a50, 0x6)
/opt/go/src/net/cgo_unix.go:198 +0x4d fp=0xc42001ffa8 sp=0xc42001ff18
runtime.goexit()
/opt/go/src/runtime/asm_amd64.s:2086 +0x1 fp=0xc42001ffb0 sp=0xc42001ffa8
created by net.cgoLookupIP
/opt/go/src/net/cgo_unix.go:208 +0xb4
```
@CarlXK 需要到#fabric-consensus频道里去问开发者
@jimthematrix core/platforms/car
这个car是什么玩意
一种语言
？
"Chaincode ARchive", Greg Haskin 的发明，总的想法是用一种打包格式来支持不同chaincode语言的部署（golang，java，node.js等等）
[ ](https://chat.hyperledger.org/channel/twg-china?msg=3SFTyRnynKJaKb9Qo) @jimthematrix 解决了, 是kafka集群没启动好, 跨机器方式要设置
- KAFKA_ZOOKEEPER_CONNECT=ZK_IP1:12181,ZK_IP2:22181,ZK_IP3:32181
- KAFKA_ADVERTISED_LISTENERS=PLAINTEXT://KAFKA_IP:KAFKA_PORT
并且这个时候的ZK_IP和KAFKA_IP要是宿主机的IP
fabric的代码编译有人在docker里做吗
可以在docker里编译 参考 https://github.com/yeasy/docker-hyperledger-fabric-base
thanks @baohua
目前起了不同的vm，每一个vm起了一个docker，模拟分布式fabric，目前orderer生成所有证书，然后同步到各个peer节点，目前用peer节点的cli创建channel，就报以下错误.求指导
peer channel create -o orderer.example.com:7050 -c mychannel -f ./channel-artifacts/channel.tx --tls --cafile /opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/ordererOrganizations/example.com/orderers/orderer.example.com/msp/cacerts/ca.example.com-cert.pem
UTC [grpc] Printf -> DEBU 003 Failed to dial orderer.example.com:7050: connection error: desc = "transport: authentication handshake failed: x509: certificate signed by unknown authority"; please retry.
Error: Error connecting due to rpc error: code = Internal desc = connection error: desc = "transport: authentication handshake failed: x509: certificate signed by unknown authority"
[ ](https://chat.hyperledger.org/channel/twg-china?msg=8dtkrR42sdjLn7MEb) @aaronzheng 可以看官方例子啊, orderer生成所有证书?
from the error log, seems tls handshake failed, can u disable the tls first to try?
thanks for your prompt response @baohua may i know how to disbale the tls?
i only set 'CORE_PEER_TLS_ENABLED=false', but after i create the channel, the cli still use tls.
from ur cmd parameter, remove --tls
removed the 'tls' from the command, it will prompt another error. i searched it in google, seems it related to go1.7 need the tls for serverhttp.
2017-08-01 08:15:41.766 UTC [msp] GetDefaultSigningIdentity -> DEBU 010 Obtaining default signing identity
2017-08-01 08:15:41.766 UTC [msp/identity] Sign -> DEBU 011 Sign: plaintext: 0AC3060A1508021A0608ADF180CC0522...F795B458DEEDC9FF65CF14DDC2F809BB
2017-08-01 08:15:41.766 UTC [msp/identity] Sign -> DEBU 012 Sign: digest: A2C52FB70F7D089A5B99E140770BA1CAABF7E3089B6E14C6B8C8764D13A3C907
2017-08-01 08:15:41.766 UTC [grpc] Printf -> DEBU 013 transport: http2Client.notifyError got notified that the client transport was broken unexpected EOF.
2017-08-01 08:15:41.767 UTC [grpc] Printf -> DEBU 014 transport: http2Client.notifyError got notified that the client transport was broken read tcp 172.18.0.3:36530->10.142.0.6:7050: read: connection
reset by peer.
Error: rpc error: code = Internal desc = transport is closing
@jimthematrix 我看node sdk的频道也有人在问 eventhub listener的问题, 我用java sdk也有这个问题, 目前有解决方案嘛?
strange, is the problem still happening with fabric 1.0 images?
@baohua 是的, 我现在是多机器部署, 就总是会有这样的问题, 不知道单机是不是也会有
@baohua 是的, 我现在是多机器部署, 就总是会有这样的问题, 不知道单机是不是也会有
而且还有个问题就是cc的容器 放一段时间再去调用就会要重新生成这个容器, 这是什么原因?
@baohua @jimthematrix 这两个问题能不能找人帮忙看看, 没法玩了
1. cc容器放置一段时间 在调用就会重新调用就会重新生成这个容器, 这样会导致调用超时
2. eventhub 在放置一段时间后根本就收不到消息了
@CarlXK 需要在grpc用户端设置keepalive，见https://github.com/hyperledger/fabric-sdk-node/blob/release/test/integration/invoke.js#L172，设置为每15秒发一个keepalive告知
java 设置的是5分钟发一次
我改一下
peer和chaincode容器之间的keepalive是在peer上设置的，sampleconfig/core.yaml:
```
# keepalive in seconds. In situations where the communiction goes through a
# proxy that does not support keep-alive, this parameter will maintain connection
# between peer and chaincode.
# A value <= 0 turns keepalive off
keepalive: 0
为什么javasdk设置的是grpc.NettyChannelBuilderOption.keepAliveTime
properties.put("grpc.NettyChannelBuilderOption.keepAliveTime", new Object[] {5L, TimeUnit.MINUTES});
properties.put("grpc.NettyChannelBuilderOption.keepAliveTimeout", new Object[] {8L, TimeUnit.SECONDS});
或者用CORE_CHAINCODE_KEEPALIVE=15
OK, 这个写在Peer的docker-compose 里面是吧
可以
我试试看
对应上面javaSDK，nodeSDK的两个环境变量是
```
grpc.http2.keepalive_time
grpc.http2.keepalive_timeout
对应上面javaSDK，nodeSDK的两个环境变量是
```grpc.http2.keepalive_time
grpc.http2.keepalive_timeout```
单位都是秒，默认值是300（五分钟）和3。 可能在你的环境下需要调整
非常感谢, 这个问题困扰了我两天, 正在观测, 让环境静止20分钟, 如果重新发送请求没有问题就是OK了
CORE_CHAINCODE_KEEPALIVE=15 设置了这个参数已经可以保持peer和容器之间的alive
grpc.NettyChannelBuilderOption.keepAliveTime 设置了5分钟好像还是不行, 我试试看30秒
CORE_CHAINCODE_KEEPALIVE=15 设置了这个参数已经可以保持peer和容器之间的alive
grpc.NettyChannelBuilderOption.keepAliveTime 设置了5分钟好像还是不行, 我试试看30秒
最后改成下面这样, 只设定keepAliveTime, 4mins OK 了
properties.put("grpc.NettyChannelBuilderOption.keepAliveTime", new Object[] {4L, TimeUnit.MINUTES});
CORE_CHAINCODE_KEEPALIVE=15 设置了这个参数已经可以保持peer和容器之间的alive
grpc.NettyChannelBuilderOption.keepAliveTime 设置了5分钟好像还是不行, 我试试看30秒
最后改成下面这样, 只设定keepAliveTime, 4mins OK 了
properties.put("grpc.NettyChannelBuilderOption.keepAliveTime", new Object[] {4L, TimeUnit.MINUTES});
虽然还会继续报错, 但是使用是可以了, 明天改成5分钟试试
```
08-01 15:38:00.897 ERROR i.n.h.c.h.DefaultHttp2Connection - Caught Throwable from listener onStreamActive.
java.lang.IllegalArgumentException: delay: -523587550241 (expected: >= 0)
at io.netty.util.concurrent.AbstractScheduledEventExecutor.schedule(AbstractScheduledEventExecutor.java:138)
at io.netty.util.concurrent.AbstractScheduledEventExecutor.schedule(AbstractScheduledEventExecutor.java:29)
at io.grpc.internal.KeepAliveManager.onTransportActive(KeepAliveManager.java:202)
at io.grpc.netty.NettyClientHandler$1.onStreamActive(NettyClientHandler.java:211)
```
@jimthematrix 这里为什么要设计成keepalive呢, 或者默认就是一直连接不可以嘛
@baohua 请问一下会议入口怎么进不去了
sorry 刚看到 https://wiki.hyperledger.org/doku.php?id=groups/twgc/meeting/2017-08-02
一会到 twgc的maillist看minutes吧 ：）
@baohua @jimthematrix 设置keepalivetime这个参数一定是基于grpc连接是TLS? 不是TLS行不行
AdminPrincipal 中admin和member 该怎么理解？同一org中的节点，有admin节点和非admin节点之分？
@here
谁能解释下peer背书究竟做了什么，代码在哪吗
@yp 默认的都是member
还能指定admin？求方法。。。
用cryptogen生成key pairs后，把某个peer的sign cert放到msp的admin cert目录
或者把Users目录下的Admin相关的key和sign cert挂载到某个Peer对应的目录
@Glen 模拟执行cc后的结果用escc进行签名..
目前没有做什么复杂的检查
@xixuejia 也就是说 admincert和 signcert一致的时候，该节点就是admin 节点咯？
是的，peer的身份就是org的admin role
saoga
那为什么要设立一个admin role的节点出来呢？
它会扮演哪些特定角色？还是执行什么特殊操作？
如果你的endorsement policy设置的是需要org1Admin的签名
那就需要peer是admin role
那么configtx.yaml中的AdminPrincipal: Role.ADMIN 目前应该没有用到
message ChaincodeProposalPayload {
// Input contains the arguments for this invocation. If this invocation
// deploys a new chaincode, ESCC/VSCC are part of this field.
bytes input = 1;
// TransientMap contains data (e.g. cryptographic material) that might be used
// to implement some form of application-level confidentiality. The contents
// of this field are supposed to always be omitted from the transaction and
// excluded from the ledger.
map
map
举例说明一下
TransientMap里面可以根据app的需要放任何内容。为什么要有这么个条目是这样：proposal payload里的内容是要签名的，保证背书请求里的payload和背书结果能对上, sign(hash(proposal_payload))，TransientMap尽管是proposal payload一部分，但并不被包括在hash里面，所以commiter在验证背书结果要算proposal payload hash时，已经没有TransientMap了。也就是说TransientMap只在endorsement request里存在，是app和endorser peer（包括chaincode）之间的小秘密
TransientMap里面可以根据app的需要放任何内容。为什么要有这么个条目是这样：proposal payload里的内容是要签名的，保证背书请求里的payload和背书结果能对上, sign(hash(proposal_payload))，TransientMap尽管是proposal payload一部分，但并不被包括在hash里面，所以commiter在验证背书结果要算proposal payload hash时，已经没有TransientMap了。也就是说TransientMap只在endorsement request里存在，是app和endorser peer（包括chaincode）之间的小秘密，orderer，committer，ledger都看不到
TransientMap里面可以根据app的需要放任何内容。为什么要有这么个条目是这样：proposal payload里的内容是要签名的，保证背书请求里的payload和背书结果能对上, sign(hash(proposal_payload))，TransientMap尽管是proposal payload一部分，但并不被包括在hash里面，所以commiter在验证背书结果要算proposal payload hash时，已经没有TransientMap了。也就是说TransientMap只在endorsement request里存在，是app和endorser（包括chaincode）之间的小秘密，orderer，committer，ledger都看不到
TransientMap里面可以根据app的需要放任何内容，通常是涉及chaincode处理交易需要，但是又不想被存在transaction里。为什么要有这么个条目是这样：proposal payload里的内容是要签名的，保证背书请求里的payload和背书结果能对上, `endorsement=sign(hash(proposal_payload-TransientMap))`，TransientMap尽管是proposal payload一部分，但endorser在对endorsement进行签名时并不被包括在hash里面，所以commiter在验证背书结果要算proposal payload hash时，已经没有TransientMap了。也就是说TransientMap只在endorsement request里存在，是app和endorser（包括chaincode）之间的小秘密，orderer，committer，ledger都看不到
TransientMap里面可以根据app的需要放任何内容，通常是涉及chaincode处理交易需要，但是又不想被存在transaction里。为什么要有这么个条目是这样：proposal payload里的内容是要签名的，保证背书请求里的payload和背书结果能对上, `endorsement=sign(hash(proposal_payload-TransientMap))`，TransientMap尽管是proposal payload一部分，但endorser在对endorsement进行签名时并不被包括它在hash里面，所以commiter在验证背书结果要算proposal payload hash时，已经没有TransientMap了。也就是说TransientMap只在endorsement request里存在，是app和endorser（包括chaincode）之间的小秘密，orderer，committer，ledger都看不到
TransientMap里面可以根据app的需要放任何内容，通常是涉及chaincode处理交易需要，但是又不想被存在transaction里。为什么要有这么个条目是这样：proposal payload里的内容是要签名的，保证背书请求里的payload和背书结果能对上, `endorsement = sign( hash( proposal_payload - TransientMap))`，TransientMap尽管是proposal payload一部分，但endorser在对endorsement进行签名时并不被包括它在hash里面，所以commiter在验证背书结果要算proposal payload hash时，已经没有TransientMap了。也就是说TransientMap只在endorsement request里存在，是app和endorser（包括chaincode）之间的小秘密，orderer，committer，ledger都看不到
TransientMap里面可以根据app的需要放任何内容，通常是涉及chaincode处理交易需要，但是又不想被存在transaction里。为什么要有这么个条目是这样：proposal payload里的内容是要签名的，保证背书请求里的payload和背书结果能对上,
```endorsement = sign( hash( proposal_payload - TransientMap))```
TransientMap尽管是proposal payload一部分，但endorser在对endorsement进行签名时并不被包括它在hash里面，所以commiter在验证背书结果要算proposal payload hash时，已经没有TransientMap了。也就是说TransientMap只在endorsement request里存在，是app和endorser（包括chaincode）之间的小秘密，orderer，committer，ledger都看不到
上面的解释省略了对交易的生命周期的介绍，是觉得你问这么高级的问题应该已经对交易的生命周期有了解了
@jimthematrix 现在发现客户端即时加了keepalive属性也不能保持住eventhub的连接, 在sdk client 放置一段时间后, eventhub就收不到任何事件了
我们现在的解决方案是每隔10分钟重新生成一下channel
@jimthematrix 现在发现客户端即时加了keepalive属性也不能保持住eventhub的连接, 在sdk client 放置一段时间后, eventhub就收不到任何事件了
我们现在的解决方案是每隔10分钟重新生成一下channel
我是用docker swarm 部署的, 多机器模式
@jimthematrix 能再解释一下input？
吗
repeat
@CarlXK 可以确认一下客户端grpc的版本吗？上面给的属性是基于1.2.4，如果grpc是1.3.x，属性名字会不一样
message ChaincodeProposalPayload {
// Input contains the arguments for this invocation. If this invocation
// deploys a new chaincode, ESCC/VSCC are part of this field.
bytes input = 1;
// TransientMap contains data (e.g. cryptographic material) that might be used
// to implement some form of application-level confidentiality. The contents
// of this field are supposed to always be omitted from the transaction and
// excluded from the ledger.
map
@chenxuan 具体是这个protobuf：https://github.com/hyperledger/fabric/blob/release/protos/peer/chaincode.proto#L54， 其实就是调用chaincode时的“Args”，用法参见https://github.com/hyperledger/fabric-sdk-node/blob/release/fabric-client/lib/Channel.js#L469
[ ](https://chat.hyperledger.org/channel/twg-china?msg=CqeyFDyYwaBPZSm7E) @jimthematrix 怎么看grpc版本
在你运行node的目录下`npm list grpc`
在你运行node的目录下 `npm list grpc`
[ ](https://chat.hyperledger.org/channel/twg-china?msg=xyX6HHmimoK45PkdP) @jimthematrix 我感觉像是chaincodeInvocationSpec
@CarlXK 感觉你是使用的是java sdk
@chenxuan @jimthematrix 用的是javasdk
你看pom.xml
oh，那样的话建议到#fabric-sdk-java里问@rickr
我看下1.几, 可以看到的
java SDK用的应该是grpc 1.4
java SDK用的应该是grpc 1.3
java SDK 1.0 用的应该是grpc 1.3
那个fabric 怎么看grpc的版本呢 @jimthematrix
在core/comm
当中抽取了grpc的公共实现
fabric Golang 就没有版本这一说了
fabric Golang 就没有版本这一说了，主要看什么时候vendor的
看了javasdk设置的方案, 也看了grpc客户端的版本, 并不能找到问题, 网上也没有看到有类似问题, 很头疼
看了javasdk设置的方案, 也看了grpc客户端的代码, 并不能找到问题, 网上也没有看到有类似问题, 很头疼
也不是，主要看什么时候vendor的
记得是在1.0发布以前升级到了grpc 1.4
服务端1.0发布的时候用的是什么版本
如果版本不对应好像会有问题
{
"checksumSHA1": "u5V5OglAZoibucYHK3OtIFYM+w0=",
"path": "github.com/golang/protobuf/protoc-gen-go/grpc",
"revision": "fec3b39b059c0f88fa6b20f5ed012b1aa203a8b4",
"revisionTime": "2017-05-12T17:16:34Z"
},
make gotools 一下
应该生成了一些东西吧
然后在看版本
应该是可以的吧
Has left the channel.
各位大神，我还是想问下，TLS问题。目前我是起了2个VM，VM1只有orderer，VM2是cli+peer，然后我在VM1生成证书，然后也同步到VM2。在cli通过以下命令去建立channel，会报证书错误。如果orderer禁止了TLS的话，就没问题。 有人知道要如何解决么？
peer channel create -o orderer.example.com:7050 -c mychannel -f ./channel-artifacts/channel.tx --cafile /opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/ordererOrganizations/example.com/orderers/orderer.example.com/msp/cacerts/ca.example.com-cert.pem
Failed to dial orderer.example.com:7050: connection error: desc = "t
ransport: authentication handshake failed: x509: certificate signed by unknown authority"; please retry.
Error: Error connecting due to rpc error: code = Internal desc = connection error: desc = "transport: authentication hand
shake failed: x509: certificate signed by unknown authority"
@jimthematrix 我对交易的流程还不是特别熟悉 能具体讲讲吗
Has joined the channel.
请问现在有基于Fabric开发的商业应用吗？
@baohua 我这个问题，我应该问谁？我尝试过自己编辑1.0的源码 然后跑，也是遇到tls问题。 用下载的1.0镜像也是会遇到这个问题。 只能关闭tls才能搭分布式的peer。
TLS证书是用什么方式生成的
用的e2e里面的命令生成的证书，因为我的理解是e2e可以跑得通，证书应该都是可以通用的。所以我把证书同步到vm2那里。 在vm2那里用cli创建channel
/opt/gopath/src/github.com/hyperledger/fabric/examples/e2e_cli/generateArtifacts.sh
我现在在没tls的情况下，继续打分布式，在跑完更新anchor后
peer channel update -oorderer.example.com:7050 -c mychannel -f ./channel-artifacts/Org1MSPanchors.tx --cafile /opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/ordererOrganizations/example.com/orderers/orderer.example.com/msp/cacerts/ca.example.com-cert.pem
要初始化mychannel
peer chaincode instantiate -o orderer.example.com:7050 --cafile /opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/ordererOrganizations/example.com/orderers/orderer.example.com/msp/cacerts/ca.example.com-cert.pem -C mychannel -n mycc -v 1.0 -c '{"Args":["init","a","100","b","200"]}' -P "OR ('Org1MSP.member','Org2MSP.member')"
但会出现这个错误，有什么想法么？
Error endorsing chaincode: rpc error: code = Unknown desc = Failed to deserialize creator identity, err MSP Org1MSP
is unknown
{"code":-100,"message":"Failed query proposal from peer peer0.org1.example.com status: FAILURE. Messages: Sending proposal to peer0.org1.example.com failed because of: gRPC failure=Status{code=INTERNAL, description=io.grpc.netty.NettyClientTransport$3: Frame size 4703206 exceeds maximum: 4194304. , cause=null}. Was verified : false","data":null}
@jimthematrix
看一下
我看了那个grpc的服务器设置了 maxRecvMsgSize = 100 * 1024 * 1024
maxSendMsgSize = 100 * 1024 * 1024
为什么我使用couchdb的时候还是报了这个错
@aaronzheng 如果关了tls能跑，我猜测多半是tls证书的问题，可以多检查检查。e2e是可以跑通的，可以对比参考。
@aaronzheng 应该使用tlscacerts目录下的ca证书
@chenxuan 消息包大小都是在客户端设置的，你说“grpc的服务器”是指什么？
我去取的时候 如果查询出来的数据量很大
服务器也应该要设置的吧
？
[ ](https://chat.hyperledger.org/channel/twg-china?msg=KSkfqDvjSgTQPh6kt) @zhuxubin01 详细文档：http://hyperledger-fabric.readthedocs.io/en/latest/txflow.html
@chenxuan grpc基于http2 duplex stream，这个stream建立的时候主要是客户端设置参数的，服务器不会像http那样分别建立另外的通道传送响应消息
其实protos 里面的proposal,proposal_response,transaction protoful文件说的还是很明白的
@jiangyaoguo 感谢，的确是tls要用tlsca证书。换了证书后，就可以用tls创建channel了。
[ ](https://chat.hyperledger.org/channel/twg-china?msg=px5eigwsnsmhsNwcq) @CarlXK
[ ](https://chat.hyperledger.org/channel/twg-china?msg=y5kvb7mrz9PHDd985) @liuwenliang0632 我知道是可以调用, peer会自己把cc容器拉起来嘛, 但是现在的这个行为不是很奇怪么, 不合理啊
会拉起来
现在这个行为就是不合预期啊, 因为两个cc都在其他节点被初始化了, 如果能instantiate就应该都可以被instantiate, 要不就是都已经instantiate了
现在这个行为就是不合预期啊, 因为两个cc都在其他节点被初始化了, 如果能instantiate就应该都可以被instantiate, 要不就是都已经instantiated了
感谢各位，分布式的fabric1.0，我已经搭通了。之前主要是证书用了ca，没有用tlsca的问题卡住了。
想问下，有没orderer kafka相关的搭建文章。 接下来，要整合 kafka的。
Has joined the channel.
各位像Fabric之类的区块链，怎么知道哪个区块是最后一个啊
Leading Peer 和 Anchor Peer 分别在什么地方指定的呢？？
@here Leading Peer 和 Anchor Peer 分别在什么地方指定的呢？？
configtx
或者peer的参数
两个属性同事定义？
configtx指定的Anchor Peer ，peer配置指定的Leading Peer ？？ @liuwenliang0632
如何动态修改anchor peer
anchor peer挂了 怎么办
我看代码是有两种模式， 一个是竞选模式就是anchor peer，另一是指定模式必须指定 Leading Peer，这是我的理解。
anchor peer 与 Leading Peer 不是一个概念啊。。。你说的两种模式都是针对 Leading Peer的
orderer1.example.com | 2017-08-04 19:25:40.687 CST [cauthdsl] func2 -> DEBU 229 0xc42002e038 principal evaluation fails
orderer1.example.com | 2017-08-04 19:25:40.687 CST [cauthdsl] func1 -> DEBU 22a 0xc42002e038 gate 1501845940686542583 evaluation fails
orderer1.example.com | 2017-08-04 19:25:40.687 CST [orderer/common/broadcast] Handle -> WARN 22b [channel: testchainid] Rejecting broadcast message because of filter error: Rejected by rule: *sigfilter.sigFilter
我启动两个orderer 时，其中一个使用peer chaincode install 时 其中一个报错。在代码1.0.0中能搜到。在最新的master里面这个日志怎么去掉了？
@jimthematrix node-sdk的grpc不都是1.2.4的吗
anyone knows here how to check nginx_stream_proxy
I've created one and experiencing issues
[ ](https://chat.hyperledger.org/channel/twg-china?msg=ejfaKmJgKTgvARTh4) @liuwenliang0632 anchor peer是属于多个channel的节点，而leader peer是负责与order通信的节点
@baohua 我按照这个来跑kafka，https://github.com/yeasy/docker-compose-files/tree/master/hyperledger/1.0/kafka
但是在cli跑bash ./scripts/initialize.sh遇到这个错误，要怎么修改？（而且我本地的orderer.example.com改回对应的 10.138.0.7也会出这个错误）
2017-08-07 04:54:41.636 UTC [grpc] Printf -> DEBU 003 grpc: addrConn.resetTransport failed to create client transport: con
nection error: desc = "transport: Error while dialing dial tcp: lookup orderer.example.com on 127.0.0.11:53: no such host"
; Reconnecting to {orderer.example.com:7050
@baohua 根据这里https://github.com/yeasy/docker-compose-files/tree/master/hyperledger/1.0/kafka
这个 channel-artifacts/orderer.genesis.block 文件是怎么生成出来的啊？
1. 如果我启动的时候，没有 ”orderer.genesis.block文件“，
2. 直接运行docker-compose -f orderer-kafka.yaml up，
3. 就会变成创建一个 ”orderer.genesis.block目录“
这里是不是有什么设置问题的。
这个使用configtxgen工具提前生成的，如果你用的link中的例子 应该是会map本地的文件过去的，可以检查下路径。 @qiang0723
我那个问题，我现在看了下，其实只是把 genesis.block 改名为 orderer.gensis.block就可以启动成功了。
@baohua 在orderer-kafka.yaml里面 的cli，为什么不用配置智能合约路径-？ 不配置的话，会找不到chaincode安装的。../chaincode/go/:/opt/gopath/src/github.com/hyperledger/fabric/examples/chaincode/go
你如果follow这个例子 就要按照它的文档来 注意用的镜像并不是官方镜像 有差别
@baohua 现在好了，我按照那个例子 结合 官方镜像跑完了kafka啦。感谢！！！
后面还有一个小坑，就是那个网络CORE_VM_DOCKER_HOSTCONFIG_NETWORKMODE要修改为启动命令的文件夹名称+default
对 这个是compose的问题 默认用文件夹名了
我现在看会整个流程的log，发现在最前面，会出现很多这种日志，这个有问题的么？
orderer.example.com | 2017-08-07 07:37:34.966 UTC [orderer/common/deliver] Handle -> WARN 91c [channel: businesschannel] Rejecting deliver request because of consenter error
还想问下，orderer和kafka的个数有比例关系的么？例如是1个orderer要对应多少个kafka比较好？ 有没说3个orderer，要多少个kafka之类的？
我在按照http://hyperledger-fabric.readthedocs.io/en/latest/build_network.html页面操作，执行命令：peer channel create -o orderer.example.com:7050 -c $CHANNEL_NAME -f ./channel-artifacts/channel.tx --tls $CORE_PEER_TLS_ENABLED --cafile /opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/ordererOrganizations/example.com/orderers/orderer.example.com/msp/tlscacerts/tlsca.example.com-cert.pem时候报错
2017-08-07 08:40:54.164 UTC [msp] GetLocalMSP -> DEBU 001 Returning existing local MSP
2017-08-07 08:40:54.164 UTC [msp] GetDefaultSigningIdentity -> DEBU 002 Obtaining default signing identity
2017-08-07 08:40:54.168 UTC [channelCmd] InitCmdFactory -> INFO 003 Endorser and orderer connections initialized
2017-08-07 08:40:54.169 UTC [msp] GetLocalMSP -> DEBU 004 Returning existing local MSP
2017-08-07 08:40:54.169 UTC [msp] GetDefaultSigningIdentity -> DEBU 005 Obtaining default signing identity
2017-08-07 08:40:54.169 UTC [msp] GetLocalMSP -> DEBU 006 Returning existing local MSP
2017-08-07 08:40:54.170 UTC [msp] GetDefaultSigningIdentity -> DEBU 007 Obtaining default signing identity
2017-08-07 08:40:54.170 UTC [msp/identity] Sign -> DEBU 008 Sign: plaintext: 0A8C060A074F7267314D53501280062D...53616D706C65436F6E736F727469756D
2017-08-07 08:40:54.170 UTC [msp/identity] Sign -> DEBU 009 Sign: digest: B44AAB49697852D51DF8B09B25AF6E6DCF170EC55606642D06E07B98EA8D64BC
2017-08-07 08:40:54.170 UTC [msp] GetLocalMSP -> DEBU 00a Returning existing local MSP
2017-08-07 08:40:54.170 UTC [msp] GetDefaultSigningIdentity -> DEBU 00b Obtaining default signing identity
2017-08-07 08:40:54.170 UTC [msp] GetLocalMSP -> DEBU 00c Returning existing local MSP
2017-08-07 08:40:54.170 UTC [msp] GetDefaultSigningIdentity -> DEBU 00d Obtaining default signing identity
2017-08-07 08:40:54.170 UTC [msp/identity] Sign -> DEBU 00e Sign: plaintext: 0AC3060A1508021A060896CFA0CC0522...8BB80E746E443400E6E982E2F019DF94
2017-08-07 08:40:54.170 UTC [msp/identity] Sign -> DEBU 00f Sign: digest: 39468498C061EDE7F30E785248446A16633C4EEC2E63C1CB6347972F808F479D
Error: Got unexpected status: BAD_REQUEST
请问有哪位可以帮忙指点一下，感激不尽
这是在Create & Join Channel 这一步
是不是重复创建channel了？
@aaronzheng 谢谢您的回答，我还是没太明白
channel-artifacts crypto log.txt mychannel.block scripts
这是当前peer目录下的文件
没看到有生成
This command returns a genesis block -
文档上是这样描述的
channel创建成功后，就会出现mychannel.block的了。 如果你再次创建相同的channel，就会出现你上面的错误。 如果其他peer要加入这个channel，要复制这个mychannel.block，然后其他peer join channel指定这个文件就好了。
@aaronzheng ,谢谢，不过我好像还是没能抓住您的意思，我刚刚做了两次尝试：
1、复制mychannel.block
root@c421166ff918:/opt/gopath/src/github.com/hyperledger/fabric/peer# cp mychannel.block mychannel1.block
root@c421166ff918:/opt/gopath/src/github.com/hyperledger/fabric/peer# peer channel join -b mychannel1.block
2017-08-07 09:26:40.201 UTC [msp] GetLocalMSP -> DEBU 001 Returning existing local MSP
2017-08-07 09:26:40.201 UTC [msp] GetDefaultSigningIdentity -> DEBU 002 Obtaining default signing identity
2017-08-07 09:26:40.204 UTC [channelCmd] InitCmdFactory -> INFO 003 Endorser and orderer connections initialized
2017-08-07 09:26:40.204 UTC [msp/identity] Sign -> DEBU 004 Sign: plaintext: 0A89070A5B08011A0B08D0E4A0CC0510...64D81AB6CAC11A080A000A000A000A00
2017-08-07 09:26:40.204 UTC [msp/identity] Sign -> DEBU 005 Sign: digest: 26EBA4D83C1C721455A79D1624CF845A7896E38E57F6FB98136155AF7D6C3FA6
Error: proposal failed (err: rpc error: code = Unknown desc = chaincode error (status: 500, message: Cannot create ledger from genesis block, due to LedgerID already exists))
peer channel join失败了
2、修改CHANNEL_NAME
root@c421166ff918:/opt/gopath/src/github.com/hyperledger/fabric/peer# export CHANNEL_NAME=sqch
root@c421166ff918:/opt/gopath/src/github.com/hyperledger/fabric/peer# peer channel create -o orderer.example.com:7050 -c $CHANNEL_NAME -f ./channel-artifacts/channel.tx --tls $CORE_PEER_TLS_ENABLED --cafile /opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/ordererOrganizations/example.com/orderers/orderer.example.com/msp/tlscacerts/tlsca.example.com-cert.pem
2017-08-07 09:17:10.514 UTC [msp] GetLocalMSP -> DEBU 001 Returning existing local MSP
2017-08-07 09:17:10.514 UTC [msp] GetDefaultSigningIdentity -> DEBU 002 Obtaining default signing identity
2017-08-07 09:17:10.518 UTC [channelCmd] InitCmdFactory -> INFO 003 Endorser and orderer connections initialized
Error: Invalid channel create transaction : mismatched channel ID mychannel != sqch
创建失败
还请您费心指点一下
不胜感激
第一个问题，你用了同一个peer来选择加入。（首先，这里应该有4个peer，其中1个peer创建了channel，然后其他3个peer就是用channel.block来做加入的）目前我感觉，你应该是用创建的那个peer来做加入操作。
第二个问题，channel.tx里面其实包含了 channel的名称的了。 channel是你最外面生成证书和其他文件的时候，设置好的了。
另外求问一下，orderer要怎么做集群的？目前kafka可以做集群，但是orderer要怎么做的啊。求指导一下。
求教一下，
另外求问一下，orderer要怎么做集群的？目前kafka可以做集群，但是orderer要怎么做的啊。求指导一下。
@aaronzheng 非常感谢您
我好像找到原因了，这些操作我原来都做过，只是前面断电了，重启后，我感觉应该是有些步骤就不用重复做了。
我刚刚继续后面的步骤Install & Instantiate Chaincode，也遇到了类似的问题，但是invoke/query chaincode是正常的
For read-permissions we allow that the chain content is readable within a selection of MSP networks that govern the chain. 什么叫做a selection of MSP networks ，对于E2E来说是不是就是所有的节点
想问一下，kafka的集群，整个流程是怎么跑的啊？
现在想到的是，orderer貌似是没有集群的，通过客户端来做判断orderer是否有问题么？
整个流程 client（收集完签名）->orderer->kafka，然后kafka要做什么？还要把信息返回到orderer，还是直接广播给peer了？
kafka是做集群，形成消息队列。orderer是agent，从kafka读取消息
@baohua 看了下这个：https://docs.google.com/document/d/1vNMaM7XhOlu9tB_10dKnlrhy5d7b1u8lSY8a-kVjCO4/edit
相当于orderer之间是独立的，不会有信息交流，kafka是处理 orderer和committer之间的过程，由kafka来排序统一生成block，各自独立的orderer就可以获取相同的block。
但是我想知道，sdk 或者 cli 调用orderer失效时候，做failover是在sdk那里做处理的么要？
https://gerrit.hyperledger.org/r/#/c/12047/ 看是已经release 1.0.1了，怎么github上看不到。不开源了？
我在分布式部署的时候遇见一个问题，相对于e2e_cli的配置文件，我只是将所有配置的example.com修改为mytest.com，然后在启动order的时候就会出现如下错误：
Message Attachments
我启动了2个orderer，然后用chaincode做invoke的时候指定第二个orderer，出了这个错，有知道怎么解决么？
2017-08-09 03:07:38.381 UTC [orderer/main] Broadcast -> DEBU 0eb Starting new Broadcast handler
2017-08-09 03:07:38.381 UTC [orderer/common/broadcast] Handle -> DEBU 0ec Starting new broadcast loop
2017-08-09 03:07:38.387 UTC [orderer/common/broadcast] Handle -> WARN 0ed Rejecting broadcast because channel mychannel was not found
2017-08-09 03:07:38.387 UTC [orderer/main] func1 -> DEBU 0ee Closing Broadcast stream
是不是在orderer是solo的情况下，我有2个orderer，那么channel他们之间是互相不知道的。 所以如果我在orderer1创建的channel，orderer2是用不到这个channel的啊？
又不是kafka模式他们怎么会知道对方创建了channel并且同步
我同一个peer，用同一个channel.tx，指定2个orderer来创建2个同名mychannel~，我发现invoke的时候指定orderer1，那么orderer0的账本就没影响，是这样的么？那么是不是会有2个ledger的了？
相当于把orderer加入了不同网络的同名账本而已
应该是有两个ledger吧, 你进入peer的容器里面看下
我个人的感觉是，
ordererType=solo的话，同一个peer，channel只能对应一个orderer（目前验证了这个）
orderType=kafka的话，同一个peer，channel可以对应多个orderer。（这个准备去验证）
如果有其他建议或者情景验证，欢迎提出啊~~~
我个人的感觉是，
ordererType=solo的话，同一个peer，同名channel只能对应一个orderer（目前验证了这个）
orderType=kafka的话，同一个peer，同名channel可以对应多个orderer。（这个准备去验证）
如果有其他建议或者情景验证，欢迎提出啊~~~
Is there any method to supply user-defined environment variables to chain code container before instantiation ?
[ ](https://chat.hyperledger.org/channel/twg-china?msg=GGiyLcTF8qJWPi3s2) @dongqi 你有修改证书和初始配置吗？
另外想问一下，configtxlator 是不是真的可以做到 修改orderer的那个组织信息的？peer channel update -f config_update_as_envelope.pb -c testchainid -o 127.0.0.1:7050
然后就是如果，configtxlator 可以添加组织信息，那么我要如何用 crypto-config 生成新的组织证书？因为之前生成的证书时候，是包含进去了初始区块的了。
@chawlanikhil24 There's no direct support currently, but i guess it's useful in future to support more types of CoEs. So, would u like to open some jira issue for this? It should be not difficult to design and implement, as we can specify those ENV in core.yaml, and ask cc container to follow when starting it up at peer node.
@aaronzheng configtxlator just convert from/to json for the convenience to update the content.
crypto-config can generate new certs by running it again.
@baohua Exactly it Will be very useful ! :) I'll open a Jira issue for this in Fabric
昨天配置完单机多个orderer+kafka环境，现在在配置 多机orderer+kafka。 想问下，除了 configtx 和 CONFIGTX_ORDERER_KAFKA_BROKERS 要修改port，还有什么地方要修改的？目前我的orderer，还是默认去寻找9092端口。
請問 fabric-sdk-node 目前沒有再更新是因為 post-Fabric1.0 會推出 restful API 嗎?
大家早，想问一个问题。
1. 我昨天已经验证了 多机，多orderer的kafka情景，正常跑起来，1个peer对应1个orderer，是没问题的。
2. 但当我重启一个orderer的时候，日志中看不出异常，但是这个orderer在接到transaction后，做boardcast操作的时候，发现并没有发到peer。并且会导致其他orderer也同样失效。
这个是我的配置问题，还是其他导致的？
orderer.example.com | 2017-08-10 10:43:56.556 UTC [fsblkstorage] updateCheckpoint -> DEBU 361 Broadcasting about upd
ate checkpointInfo: latestFileChunkSuffixNum=[0], latestFileChunksize=[86760], isChainEmpty=[false], lastBlockNumber=[14]
orderer.example.com | 2017-08-10 10:43:56.556 UTC [orderer/multichain] WriteBlock -> DEBU 362 [channel: mychannel] W
rote block 14
orderer.example.com | 2017-08-10 10:43:56.556 UTC [orderer/kafka] processTimeToCut -> DEBU 363 [channel: mychannel]
Proper time-to-cut received, just cut block 14
orderer.example.com | 2017-08-10 10:43:56.556 UTC [orderer/kafka] processMessagesToBlocks -> DEBU 364 [channel: mych
annel] Successfully unmarshalled consumed message, offset is 43. Inspecting type...
orderer.example.com | 2017-08-10 10:43:56.556 UTC [orderer/kafka] processTimeToCut -> DEBU 365 [channel: mychannel]
It's a time-to-cut message for block 14
orderer.example.com | 2017-08-10 10:43:56.556 UTC [orderer/kafka] processTimeToCut -> DEBU 366 [channel: mychannel]
Ignoring stale time-to-cut-message for block 14
IMPORTANT: the TSC annual nomination email has now been distributed to everyone that is eligible to run (per the list above) -- if you did not receive this email (and should have), please get in touch with tbenzies@linuxfoundation.org ASAP.
早啊
peer chaincode package -n mycc -p github.com/hyperledger/fabric/examples/chaincode/go/chaincode_example02 -v 0 -s -S -i "AND('OrgA.admin')" ccpack.out，请问这个方法是起什么作用？
本地生成一个可以用作安装使用的cc的package。
package里可以含有多本chaincode？ 打包后一起安装吗？
@baohua 我执行 peer chaincode signpackage ccpack.out signedccpack.out后，输出signedccpack.out，然后我是拿signedccpack.out去执行install吗？
怎么才能安装signedccpack.out成功呢？ 我install的时候就报错
大家好啊 请问一下构建App Developers环境的fabric文档中指定的示例测试文件sfhackfest.tar.gz 是否已经无效了？ 【Getting Started with v1.0 Hyperledger Fabric - App Developers】 文档中“curl -L https://raw.githubusercontent.com/hyperledger/fabric/master/examples/sfhackfest/sfhackfest.tar.gz -o sfhackfest.tar.gz 2> /dev/null; tar -xvf sfhackfest.tar.gz” 无法执行 有没有其他构建环境的参考文档可以推荐啊？
大家有没有谁测试过，fabric目前对高并发交易的支持情况？大概什么程度会挂掉？
Dear all, we will have group meeting at 10AM this Wednesday morning, pls help update the agenda/attendee at https://wiki.hyperledger.org/groups/twgc/meeting/2017-08-16, thanks!
Has joined the channel.
Has joined the channel.
请问下policy /Channel/Readers 控制读取channel数据的权限 那么/Channel/Application/Readers /Channel/Application/Writers /Channel/Application/Admins /Channel/Orderer/Readers /Channel/Orderer/Writers /Channel/Orderer/Admins /Channel/*/Org/Readers 等这些是控制上面的权限
请问下policy /Channel/Readers 控制读取channel数据的权限 那么/Channel/Application/Readers /Channel/Application/Writers /Channel/Application/Admins /Channel/Orderer/Readers /Channel/Orderer/Writers /Channel/Orderer/Admins /Channel/*/Org/Readers 等这些是控制什么的权限
@baohua https://jira.hyperledger.org/browse/FAB-4821
你来提吧
请问下policy /Channel/Readers 控制读取channel数据的权限 那么/Channel/Application/Readers /Channel/Application/Writers /Channel/Application/Admins /Channel/Orderer/Readers /Channel/Orderer/Writers /Channel/Orderer/Admins /Channel/*/Org/Readers 等这些是控制什么的权限
有人遇到这个问题吗：用两个cli 去安装相同的链代码dao不同的peer，发现安装的结果不一样，codehash不同，导致后启动链代码的peer启动链代码失败：
Error executing chaincode: Could not get deployment transaction from LSCC for mycc:1.0 - Get ChaincodeDeploymentSpec for mycc/bancassurance from LSCC error: chaincode fingerprint mismatch data mismatch
我这个是chaincode 挂载cli容器的时候，文件owner不同导致的，，，打包chaincode的时候，文件头信息，除了名称，大小，其他是否可以都搞成默认的。否则这个太容易出现不一致了
please help file a bug in jira.hyperledger.org
including all the repeated steps, thanks!
ok
超级账本 tsc正在讨论后面代码管理是否迁移到 github上，想听听大家对 github vs gerrit 的一些体验~ pls help share ur experience by using gerrit and github, thanks!
Has joined the channel.
我个人的感觉是，github上参与的人应该比较多把。感觉用github大家都可以很方便pull和push代码，然后再由tsc来决定是否merge代码，方便很多。 gerrit我个人是没用过的。 另外开issue的话，可以在github进行讨论。
之前不是说github不能设置2个+2的这种策略吗
@aaronzheng thanks
@grapebaba are u sure the limit still exists now?
不清楚
[ ](https://chat.hyperledger.org/channel/twg-china?msg=FeeDTXvobGPfJtWNf) @barry_liang 我们也遇到了这个问题 , 我们是用java sdk , 如果启动两个sdk来操作就会出现这个问题, 如果一次操作完不会有问题, 操作完了把这个sdk所在容器保留了以后继续操作也不会有问题
我是看peer代码中打包 chaincode的时候有打包路径，名称，owner等信息，
或者可以用官方的tool把cc打包一下再安装, 目前没有试过
不知道java是否也有这问题
有这个问题的, 你用命令行还是node sdk?
不是，直接peer cli
同一个cli还是你安装完了又启动了cli容器
我是在两台机器上启动了两个cli
那是有问题的
把chaincode的owner都改成root：root，就解决了
这样两边就一致了
哦, 我试试
我看看java sdk有这个owner么
在实际应用的时候肯定要两个cli啊， 联盟链多家公司，不可能在一个地方安装链代码，都是各家公司安装自己的
你这个owner是什么的owner, 文件的owner么?
chaincode文件的owner，， ls -l 命令显示的那个
这个啊, 我还真没有注意
关于Chaincode cannot read back written values in same transaction，不知道现在有什么好的解法？我只看到https://jira.hyperledger.org/browse/FAB-2045 提到，也有相关的fix。但没找到建议怎么做。大家有经验么？
not supported currently, as it follows the mvcc model...
@muralisr the issue is reported here: https://chat.hyperledger.org/channel/twg-china?msg=uMtCb2nwK9oiZPAAW
Has joined the channel.
In English, instantiate the same cc, with different ownership
https://chat.hyperledger.org/channel/twg-china?msg=QRPsuYpphCDbQrbtc
The reporter is @barry_liang
thanks @baohua
everything else - path, cc content, etc remains same ?
@baohua @jimthematrix 在fabric架构相关文章里看到peer节点本地的ledger和orderer维护的ledger其实不同，peer节点本地的ledger是过滤掉了block中的无效交易的。然后当新节点加入channel时，是直接从其他peer同步只包含有效交易的ledger。请问我的理解是正确的吗？
@tolak 应该是不同的orderer当中应该只是吧tx打成了block
不是很明白这句话，可以详细解释下吗？ @chenxuan
@tolak orderer 上有所有的链，并且不知道tx是否合法；committer只有自己加入的通道的链。提交的时候，会检查tx是否合法，并对其进行标记。所有tx，无论是否合法，都会被封装到区块中。
@baohua 那意味这生成block实在orderer节点了
？
?
那意味这生成block是在orderer节点了
？
那意味着block的生成是在block当中了？
那意味这生成block是在orderer节点了
？
orderer是切出来能够形成block的一组tx，最终的完整block是在committer构成
orderer也打包出来区块，但是里面的tx是否合法的标记是空的
@baohua 谢谢，明白了
[ ](https://chat.hyperledger.org/channel/twg-china?msg=BsAuNXEaTM89Kow2Y) @muralisr yes everything else remains the same
[ ](https://chat.hyperledger.org/channel/twg-china?msg=JdpmXiAdvcsFn7jhD) @muralisr yes everything else remains same
@barry_liang how about opening some bug issue at jira.hyperledger.org, then people can follow to add comments. :grinning:
https://jira.hyperledger.org/browse/FAB-5835
[ ](https://chat.hyperledger.org/channel/twg-china?msg=Em9zk9DLNNEHzRtEG) @baohua @muralisr i create this: https://jira.hyperledger.org/browse/FAB-5835
thanks barry
Has joined the channel.
想确认一下，动态增加组织那里，是不是超过1个组织就不能单纯用cli添加？ 目前，如果只有1个组织，是可以按照configtxlator来做的，最后跑命令更新的 peer channel update。 但是如果超过1个组织，例如有2个组织，是不是就不可以，因为里面默认是majority，需要超过1半，但是cli命令里，我找不到有封装envelope包装2个签名的方法，是不是一定要用sdk来实现增加的了？
[ ](https://chat.hyperledger.org/channel/twg-china?msg=9G3WcraGSda5Ya22F) @baohua 有没有啥best practice来workaround？
想问下kafka模式下，生成block是在orderer生成的，还是在kafka生成的？因为我看到orderer有参数是，batch_time_out和 max_message_count， kafka那里有参数 message_max_bytes
@aaronzheng 你已经实现动态添加Org了吗？
docker compose中有service_name, host_name, container_name，源码示例中的`orderer.example.com:7050`, `peer1.org1.example.com:7051`这样的通信标识，是指其中哪一个呢？？TLS证书又是用的哪一个？
请问fabric中是否有用的keccak算法来作为散列算法的，在哪可以找到示例？
@baohua @jimthematrix 请问下CA怎么做集群?
ca提供rest服务 不带状态 可以直接横向扩展。但后端的数据库需要依赖数据库集群来做。
[ ](https://chat.hyperledger.org/channel/twg-china?msg=m6NN5nJWJqNei3NLX) @baohua 现在ca的后端数据库有分离配置么, 没看到啊
后端有数据库的 印象里至少支持mysql和postgre
你看下fabric-ca项目的文档
好, 我看看
@aaronzheng 你的理解是对的，在configupdate envelope里的签名，需要用SDK来封装，具体见https://fabric-sdk-node.github.io/tutorial-channel-create.html（如果你用java SDK的话，有类似的API）
@tolak fabric 1.0Keccak
@tolak fabric 1.0 初期曾用过SHA3，忘记了是否基于Keccak，后来因为SHA3对于SHA2并没有明显优势，又回到SHA2了
可以请问一下为什么需要用Keccak？
@jimthematrix 我也只是以前在代码里看到Keccak相关的，没有这方面的需求。
@jimthematrix 后来退回到SHA2 这个挺可惜。现在hard-coded的地方挺多，后面更新不太容易。
Has joined the channel.
@baohua 是的，有好多地方是hard-coded成SHA2，不过基本上限于系统层，像BCCSP Key里计算Subject Key Indentifier (SHA256)，面向用户的BCCSP设置是完全可以定制的
@baohua 是的，有好多地方是hard-coded成SHA2，不过基本上限于系统层，像BCCSP Key里计算Subject Key Indentifier (SHA256)，而面向用户的BCCSP设置是完全可以定制的
./bin/configtxgen -profile SampleDevModSolo -outputCreateChannelTx ./channel-artifacts/channel.tx -channelID businesschannel
2017-08-23 01:58:53.477 UTC [common/configtx/tool] main -> INFO 001 Loading configuration
2017-08-23 01:58:53.490 UTC [common/configtx/tool/localconfig] Load -> CRIT 002 Could not find profile: SampleDevModSolo
启动的时候我也添加了 环境变量 ORDERER_GENERAL_GENESISPROFILE=SampleDevModSolo
@baohua 这是什么原因？
不用SHA3应该还是没有经过时间检验吗
不用SHA3应该还是没有经过时间检验吧
@duwenhui 你那个profile要在configtx.yaml配置的。配置了没？
Has joined the channel.
@aaronzheng 没有配置
需要在当前目录引用对吧
TwoOrgsChannel:
1 ¦ Consortium: SampleConsortium
29 ¦ Application:
1 ¦ ¦ <<: *ApplicationDefaults
2 ¦ ¦ Organizations:
3 ¦ ¦ ¦ - *Org1
4 ¦ ¦ ¦ - *Org2
具体怎么配置，有没有文档说明白点？
configtxgen --help
@duwenhui 查下 configtx.yaml中有没有定义这个profile。
@baohua 没有定义， 我该怎么去定义呢？
@zhangchao SHA3 确实比较新
@baohua 贴个例子我参考下
SHA2 之前一直有一些传闻发现了问题，但是目前还没有公开得到证实的证据。
@duwenhui 你看看其他的是怎么定义的
Orderer:
TwoOrgsChannel:
1 ¦ Consortium: SampleConsortium
29 ¦ Application:
1 ¦ ¦ <<: *ApplicationDefaults
2 ¦ ¦ Organizations:
3 ¦ ¦ ¦ - *Org1
4 ¦ ¦ ¦ - *Org2
仿照这个定义一下就可以吧
定义完还要生成对应的证书文件那些的。 我建议你跑一次end2end，然后 看他的scripts是怎么做的把。 基本每一步都有详细介绍的了。
哦 明白了
SHA2 要是出问题了，比特币也就该寿终正寝了:grinning:
想确认一下，对同一对象，并发操作要怎么处理？ 目前我是多orderer然后kafka，但是对同一对象A，发起例如+10，两个transcation是会写进block里面，但是在读写集里面，明显标记的读的版本号会不一样，导致后一条transcation明显是不生效的。那么如何可以 处理同一对象的高并发？
这个问题很有探讨意义，希望大牛能给予解释和建议！:grimacing:
@tolak @aaronzheng 我最近正在思考如何解决这个问题，目前的主要想法是通过设计一种数据结构，达到每个交易都用不同的key的目的，可以在query时对总的状态做aggregate，还可以通过间歇性pruning对针对同一个asset的keys进行压缩，开一下这里：https://gerrit.hyperledger.org/r/#/c/12677/
@tolak @aaronzheng 我最近正在思考如何解决这个问题，目前的主要想法是通过设计一种数据结构，达到每个交易都用不同的key的目的，可以在query时对总的状态做aggregate，还可以通过间歇性pruning对针对同一个asset的keys进行压缩，看一下这里：https://gerrit.hyperledger.org/r/#/c/12677/
欢迎提供反馈意见
@jimthematrix 每个交易都用不同的key是不是还有双花的问题？目前这样做是为了解决双花吧？
并不是所有的场景都适用上面的手段，如果每笔交易都需要读资产目前的绝对状态的话，就不能这样做了。
@here
We will be having a brief discussion (~1/2 hr) about the translation tools this afternnon, and you are welcome to join us!!
Time: Aug 24, 15:00-15:30
Location: online meeting via https://ibm.webex.com/meet/guojiannan
Topic: Transifex vs Zanata vs github, which translation tool should we use for translation
Participants: public (Baohua, Linsheng and Jiannan have RSVPed)
Note: if you haven't used Webex before, you will be prompted to install plugin at first start.
改成UTXO方式，而不是基于当前的绝对状态计算资产余额。每次生成区块前计算是否存在账号余额不足的问题
应该不能模拟UTXO方式，因为在chaincode处理时看不到其他在pending状态的交易，所以不可能准确计算账号余额
当两笔交易获取了同样的readset version，但第一笔执行写了将version更新了，第二笔还是原来的version所以交易失败，有什么机制可以保证第二笔这个时候能update 他的version？
请问vagrant up第一次起来后的ubuntu初始密码是什么
更新了version 需要模拟交易，重新背书，就是等下一次生成区块了
确实，这样就等于串行执行了。
如果不是查询，都需要背书模拟执行，貌似这个点必须得“原子”执行如果一笔交易花费的时间长的话，性能就损耗太大了
开启TLS，部署Chaincode时，Chaincode容器里边报错：Error trying to connect to local peer: x509: certificate signed by unknown authority。请问是怎么回事？
@here
肯定是证书问题啊
正常firstnetwork就开了tls 你照着那个来就可以了啊
我改了docker的服务名，将peer0.org1.example.com改为peer0了
按照 firstnetwork跑肯定没问题啊。这不是为了找解决方法嘛，服务名难道必须是peer0.xxx.com这种形式？？
@baohua
disable tls 试试
disable tls是没问题的
docker服务名难道必须是peer0.xxx.com这种形式，不能改成peer0这种么？？
no 你改了名字后 证书也需要改
Has left the channel.
看一下你的tls证书 用的是ca证书还是 tlsca证书，两个不同的
应该用后者
?
你说的是要改crypto-config.yaml，然后重新生成证书么？？如果改成peer0，那这个文件该真么改？？@baohua
@baohua 杨老师 peer channel create的时候 验证创建channel签名的源码是在哪呀
@ylsGit 你想啊 证书是标致实体的身份的 肯定要跟名称绑定。你如果用cryptogen 工具生成的，它里面默认配置指定的domain是 x.example.com。需要更新到跟你的配置一样（common/tools/cryptogen/）
@zhuxubin01 可以看下 orderer/common/msgprocessor 下面的代码，orderer 消息处理基本都在这块。
那我如果用peer0这种格式，而不是xx.yy.com这种，那crypto-config该怎么改呢？因为有些管理docker的工具（比如rancher）不支持服务名里带“.”。 @baohua
这个我觉得是rancher的限制。。。
不过你可以试试把domain留空 或者fix掉生成的代码
不过你也可以试试把domain留空 或者fix掉生成的代码
对，是rancher自己的限制
Has joined the channel.
有人做过通过智能合约读本地文件吗 应该怎么实现 或者用getcreator获得的证书来做数据加密
为啥不在发给智能合约之前加密？
如果发给智能合约之前就加密 如何对加密的数据进行操作
为啥要读本地文件？本地文件哪儿来的？
- &Orderer
Name: OrdererMSP
ID: OrdererMSP
MSPDir: crypto-config/ordererOrganizations/example.com/msp
- &Orgr3
Name: Orgr3MSP
ID: Orgr3MSP
MSPDir: crypto-config/peerOrganizations/org3.example.com/msp
AnchorPeers:
- Host: peer0.org3.example.com
Port: 7051
- &Orge2
Name: Orge2MSP
ID: Orge2MSP
MSPDir: crypto-config/peerOrganizations/org2.example.com/msp
AnchorPeers:
- Host: peer0.org2.example.com
Port: 9051
改了id 生成创世快的时候报 CRIT 003 Error on inspectChannelCreateTx: No organization name matching: Org2MSP
是不能改ID吗@baohua
Has joined the channel.
@MCC 你上一步中用 cryptogen 生成憑證時候的 crypto-config.yaml 裡有 Org2MSP 嗎@@? 或者直接貼來看看@@?
OrdererOrgs:
- Name: Orderer
Domain: example.com
Specs:
- Hostname: orderer
PeerOrgs:
- Name: Org1
Domain: org1.example.com
Specs:
- Hostname: peer0
- Hostname: peer1
Users:
Count: 1
- Name: Org2
Domain: org2.example.com
Specs:
- Hostname: peer0
- Hostname: peer1
Users:
Count: 1
这是上一步的@Xeriou
阿 抱歉 我搞混了 應該是要麻煩你把完整的 configtx.yaml 貼上來
configtx.yaml中的Name,ID我是根据crypto-config中的name+'MSP'生成的，上面贴的是我试了改Name,ID生成失败，重新该回来的
Profiles:
OrgsOrdererGenesis:
Orderer:
<<: *OrdererDefaults
Organizations:
- *Orderer
Consortiums:
SampleConsortium:
Organizations:
- *Org3
- *Org4
OrgsChannel:
Consortium: SampleConsortium
Application:
<<: *ApplicationDefaults
Organizations:
- *Org3
- *Org4
Organizations:
- &Orderer
Name: OrdererMSP
ID: OrdererMSP
MSPDir: crypto-config/ordererOrganizations/example.com/msp
- &Org3
Name: Org3MSP
ID: Org3MSP
MSPDir: crypto-config/peerOrganizations/org1.example.com/msp
- &Org4
Name: Org4MSP
ID: Org4MSP
MSPDir: crypto-config/peerOrganizations/org2.example.com/msp
Orderer: &OrdererDefaults
OrdererType: kafka
Addresses:
- orderer.example.com
BatchTimeout: 2s
BatchSize:
MaxMessageCount: 10
AbsoluteMaxBytes: 98 MB
PreferredMaxBytes: 512 KB
kafka:
Brokers:
Organizations:
Application: &ApplicationDefaults
Organizations:
这是完整的
不知道怎么贴上来没有tab
沒關係 ~
看起來你只是改了 ID 跟 NAME 而已
是的
我改了之后 生成的时候日志还是提示 Generating anchor peer update for Org1MSP
你是用官方的 byfn.sh ?
我在fabric/examples/e2e_cli/里的例子改了之后也是生成失败
generateArtifacts.sh 你應該有這個檔案吧?
https://github.com/hyperledger/fabric/blob/release/examples/e2e_cli/generateArtifacts.sh#L90
90 跟 96 行的最後面那邊
要改成你的 Org3MSP 跟 Org4MSP
然後也要確認 你的 ./channel-artifacts/Org1MSPanchors.tx 是不是還是叫 Org1MSPanchors.tx
如果不是 也要改掉
嗯 试了 是这样 谢谢@Xieiou
不客氣~
:grinning:
換我想問些基本問題了...
我把基本的網路架構弄完了
目前是用 1 Orderer & 2 Peers 再跑
現在我想照官網 *Writing Your First Application* 章節一樣弄個 Node 的 App
但是我始終找不到範例中的憑證是哪來的...
下載下來後
```
ls -al fabric-samples/fabcar/creds/
5890f0061619c06fb29dea8cb304edecc020fe63f41a6db109f1e227cc1cb2a8-priv
5890f0061619c06fb29dea8cb304edecc020fe63f41a6db109f1e227cc1cb2a8-pub
PeerAdmin
```
然後我去 basic-network 那邊找 (照裡面的 script 來看，它去這裡啟動網路的)
```
ls -al fabric-samples/basic-network/crypto-config/basic-network/crypto-config/peerOrganizations/org1.example.com/users/Admin@org1.example.com/msp/keystore
5890f0061619c06fb29dea8cb304edecc020fe63f41a6db109f1e227cc1cb2a8_sk
```
確實有找到 private key
但另外兩個是怎麼產生的?
還是說有其他解決方式呢
我看了一下 fabric-ca 好像就是為了這個而生的
但我還是想先理解這段的原理
有人有相同疑問嗎??
@here Dear all, we will have group meeting at 10AM this Wednesday morning, pls help update the agenda/attendee at https://wiki.hyperledger.org/groups/twgc/meeting/2017-08-30, thanks!
@Xeriou basic-network里面通过docker-compose启动的其中一个容器是fabric-ca，可以向它申请用户证书，具体方法见fabric-samples／balance-transfer／app／helper.js
@jimthematrix 好的，我晚點來測試！
想问下，目前我用sdk在org1和org2安装了chaincode，执行成功。 接着用cli在org3安装相同的chaincode，为什么得出的md5不一样？ 运行query，会报 Get ChaincodeDeploymentSpec for example_cc_go/foo from LSCC error: chaincode fingerprint mismatch data mismatch
这个要怎么解决
重新搞
允许多人在package签署的意义在哪里？
org1的admin签署了，org2的admin没签署 不是也能在org2上的peer上执行install吗
是不是有地方可以配置只允许安装本org的admin签署过的package
有没有人遇到过 在本机fabric-samples能正常跑 但是到了阿里云服务器上 创建channel就包rpc错误了 2017-08-29 08:41:53.304 UTC [orderer/common/broadcast] Handle -> WARN 1aa Rejecting CONFIG_UPDATE because: Error authorizing update: Error validating DeltaSet: invalid mod_policy for element [Policy] /Channel/Application/Admins: mod_policy not set
2017-08-29 08:41:53.304 UTC [orderer/main] func1 -> DEBU 1ab Closing Broadcast stream
2017-08-29 08:41:53.307 UTC [orderer/common/deliver] Handle -> WARN 1ac Error reading from stream: rpc error: code = Canceled desc = context canceled
2017-08-29 08:41:53.307 UTC [orderer/main] func1 -> DEBU 1ad Closing Deliver stream
没有 重新搞吧
ali cloud is so expensive in US. I tried to use it, but it cost like $39 to create a VM, then it costs more to run it.
vs AWS, It costs me few dollars a month.
which runs fabric just fine.
use Digital Ocean
5 bucks
a month
fabric 部署Chaincode时出错：launchAndWaitForRegister failed Error starting container: no such image。但是我看宿主机上已经生成了Chaincode的image了。请教诸位:pray:
你的 network 不对
你的 network 不对@ylsGit
哦？
什么意思？ @liuwenliang0632
是peer里的CORE_VM_DOCKER_HOSTCONFIG_NETWORKMODE这个配置？ @liuwenliang0632
之前的chaincode fingerprint问题解决了，目前遇到下一个问题，就是org3实例化chaincode容器的时候，会一直卡在那里
container lock deleted(dev-peer0.org3.example.com-example_cc_go-1)
然后查看org3peer0的chaincode日志会显示这个：
ERRO 001 Error trying to connect to local peer: context deadline exceeded
求一些解决思路，谢谢了
org1的admin签署了，org2的admin没签署 不是也能在org2上的peer上执行install吗
能调用org2的peer，默认就当时有了peer2的签名吧
问题应该是出在 创世区块里面，没有org3msp，我虽然用sdk获取签名去修改了channel config，但是创世区块那里，我的新org3peer0要join channel的时候，用的还是同一个创世区块啊，里面根本没 有org3msp信息。
当是
join-channel的时候，不要用原来那个genesis.block了，考虑下拿当前配置然后configtxlator吧
@zhuxubin01 我这周就被这个折腾，感觉跟阿里云没关系，是用了1.0.1的images。我强制都用1.0.0的就好了。
多谢各位，org3的chaincode问题也解决了。 invoke query都可以了，刚刚重新测试了 端口映射，果然是那里错了，修改后，后动态添加的org3情景验证也做完了。
[ ](https://chat.hyperledger.org/channel/twg-china?msg=73kkwKgA7kXSyTHui) @liutc 刚刚也遇到了这个问题。在·1.01环境下重新build一遍configtxgen就好了。。。
@jimthematrix 看了cryptogen工具, 现在是给orderer和每个org都生成了一个根ca, 然后再基于根ca衍生节点, 这样orderer和每个org都是属于不同的ca下面
然后order给哪些org做共识是通过创始区块来配置, 组织之间的交互也是通过创始区块来配置, 这么理解对不对?
请问下orderer下面的testchainid起什么作用？
the testchainid is a orderering system channel id
目前的背书策略仍然不支持“成员数”，只支持角色？
[ ](https://chat.hyperledger.org/channel/twg-china?msg=Q6oy9hXDtogKDXNqg) @Hangyu 确实也看到在jira上有相关的讨论，这个错应该是configtxgen的binary在sample里面没更新导致的
hi all,
I deployed a channel containing peers from two orgs, and use the AND endorsement policy. And I need to invoke chaincode under this scenario.
So I new a Channel object "newChannel" and new "EventHub"s from two orgs, then newChannel.addEventHub(eventHub) and newChannel.initialize(). But I encountered below error, the eventhub from AMSP could be connected correctly but the ones from BMSP couldn't, and the "newChannel" could be only set one HFClient which only with one UserContext. *How could I achieve the goal that channel could connect to eventhubs from different orgs?* Thanks so much!
```
org.hyperledger.fabric.sdk.exception.EventHubException: io.grpc.StatusRuntimeException: UNKNOWN: event message must be properly signed by an identity from the same organization as the peer: [failed deserializing event creator: [Expected MSP ID AMSP, received BMSP]]
```
大家好，如上问题是我在java-sdk频道问的问题，也期望能在此处得到回复，先谢过。
我部署了一个联盟链，其中包含来自不同org的节点，基于AND背书策略。但是我使用java-sdk尝试invoke的时候遇到上面的问题，EventHub的对象通过newChannel.addEventHub(eventHub)注册之后，newChannel只能使用同一套UserContext去连接eventhub，但是我这个环境里的eventhub需要使用不同的MSP去操作。请问我应该如何处理这个问题？多谢。
@CarlXK 对的:thumbsup:，需要加一点的是创世区块之后可以继续通过ConfigUpdate来对整个联盟和每个通道的成员进行修改
[ ](https://chat.hyperledger.org/channel/twg-china?msg=FEXyzXCeE8deNq6w7) @ylsGit “成员数”是什么意思？可以用具体identity（就是ECert）来规定背书阈值
[ ](https://chat.hyperledger.org/channel/twg-china?msg=FEXyzXCeE8deNq6w7) @ylsGit “成员数”你是指什么？可以用具体identity（就是ECert）来规定背书阈值
@jimthematrix 更新整个联盟的属性是更新testchainid 这个channel吗？
对的，联盟本身是在系统通道里定义维护的，只不过“testchainid”就是一个默认值，其实就是genesis block里面的channel_id:
```"header": {
"channel_header": {
"channel_id": "testchainid",
"epoch": "0",
"timestamp": "2017-07-20T03:30:47.000Z",
"tx_id": "d7209496cc2fe7dad5547498ef07ff078d0706f02a7db3ea915181956f5cc360",
"type": 1,
"version": 1
},
"signature_header": {
"nonce": "0F7D4sbArSCSRh6csq5HCeRHzloIf29v"
}
}
对的，联盟本身是在系统通道里定义维护的，只不过“testchainid”就是一个默认值，其实就是genesis block里面的channel_id:
```"header": {
"channel_header": {
"channel_id": "testchainid",
"epoch": "0",
"timestamp": "2017-07-20T03:30:47.000Z",
"tx_id": "d7209496cc2fe7dad5547498ef07ff078d0706f02a7db3ea915181956f5cc360",
"type": 1,
"version": 1
},
"signature_header": {
"nonce": "0F7D4sbArSCSRh6csq5HCeRHzloIf29v"
}
}
对的，联盟本身是在系统通道里定义维护的，只不过“testchainid”就是一个默认值，其实就是genesis block里面的channel_id:
```"header": {
"channel_header": {
"channel_id": "testchainid",
"epoch": "0",
"timestamp": "2017-07-20T03:30:47.000Z",
"tx_id": "d7209496cc2fe7dad5547498ef07ff078d0706f02a7db3ea915181956f5cc360",
"type": 1,
"version": 1
},
"signature_header": {
"nonce": "0F7D4sbArSCSRh6csq5HCeRHzloIf29v"
}
}
所以是可以改成任何名字的
明白了。谢谢
[ ](https://chat.hyperledger.org/channel/twg-china?msg=iN7vG23PNbjHHPDps) @jimthematrix 那后面是会给ca增加接口来做这些颁发和吊销证书的操作, 还是说一直会通过工具来支撑
[ ](https://chat.hyperledger.org/channel/twg-china?msg=iN7vG23PNbjHHPDps) @jimthematrix 组织之间应该不会有交互吧, 还是说会有cc或者chanel的读写交互? 后面是会给ca增加接口来做这些颁发和吊销证书的操作, 还是说一直会通过工具来支撑
[ ](https://chat.hyperledger.org/channel/twg-china?msg=iN7vG23PNbjHHPDps) @jimthematrix 组织之间应该不会有什么交互吧? 后面是会给ca增加接口来做这些颁发和吊销证书的操作, 还是说一直会通过工具来支
[ ](https://chat.hyperledger.org/channel/twg-china?msg=iN7vG23PNbjHHPDps) @jimthematrix 组织之间应该不会有什么交互吧? 后面是会给ca增加接口来做这些颁发和吊销证书的操作, 还是说一直会通过工具来支撑
Has joined the channel.
@jimthematrix cryptogen生成的证书体系 如果我有5个org 那么必须要有5个ca节点来支持
安装智能合约时候提示下面的错误
```root@fadd9e32a3c8:/opt/gopath/src/github.com/hyperledger/fabric/peer# peer chaincode install -n cbca -v 1.3 -p cbca
2017-08-31 02:10:51.605 UTC [msp] GetLocalMSP -> DEBU 001 Returning existing local MSP
2017-08-31 02:10:51.605 UTC [msp] GetDefaultSigningIdentity -> DEBU 002 Obtaining default signing identity
2017-08-31 02:10:51.605 UTC [chaincodeCmd] checkChaincodeCmdParams -> INFO 003 Using default escc
2017-08-31 02:10:51.605 UTC [chaincodeCmd] checkChaincodeCmdParams -> INFO 004 Using default vscc
2017-08-31 02:10:51.662 UTC [golang-platform] getCodeFromFS -> DEBU 005 getCodeFromFS cbca
2017-08-31 02:10:51.839 UTC [golang-platform] func1 -> DEBU 006 Discarding GOROOT package bytes
2017-08-31 02:10:51.839 UTC [golang-platform] func1 -> DEBU 007 Discarding GOROOT package encoding/json
2017-08-31 02:10:51.839 UTC [golang-platform] func1 -> DEBU 008 Discarding GOROOT package fmt```
为啥会discarding goroot下面的package吗
[ ](https://chat.hyperledger.org/channel/twg-china?msg=R7AqqQxeTYtbWjio7) @jimthematrix 现在的背书策略都是`OR ('Org1MSP.member','Org2MSP.member')`这种形式，能不能定义成`某个组织里的几个节点`这种呢？使用ECert定义背书阈值是怎么做的？
比如”Org1中的3个member ADN Org2中的2个member“这样的背书策略？
Message Attachments
配置对应的背书策略。
但是记得更新这个策略的时候，因为一开始是只有org1和org2的，所以做更新策略，也需要有org1admin去发起upgradeproposal到org3peer0节点。 不然会更新失败的。
@CarlXK 证书管理是个很大的责任，我个人觉得fabric-ca不会延伸到这一块，fabric-ca只负责颁发和吊销，如何分发以及把各处的CRL更新，需要外部工具来完成
假如我把Fabric网络，所有相关节点都进行重启的话， 把相关的所有节点容器数据都做了持久化后，是否能保证整个Fabric网络能正常恢复。
@aaronzheng 你贴的这张图的背书策略，是由SDK解析的吧？貌似go-sdk没实现这部分。
@jimthematrix @baohua 我们现在用三个peer, 但是隔一段时间其中一个(固定这一个) 总会块高度比其他两个低, 有同步的办法么, 我看了日志没有什么特别的异常
1个
一个peer可以同时连接两个以上的ordering service吗。比如peer0和peer1已经和orderer0建立了channelA, peer2和peer3, orderer1建立了channel B, 现在想用peer1, peer 3 orderer0创建channel3，为什么peer3总是向自己原来的orderer1发送请求呢？
Message Attachments
我个人理解：
看你用的是orderer solo还是kafka，如果是用的是kafka的话，每个orderer之间其实是相同的。 你peer连接到哪个orderer都可以的，每个orderer本身是有全部账本的。
我用的是solo，当邀请peer3到channel3的时候peer3已经加入成功了，但是总是向自己原来的orderer1发送 deliver block的请求。
按道理应该向orderer0发送请求，这难道是bug或者我操作有问题
因为在创始区块里面制定了哪些orderer可以和哪个org(peers) 玩耍, 如果你想这么操作, 你得把vm2 的org的根ca加入到vm1 的创始区块中去
@Hangyu 因为在创始区块里面制定了哪些orderer可以和哪个org(peers) 玩耍, 如果你想这么操作, 你得把vm2 的org的根ca加入到vm1 的创始区块中去
[ ](https://chat.hyperledger.org/channel/twg-china?msg=tMCwdiCqRZKg3Gz64) @jimthematrix 那就要把现在生成证书的这部分代码改下, 可以急于现有根证书继续增加peer节点和User证书
[ ](https://chat.hyperledger.org/channel/twg-china?msg=bTpE4BPy7ePajMETA) @CarlXK 我已经把vm2的org根证书加到orderer0的创世块里面了啊。如果vm2的peer没有加入到channel B 的话，将peer3邀请进channelA没有任何问题，peer3也会向orderer0发送请求，但是如果peer3加入channel B的同时再将它邀请进入channelA的话，peer3就向orderer1发送deliver 请求，由于orderer1内没有channel3的信息，于是就一直报错。。。 @jimthematrix 这个可以看成是bug吗，或者有其它操作方法
@Hangyu orderer的地址是在通道配置里设的：https://github.com/hyperledger/fabric-samples/blob/release/basic-network/configtx.yaml#L87
[ ](https://chat.hyperledger.org/channel/twg-china?msg=5CSESS5NnTn4gSDJe) @jimthematrix 在生成channel3的genesis block的时候已经把通道地址设置成orderer0了，但是peer3依然像orderer发送deliver请求。。。
@jimthematrix @baohua 我们现在用三个peer, 但是隔一段时间其中一个(固定这一个) 总会块高度比其他两个低, 有同步的办法么
carlxk, could u help post the env info and steps? And better u could help provide some script like docker-compose files, that would be helpful for exploring the potential problem and debugging.
环境没法提供, 这个是一个内网环境, 只有这一套环境才有这个问题, 我在阿里云和腾讯云上面都没出现过这个问题
而且我开了peer的debug日志, 没什么特别的异常
如果有手动同步的办法就更好了, 如果没有我就只能尝试把那个节点的vm干掉重新生成 了
peer1.org1.example.com | goroutine 58 [IO wait]:
peer1.org1.example.com | net.runtime_pollWait(0x7fbbec742f88, 0x72, 0x0)
peer1.org1.example.com | /opt/go/src/runtime/netpoll.go:160 +0x59
peer1.org1.example.com | net.(*pollDesc).wait(0xc420282ed0, 0x72, 0xc4207a4d50, 0xc420016150)
peer1.org1.example.com | /opt/go/src/net/fd_poll_runtime.go:73 +0x38
peer1.org1.example.com | net.(*pollDesc).waitRead(0xc420282ed0, 0x13fbd80, 0xc420016150)
peer1.org1.example.com | /opt/go/src/net/fd_poll_runtime.go:78 +0x34
peer1.org1.example.com | net.(*netFD).accept(0xc420282e70, 0x0, 0x13f9940, 0xc420366f00)
peer1.org1.example.com | /opt/go/src/net/fd_unix.go:419 +0x238
peer1.org1.example.com | net.(*TCPListener).accept(0xc4201942a8, 0xc4207a4e38, 0xc4207a4e48, 0x455cc0)
peer1.org1.example.com | /opt/go/src/net/tcpsock_posix.go:132 +0x2e
peer1.org1.example.com | net.(*TCPListener).Accept(0xc4201942a8, 0xe30f90, 0xc42000e280, 0x1403b40, 0xc4201942a8)
peer1.org1.example.com | /opt/go/src/net/tcpsock.go:222 +0x49
peer1.org1.example.com | github.com/hyperledger/fabric/vendor/google.golang.org/grpc.(*Server).Serve(0xc42000e280, 0x1403b40, 0xc4201942a8, 0x0, 0x0)
peer1.org1.example.com | /opt/gopath/src/github.com/hyperledger/fabric/vendor/google.golang.org/grpc/server.go:454 +0x196
peer1.org1.example.com | github.com/hyperledger/fabric/core/comm.(*grpcServerImpl).Start(0xc4201ac620, 0x0, 0x0)
peer1.org1.example.com | /opt/gopath/src/github.com/hyperledger/fabric/core/comm/server.go:208 +0x41
peer1.org1.example.com | created by github.com/hyperledger/fabric/peer/node.serve
peer1.org1.example.com | /opt/gopath/src/github.com/hyperledger/fabric/peer/node/start.go:227 +0xc18
我在一台阿里云上启动脚本报这个错。怎么回事？
@liuwenliang0632 the shell is
启动docker-compose文件
use the e2e
?
对，这个脚本在其他机器上不会报错
seems grpc service can't bootstrap
刚买的阿里云。root@iZbp1hhwq5a6tneirmj6d0Z:~# docker version
Client:
Version: 17.07.0-ce
API version: 1.31
Go version: go1.8.3
Git commit: 8784753
Built: Tue Aug 29 17:43:06 2017
OS/Arch: linux/amd64
Server:
Version: 17.07.0-ce
API version: 1.31 (minimum version 1.12)
Go version: go1.8.3
Git commit: 8784753
Built: Tue Aug 29 17:41:57 2017
OS/Arch: linux/amd64
Experimental: false
嗯。百度里面搜不到答案。google 能搜到类似的。没看到解决方案:joy:
can you show the docker-compose file
嗯。github.com/hyperledger/fabric/examples/e2e_cli/network_setup.sh 就是这个启动脚本
我这是新装的阿里云 。所以想试一把是否能启动
@asaningmaxchain
Not Found
Message Attachments
https://github.com/hyperledger/fabric/tree/master/examples/e2e_cli/network_setup.sh
就是master上面最新的
问个stupid问题，fabric-sdk-java有没有文档说怎么用的？直接看test的code看的头大，而且还是没有理清楚到底要实现那些接口之后才能正常调用。。。
fabric所有container了都重启后无法执行智能合约
有人遇到过没
orderer节点报2017-09-01 02:46:17.212 UTC [blocksProvider] DeliverBlocks -> WARN 4ec [bqjchannel] Got error &{SERVICE_UNAVAILABLE}
```[channel: bqjchannel] Rejecting deliver request because of consenter error```
Has joined the channel.
@liutc 放弃fabric-sdk-java吧 还是用go的好些
@baoyangc 用go写业务逻辑和应用会死人的。。。还不如nodejs
[ ](https://chat.hyperledger.org/channel/twg-china?msg=3XekLn55tPq6Bn9Tm) @Hangyu 已经找到原因了，正在修，到时请帮忙reiview :)
@liutc 用nodejs才会死人的，来来来，留个微信我把你拉到go的群里
Has joined the channel.
@baoyangc 一直认为写企业系统、业务逻辑，还是java合适
Has joined the channel.
有人知道启动chiancode容器的这段代码在哪里吗 就是dev的那个容器
Has joined the channel.
@zhuxubin01 https://github.com/hyperledger/fabric/blob/release/core/chaincode/chaincode_support.go#L550
[ ](https://chat.hyperledger.org/channel/twg-china?msg=5WRAEaTzL52pW3wb2) @liutc 除了团队经验和熟悉程度会左右Java还是nodejs之外，可以分享一下有没有其他原因吗？
@jimthematrix 这个问题本质上跟区块链没关系，实际上是企业系统用什么语言比较合适的问题。之前跟 @baohua 讨论跟很多次，反正是个没结论的讨论。纯个人观点，从软工和可维护性角度，Java比较好些。相对容易的能让不同人写的代码风格相对一致，可读性也好。另外，强类型之类的特性比较有助于项目内不一致（特别是修改/变更导致的不一致）更早的被发现。
language battle is a permanent topic, the other one is which editor is better :)
i would say, let the people choose. At least, i would like to recommend JPG (Java(script) + Python + Golang) for new programers.
@jimthematrix another fact I noticed in China (in a customer project), is that .Net and Delphi are widely used for ERP, WMS, etc. And those languages are not supported (no SDK in those languages). Providing SDK layer RESTful APIs (fully on client side) might be a solution.
@liutc 谢谢分享，基本我猜的八九不离十。有关REST：https://jira.hyperledger.org/browse/FAB-156
之前就留意到了，期待中……
HI~
我使用 node sdk 時遇到了一個錯誤
`node: symbol lookup error: /{myhome}/xfabric/app/node_modules/grpc/src/node/extension_binary/grpc_node.node: undefined symbol: SSL_CTX_set_alpn_protos`
是 openssl 的問題嗎?還是 node/grpc 本身的問題@@?
我這裡使用 `OpenSSL 1.0.1e-fips 11 Feb 2013`
我的package.json只裝了
```
"dependencies": {
"fs-extra": "^2.0.0",
"fabric-client": "^1.0.0",
"fabric-ca-client": "^1.0.0"
}
```
有人有遇過相同的事情嗎??
我稍微查了一下相關錯誤
https://github.com/grpc/grpc/issues/9887
升級完 openssl 後還是一樣
所以讓我很困惑:woo:
可是我也沒引用grpc，應該是 fabric-client 自己裝的
所以才問這個問題 ORZ
have you tried ```npm install --build-from-source --grpc_alpn=false
otherwise, v1.0.2 is going to be released soon with grpc upgrade: https://gerrit.hyperledger.org/r/#/c/13159/
@jimthematrix YES~ I recompile openssl & exec this command
but still have error ...
That's fine, I'll keep finding problem.
and wait 1.0.2 release :P
v1.0.2 just got published to npm, feel free to give it a try
@jimthematrix YES~
It's work!
更新完後
`npm install --build-from-source --grpc_alpn=false`
要用這行安裝後 就OK了
但又遇到了一個問題QAQ
一樣的環境 我把chaincode 用 `peer chaincode instantiate ...` 的方式部屬上去了
`docker ps
但又遇到了一個問題QAQ
一樣的環境 我把chaincode 用 `peer chaincode instantiate ...` 的方式部屬上去了
`docker ps` 也有 `dev-peer0.peer.example.com-mycc-1.0...` 了
但 我執行 client app 時 會出現
`[client-utils.js]: sendPeersProposal - Promise is rejected: Error: cannot retrieve package for chaincode mycc/1.0, error open /var/hyperledger/production/chaincodes/mycc.1.0: no such file or directory`
但我沒有去指定說要用 dev mode
而且 我的 peer 裡面
也確實有這個檔案
@Xeriou 你的proposal送到那几个peer？每个peer必须都有自己的`/var/hyperledger/production/chaincodes/mycc.1.0`
@Xeriou 你的proposal送到那几个peer？每个peer必须都有自己的 `/var/hyperledger/production/chaincodes/mycc.1.0`
要分别install chaincode到每一个endorsing peer上
Dear all, we will have group meeting at 10AM this Wednesday morning, pls help update the agenda/attendee at https://wiki.hyperledger.org/groups/twgc/meeting/2017-09-13, thanks!
Has joined the channel.
两个组织中各自的任意三个节点背书即可，这个背书策略如何写？
Has joined the channel.
Has joined the channel.
背书策略如何才能指定某个peer必须背书
是不是node的支持 go的不支持啊
一直没明白， 背书策略中指定的member或者admin是怎么给交易签名的？
endorse peer在其中的角色是怎么样的？
Has joined the channel.
Has joined the channel.
多节点kafka的fabric集群，清空所有通道的的方式是如何做的？
如何清除基于kafka，多节点，fabric集群的通道？现在我琢磨的方法如下，感觉略麻烦，有更好的？
1 杀掉所有节点的orderer,peer进程
2 删除fabric临时数据（rm -r /var/hyperledger/production/）
3 清除kafka的主题 （kafka-topics.sh --delete --zookeeper 127.0.0.1 --topic test）
4 重启zookeeper和kafka
5 重启orderer,peer进程
1 杀掉所有节点的orderer,peer进程
2 删除fabric临时数据（rm -r /var/hyperledger/production/）
3 清除kafka的主题 （kafka-topics.sh --delete --zookeeper ）
4 重启zookeeper和kafka
5 重启orderer,peer进程
如何清除多节点 基于kafka的fabric集群的通道数据？
1 杀掉所有节点的orderer,peer进程
2 删除fabric临时数据（rm -r /var/hyperledger/production/）
3 清除kafka的主题 （kafka-topics.sh --delete --zookeeper ）
4 重启zookeeper和kafka
5 重启orderer,peer进程
如何清除多节点 基于kafka的fabric集群的通道数据？现在我琢磨的方法如下，感觉略麻烦，有更好的？
1 杀掉所有节点的orderer,peer进程
2 删除fabric临时数据（rm -r /var/hyperledger/production/）
3 清除kafka的主题 （kafka-topics.sh --delete --zookeeper ）
4 重启zookeeper和kafka
5 重启orderer,peer进程
如何清除多节点 基于kafka的fabric集群的通道数据？现在我琢磨的方法如下，感觉略麻烦，有更好的？
1 杀掉所有节点的orderer,peer进程
2 删除fabric临时数据（rm -r /var/hyperledger/production/）
3 清除kafka的主题 （kafka-topics.sh --delete --zookeeper 127.0.0.1 --topic test）
4 重启zookeeper和kafka
5 重启orderer,peer进程
Has joined the channel.
Has joined the channel.
有 fabric交流的微信群吗？
@jimthematrix 我的環境中只有一個 PeerMSP - [peer0.peer.example.com , peer1.peer.example.com]
其中又以 peer0.peer.example.com 當作 Anchor Peer
我也確定 peer0.peer.example.com 有該檔案
照文件上來說 peer1.peer.example.com 也應該要有 但我沒去檢查
但現在我再用 純 command 來測試QAQ"
暫時沒碰 SDK了 ORZ
@jimthematrix node sdk 对于channel有做缓存么, 比如建立一个channel对象, 然后就缓存起来下次直接取用 , 还是SDK只管创建销毁
@jimthematrix node/java sdk 对于channel有缓存并且一个channel只有一个channel对象
那如果我要对一个channel产生多个channel对象, 目前只能生成过个HFClient对象?
@jimthematrix 我的peer突然退出了, 貌似是收到了一个SIGTERM事件, 打印了sig: terminated, 但是我不知道为什么会收到这个事件...
```
2017-09-18 11:23:53.806 CST [chaincode] processStream -> DEBU 3f3b3 []Received message KEEPALIVE from shim
2017-09-18 11:23:53.806 CST [chaincode] processStream -> DEBU 3f3b4 Received KEEPALIVE Response
2017-09-18 11:23:55.753 CST [chaincode] processStream -> DEBU 3f3b5 []Received message KEEPALIVE from shim
2017-09-18 11:23:55.754 CST [chaincode] processStream -> DEBU 3f3b6 Received KEEPALIVE Response
2017-09-18 11:23:58.466 CST [nodeCmd] func3 -> DEBU 3f3b7 sig: terminated
2017-09-18 11:23:58.466 CST [fsblkstorage] Shutdown -> DEBU 3f3b8 closing fs blockStore:xnchannel
2017-09-18 11:23:58.466 CST [main] main -> INFO 3f3b9 Exiting.....
```
composer 这个开发。怎么查询块的数量？
现在有没有机制来处理私钥丢失的情况？如果一个用户私钥丢失了怎么证明他以前签署的数据还是有效的呢？
私钥丢失了，只影响后续的交易
对之前他签署的数据 通过验签就能证明是有效的了
@CarlXK 是的需要多个Client对象来处理，因为每个client只允许一个对应后台channel名字的Channel对象
上面这个sig: terminated问题需要到#fabric-peer-endorser-committer里问一下，nodeCmd本身非常简单，只负责peer的开启和状态两个命令
@zhaoliang1133 目前应该没有支持，可以到#composer-dev里问一下
[ ](https://chat.hyperledger.org/channel/twg-china?msg=QnHC4mZgWyhiJvapc) @jimthematrix 好的, 谢谢!
我要更新batchsize的话是需要更新mychannel 还是testchainid 还是2个都要更新
Has joined the channel.
batchsize是针对每个channel的，所以不需要涉及system channel（testchainid）
试用范例 https://github.com/hyperledger/fabric-samples/tree/release/balance-transfer
依照 https://hyperledgercn.github.io/hyperledgerDocs/getting_started/#_12
将区块链资料档放在 docker container 外面，重开 docker-compose 之后，却无法重新接上之前的区块链资料，请问这问题该如何解决？ 谢谢。
Has joined the channel.
@jimthematrix 刚才试了一下example02 用cli的方式运行 我把config.tx里面的batchtimeout设置成1分钟 message_count设置成100个 然后通过cli测试invoke a转账b 我的理解cli返回成功了应该就是出块了 我看了peer容器里面的blockfile也变大了 但是按照设置理论上1分钟之内应该是不会出块的 请问这是怎么一回事
invoke返回成功不代表出块了
@here
Dear all, we will have group meeting at 10AM this Wednesday morning, pls help update the agenda/attendee at https://wiki.hyperledger.org/groups/twgc/meeting/2017-09-27, thanks!
@baohua batchsize是针对channel的 batchtimeout是针对system channel的吗 我用configtxlator改了mychannel的batchtimeout 但是没有什么用 但是我改了configtx.yaml文件的batchtimeout 重新生成创世区块和channel.tx就有效果了
你是改了之后更新配置成功了吗？后者肯定是能成功因为是从一开始就该配置了。
可以吧你的问题和具体操作步骤发到社区的maillist，请大家帮忙找找问题。
我改了之后 重新屈fetchconfig 查出来是成功的
嗯 那说明提交配置了
@baohua 好的 我去社区发出去问问
:grinning: 注意书里面说的那几条~
[ ](https://chat.hyperledger.org/channel/twg-china?msg=SomFAcLbMEtq9JjdY) @zhuxubin01 你fetch修改之后的config，里边的timeout如果是修改成功后的值，就应该有效果。
你把orderer的log发来看一下
创建channel的时候会默认使用system channel的配置，之后每个channel的配置都是独立的，可以单独update
（其实batchtimeout, size等值对于system channel是没有意义的，因为 1）system channel本身并不需要接受非config类型的tx，2）config类型的tx都会立即单独成块。
只不过由于实现原因，system channel现在也能接受非config类型的tx，不过没啥用罢了。
Message Attachments
@guoger 已经发上来了
06:55:15 的就是我updateconfig的log
然后你是怎么判断不起作用的
1.我通过改configtx.yaml 改成60s 重新生成channel.tx和创世区块 2.运行invoke 创建一个账户a 3.查询a 60s之内没有查询到 4 我通过我自己写的工具修改batchtimeout为2s 5.同样 的我运行invoke创建账户b 6查询b还是60s之内查询不到 60秒之后查询到
第5步之前你用 `peer fetch config` 查询配置，确认已经改为2s了吗？
@guoger 我发现问题了 我重启order之后就生效了 这是什么原因 难道每次都要重启order吗
不用
最后还需要有生效的命令吗
[ ](https://chat.hyperledger.org/channel/twg-china?msg=KqtWzjuoBxA7oik7S) @guoger 你这一步的结果是什么
确定
刚才我做了第7步 重启order 8.创建账号c 9.查询 马上出来
不用重启就能生效 肯定哪里做得不太对
不用重启就能生效的。肯定哪里不太对
最后修改的命令docker exec cli /bin/bash -c './scripts/updateconfig.sh'
updateconfig.sh内容
export CORE_PEER_LOCALMSPID=OrdererMSP
ORDERER_CA=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/ordererOrganizations/example.com/orderers/orderer.example.com/msp/tlscacerts/tlsca.example.com-cert.pem
export CORE_PEER_MSPCONFIGPATH=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/ordererOrganizations/example.com/users/Admin@example.com/msp
peer channel update -o orderer.example.com:7050 -c mychannel -f config_update_as_envelope.pb --tls $CORE_PEER_TLS_ENABLED --cafile $ORDERER_CA
if [ $? -ne 0 ]; then
echo "error update config"
echo
exit 1
fi
export CORE_PEER_LOCALMSPID=Org1MSP
export CORE_PEER_MSPCONFIGPATH=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org1.example.com/users/Admin@org1.example.com/msp
你那个工具run出来的log看一下
btw 你可以用markdown来格式化一下你的消息
比如
```
updateconfig.sh内容
export CORE_PEER_LOCALMSPID=OrdererMSP
ORDERER_CA=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/ordererOrganizations/example.com/orderers/orderer.example.com/msp/tlscacerts/tlsca.example.com-cert.pem
export CORE_PEER_MSPCONFIGPATH=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/ordererOrganizations/example.com/users/Admin@example.com/msp
peer channel update -o orderer.example.com:7050 -c mychannel -f config_update_as_envelope.pb --tls $CORE_PEER_TLS_ENABLED --cafile $ORDERER_CA
if [ $? -ne 0 ]; then
echo "error update config"
echo
exit 1
fi
export CORE_PEER_LOCALMSPID=Org1MSP
export CORE_PEER_MSPCONFIGPATH=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org1.example.com/users/Admin@org1.example.com/msp
```
#####################################################
Sending config update to channel
#####################################################
2017-09-25 07:43:55.848 UTC [msp] GetLocalMSP -> DEBU 001 Returning existing local MSP
2017-09-25 07:43:55.848 UTC [msp] GetDefaultSigningIdentity -> DEBU 002 Obtaining default signing identity
2017-09-25 07:43:55.852 UTC [channelCmd] InitCmdFactory -> INFO 003 Endorser and orderer connections initialized
2017-09-25 07:43:55.852 UTC [msp] GetLocalMSP -> DEBU 004 Returning existing local MSP
2017-09-25 07:43:55.852 UTC [msp] GetDefaultSigningIdentity -> DEBU 005 Obtaining default signing identity
2017-09-25 07:43:55.853 UTC [msp] GetLocalMSP -> DEBU 006 Returning existing local MSP
2017-09-25 07:43:55.853 UTC [msp] GetDefaultSigningIdentity -> DEBU 007 Obtaining default signing identity
2017-09-25 07:43:55.853 UTC [msp/identity] Sign -> DEBU 008 Sign: plaintext: 0AF6050A0A4F7264657265724D535012...080612040A0232731A0641646D696E73
2017-09-25 07:43:55.853 UTC [msp/identity] Sign -> DEBU 009 Sign: digest: 78EAF68EE7158F38F5143D47F7C2AE6BD1CD5B6CDC00D7425B38CBD32D9ED172
2017-09-25 07:43:55.853 UTC [msp] GetLocalMSP -> DEBU 00a Returning existing local MSP
2017-09-25 07:43:55.853 UTC [msp] GetDefaultSigningIdentity -> DEBU 00b Obtaining default signing identity
2017-09-25 07:43:55.853 UTC [msp] GetLocalMSP -> DEBU 00c Returning existing local MSP
2017-09-25 07:43:55.853 UTC [msp] GetDefaultSigningIdentity -> DEBU 00d Obtaining default signing identity
2017-09-25 07:43:55.853 UTC [msp/identity] Sign -> DEBU 00e Sign: plaintext: 0AAD060A1508021A0608BBE7A2CE0522...900ADAD6B6E7835A50D0772D955D453F
2017-09-25 07:43:55.853 UTC [msp/identity] Sign -> DEBU 00f Sign: digest: F19BA15B229A1F6B766BDE8AD403C8A19EBA2D693429688FEA0A76225B7B2753
2017-09-25 07:43:55.907 UTC [main] main -> INFO 010 Exiting.....
你这段log没意义啊
发完整的吧
pastebin一下
Message Attachments
以上是整个log
Has joined the channel.
分享下午的问题解决方法 关于batimeout的修改已经解决 我用的是fabric1.0.0版本的 fabric1.0.0版本修改batchtimeout有bug需要修改完重启orderer才能生效 最新版本的images 可以修改成功无需重启order
Has joined the channel.
Has joined the channel.
Has joined the channel.
Has joined the channel.
大家好！想请假一下各位，chaincode容器启动的时候报这个错误是什么情况导致的？error: code = Unimplemented desc = unknown service protos.ChaincodeSupport, ending chaincode stream
Error starting Simple chaincode: rpc error: code = Unimplemented desc = unknown service protos.ChaincodeSupportroot@35f92f87a79e:/
大家好！想请教一下各位，chaincode容器启动的时候报这个错误是什么情况导致的？error: code = Unimplemented desc = unknown service protos.ChaincodeSupport, ending chaincode stream
Error starting Simple chaincode: rpc error: code = Unimplemented desc = unknown service protos.ChaincodeSupportroot@35f92f87a79e:/
大家好！想请教一下各位，chaincode容器启动的时候报这个错误是什么情况导致的？error: code = Unimplemented desc = unknown service protos.ChaincodeSupport, ending chaincode stream
Error starting Simple chaincode: rpc error: code = Unimplemented desc = unknown service protos.ChaincodeSupportroot@35f92f87a79e:/
大家好！想请教一下各位，chaincode容器启动的时候报这个错误是什么情况导致的？
error: code = Unimplemented desc = unknown service protos.ChaincodeSupport, ending chaincode stream
Error starting Simple chaincode: rpc error: code = Unimplemented desc = unknown service protos.ChaincodeSupportroot@35f92f87a79e:/
各位安安
遇到一個奇怪的問題
我想要做些壓力測試，方法如下是用
chaincode 分別為 out 跟 come,
```
func (tc *ThuChaincode) come(stub shim.ChaincodeStubInterface, args []string) peer.Response {
a 給 b 錢
...
time, err := stub.GetTxTimestamp()
if err != nil {
shim.Error("Time error")
}
//我需要監聽 deploy 時間，來統計從 deploy 到 發送給 peer 的時間
err = stub.SetEvent("ComeEvent", Int64ToBytes(time.GetSeconds()))
if err != nil {
shim.Error("Come Event error")
}
return shim.Success(nil)
}
func (tc *ThuChaincode) out(stub shim.ChaincodeStubInterface, args []string) peer.Response {
b 給 a 錢
...
time, err := stub.GetTxTimestamp()
if err != nil {
shim.Error("Time error")
}
//我需要監聽 deploy 時間，來統計從 deploy 到 發送給 peer 的時間
err = stub.SetEvent("OutEvent", Int64ToBytes(time.GetSeconds()))
if err != nil {
shim.Error("Out Event error")
}
return shim.Success(nil)
}
```
使用 peer invoke 指令來做測試
然後用 fabric 提供的 block-listener 來監聽
執行一次 peer invoke，確定 listener 有聽到我想要的內容
```
Chaincode Event:chaincode_id:"thucc" tx_id:"4b0fcc61171828005772c6ced954a3444706c7087a6a82dee46044fc2b726351" event_name:"OutEvent" payload:"\000\000\000\000Y\314\247\345"
```
但是只要同時執行兩次以上
就只有第一次的 peer invoke 會成功
其他的都是 invalid transaction
這樣是正常的嗎??
各位安安
遇到一個奇怪的問題
我想要做些壓力測試，方法如下是用
chaincode 分別為 out 跟 come,
```
func (tc *ThuChaincode) come(stub shim.ChaincodeStubInterface, args []string) peer.Response {
a 給 b 錢
...
time, err := stub.GetTxTimestamp()
if err != nil {
shim.Error("Time error")
}
//我需要監聽 deploy 時間，來統計從 deploy 到 發送給 peer 的時間
err = stub.SetEvent("ComeEvent", Int64ToBytes(time.GetSeconds()))
if err != nil {
shim.Error("Come Event error")
}
return shim.Success(nil)
}
func (tc *ThuChaincode) out(stub shim.ChaincodeStubInterface, args []string) peer.Response {
b 給 a 錢
...
time, err := stub.GetTxTimestamp()
if err != nil {
shim.Error("Time error")
}
//我需要監聽 deploy 時間，來統計從 deploy 到 發送給 peer 的時間
err = stub.SetEvent("OutEvent", Int64ToBytes(time.GetSeconds()))
if err != nil {
shim.Error("Out Event error")
}
return shim.Success(nil)
}
```
使用 peer invoke 指令來做測試
然後用 fabric 提供的 block-listener 來監聽
執行一次 peer invoke，確定 listener 有聽到我想要的內容
```
Chaincode Event:chaincode_id:"thucc" tx_id:"4b0fcc61171828005772c6ced954a3444706c7087a6a82dee46044fc2b726351" event_name:"OutEvent" payload:"\000\000\000\000Y\314\247\345"
```
但是只要同時執行兩次以上
就只有第一次的 peer invoke 會成功
其他的都是 invalid transaction
但我在終端上看到的又是兩筆 INFO 00a Chaincode invoke successful. result: status:200
這樣是正常的嗎??
請問有人能將 hyperledger/fabric-sdk-rest 成功執行起來嗎？
我在這一步都會失敗: and run npm link loopback-connector-fabric in the fabric-rest folder
Hyperledger community survey: https://www.surveymonkey.com/r/VNYZ6D7
请问一下怎么用peer channel fetch 获取配置块
有人用过吗
peer channel fetch config config_block.pb -o orderer.example.com:7050 -c channelname
[ ](https://chat.hyperledger.org/channel/twg-china?msg=cpZY32X3QggKADtY8) @Glen
你是在cli上操作，还是peer上面
我在cli上面操作了，但是似乎没有拿到块啊
cli container里面，块的名字是 config_block.pb
对啊，就是没有，我开启了tls，所以命令还带了orderer的证书的
有 error message 吗
没有
orderer里有什么message吗
Received block: header:<6:39 0:"\x00" } 0:4 4:119 3014423397:3322365509 24202727 { 1843:2247475411 18333206:1737171869 7:/* unexpected EOF */ /* unexpected EOF */ >data:<1:"\n\x87\a\n\x15\b\x01\x1a\x06\b\xb2\xa1\xb6\xce\x05\"\tmychannel\x12\xed\x06\n\xd0\x06\n\nOrdererMSP\x12\xc1\x06-----BEGIN -----\nMIICSzCCAfKgAwIBAgIQThQIisHaZ2TTJmR/gg398jAKBggqhkjOPQQDAjBpMQsw\nCQYDVQQGEwJVUzETMBEGA1UECBMKQ2FsaWZvcm5pYTEWMBQGA1UEBxMNU2FuIEZy\nYW5jaXNjbzEUMBIGA1UEChMLZXhhbXBsZS5jb20xFzAVBgNVBAMTDmNhLmV4YW1w\nbGUuY29tMB4XDTE3MDkyOTAwMTQxN1oXDTI3MDkyNzAwMTQxN1owWDELMAkGA1UE\nBhMCVVMxEzARBgNVBAgTCkNhbGlmb3JuaWExFjAUBgNVBAcTDVNhbiBGcmFuY2lz\nY28xHDAaBgNVBAMTE29yZGVyZXIuZXhhbXBsZS5jb20wWTATBgcqhkjOPQIBBggq\nhkjOPQMBBwNCAARt3JWLAuXMI8fZhS2piKq81l9rVr3iZ6O+Lhpv354wOj6qC8e5\ntOcCm6ZrQn2wrLpUO1/HvZ/lv72dZbwU3fldo4GMMIGJMA4GA1UdDwEB/wQEAwIF\noDATBgNVHSUEDDAKBggrBgEFBQcDATAMBgNVHRMBAf8EAjAAMCsGA1UdIwQkMCKA\nIG2m8xuZDMNDOyvJJT0PsUWRdNTDKrtVIUKSU0g9SzPnMCcGA1UdEQQgMB6CE29y\nZGVyZXIuZXhhbXBsZS5jb22CB29yZGVyZXIwCgYIKoZIzj0EAwIDRwAwRAIgeAqz\nz4Ed4e7v3DD+8l3gQ8QDjwNHK6nPPm9toGt2AnsCIAwJI6+a3WEL+u32L6tpiNNy\nyPtZypoafq5Vdf2V3h3N\n-----END -----\n\x12\x18\xf0\xfe\xe0\xb0,Vƀ|\xb3\x99N\x89\xd4\xe2H\x9b\v9\x04s\xd7u\xef\x12\xdcC\n\xd22\b\x01\x12\xcd2\x12\xd4\x1e\n\vApplication\x12\xc4\x1e\b\x01\x12\xf0\x0e\n\aOrg1MSP\x12\xe4\x0e\x1a\xc2\r\n\x03MSP\x12\xba\r\x12\xaf\r\x12\xac\r\n\aOrg1MSP\x12\xdb\x06-----BEGIN CERTIFICATE-----\nMIICTDCCAfOgAwIBAgIQSqz0R12J1MqgSNMzvkLrkDAKBggqhkjOPQQDAjBzMQsw\nCQYDVQQGEwJVUzETMBEGA1UECBMKQ2FsaWZvcm5pYTEWMBQGA1UEBxMNU2FuIEZy\nYW5jaXNjbzEZMBcGA1UEChMQb3JnMS5leGFtcGxlLmNvbTEcMBoGA1UEAxMTY2Eu\nb3JnMS5leGFtcGxlLmNvbTAeFw0xNzA5MjkwMDE0MTdaFw0yNzA5MjcwMDE0MTda\nMHMxCzAJBgNVBAYTAlVTMRMwEQYDVQQIEwpDYWxpZm9ybmlhMRYwFAYDVQQHEw1T\nYW4gRnJhbmNpc2NvMRkwFwYDVQQKExBvcmcxLmV4YW1wbGUuY29tMRwwGgYDVQQD\nExNjYS5vcmcxLmV4YW1wbGUuY29tMFkwEwYHKoZIzj0CAQYIKoZIzj0DAQcDQgAE\nQLxMzx6vUqLFm2f8CO+dw7Ng0oNeunLZKiW4HjHmVgUpa1OZ+vXfZm51MnMknmII\ncTjNyjmAb2EKOvqPalQScqNpMGcwDgYDVR0PAQH/BAQDAgGmMBkGA1UdJQQSMBAG\nBFUdJQAGCCsGAQUFBwMBMA8GA1UdEwEB/wQFMAMBAf8wKQYDVR0OBCIEIIahfiFC\nVCr/uWjQ/v6sywUynS7ceACiKE18qTxFy+tDMAoGCCqGSM49BAMCA0cAMEQCIAXh\ny4fHnbOqqXOpIE3UFyFpU75WufUC/VqIYEQ7QXH2AiA6AUwTFEupXFf4CIQEeBa2\n2+V45rqx8CXYEBTxjH2RRg==\n-----END CERTIFICATE-----\n\"\xb2\x06-----BEGIN CERTIFICATE-----\nMIICLzCCAdWgAwIBAgIRAKjBok1I8A7Ux16r4VUVx7QwCgYIKoZIzj0EAwIwczEL\nMAkGA1UEBhMCVVMxEzARBgNVBAgTCkNhbGlmb3JuaWExFjAUBgNVBAcTDVNhbiBG\ncmFuY2lzY28xGTAXBgNVBAoTEG9yZzEuZXhhbXBsZS5jb20xHDAaBgNVBAMTE2Nh\nLm9yZzEuZXhhbXBsZS5jb20wHhcNMTcwOTI5MDAxNDE3WhcNMjcwOTI3MDAxNDE3\nWjBbMQswCQYDVQQGEwJVUzETMBEGA1UECBMKQ2FsaWZvcm5pYTEWMBQGA1UEBxMN\nU2FuIEZyYW5jaXNjbzEfMB0GA1UEAwwWQWRtaW5Ab3JnMS5leGFtcGxlLmNvbTBZ\nMBMGByqGSM49AgEGCCqGSM49AwEHA0IABByrYS0mAcvYMWeOqz/MgIhy59XWb4Oh\nfC9ybD4CBsGUNxM4s36nZrchOIWygIxIYwTm5j1U2KSoHDBJFT+6zeWjYjBgMA4G\nA1UdDwEB/wQEAwIFoDATBgNVHSUEDDAKBggrBgEFBQcDATAMBgNVHRMBAf8EAjAA\nMCsGA1UdIwQkMCKAIIahfiFCVCr/uWjQ/v6sywUynS7ceACiKE18qTxFy+tDMAoG\nCCqGSM49BAMCA0gAMEUCIQCslEdMudci8hiK7yIXfPIlRb3aVilwzfznWXlkZDST\nbwIgVEYL2Qcj0ry3tu/oCLxK4u6aFdxIGx245436i3QcsqA=\n-----END CERTIFICATE-----\nB\x0e\n\x04SHA2\x12\x06SHA256\x1a\x06Admins\"0\n\aWriters\x12%\x12\x1b\b\x01\x12\x17\x12\b\x12\x06\b\x01\x12\x02\b\x00\x1a\v\x12\t\n\aOrg1MSP\x1a\x06Admins\"1\n\x06Admins\x12'\x12\x1d\b\x01\x12\x19\x12\b\x12\x06\b\x01\x12\x02\b\x00\x1a\r\x12\v\n\aOrg1MSP\x10\x01\x1a\x06Admins\"0\n\aReaders\x12%\x12\x1b\b\x01\x12\x17\x12\b\x12\x06\b\x01\x12\x02\b\x00\x1a\v\x12\t\n\aOrg1MSP\x1a\x06Admins*\x06Admins\x12\xf0\x0e\n\aOrg2MSP\x12\xe4\x0e\x1a\xc2\r\n\x03MSP\x12\xba\r\x12\xaf\r\x12\xac\r\n\aOrg2MSP\x12\xdb\x06
好面是cli的
上面是cli的
warding validly signed message for policy &{%!s(*common.ImplicitMetaPolicy=&{Readers 0}) %!s(int=1) [%!s(*policies.implicitMetaPolicy=&{0xc4202a7600 1 [0xc420190f48]}) %!s(*policies.implicitMetaPolicy=&{0xc4202a7b80 1 [0xc420190ff8 0xc420191098]})]}
2017-09-29 01:41:33.532 UTC [orderer/common/deliver] Handle -> DEBU f25 Received seekInfo (0xc4203923e0) start:
orderer这边发送block也正常啊
cli上的log好像有点问题 Received block: header:<6:39 0:"\x00" } 0:4 4:119 3014423397:3322365509 24202727 { 1843:2247475411 18333206:1737171869 7:/* unexpected EOF */ /* unexpected EOF */ >data:
可能·block本身有问题，从头做一遍再看看吧，发送和接受看起来都没问题啊。。。
又试了一把只建立channel，然后获取块，还是有异常信息
Received block: header:<6:39 0:"\x00" } 0:4 4:64 } 200:/* unknown wire type 7 */ } } 401496408075:4286930973694 164747 { 15:41 22173:/* unknown wire type 6 */ 210:/* unknown wire type 7 */ 335 {
Has joined the channel.
Has left the channel.
Has joined the channel.
Hello, 谁有 configtx.yaml 配置文件格式说明的详细文档？帮我发一下呗，谢谢了
Has joined the channel.
Has joined the channel.
Has joined the channel.
Message Attachments
eventHub监听到peer的交易返回，关闭连接这句代码，如果不注释的话，并发会报错。
有大佬遇到过这个问题吗
注释后，测了几十的并发，就没问题了。node的SDK
如果不注释，一并发就会报错
@hxmhlt feel free to report potential bugs at jira.hyperledger.org
请问谁知道peer是在什么时候跟orderer建立长链接的 建立长链接的代码在哪
还有peer节点接收order发送的区块的代码在哪
Message Attachments
@here Dear all, we will have group meeting at 10AM this Wednesday morning, pls help update the agenda/attendee at https://wiki.hyperledger.org/groups/twgc/meeting/2017-10-11, thanks!
noted, ths
Has joined the channel.
Has joined the channel.
建channel的时候，cli上报Error: Got unexpected status: BAD_REQUEST的错误，orderer上面报Rejecting CONFIG_UPDATE because: Error authorizing update的错误，用的是 v1.0.0-rc1分支，镜像是x86_64-1.0.3
有人感到过吗
有人碰到过吗
Has joined the channel.
@chenxuan 请问您遇到 “launchAndWaitForRegister failed Timeout expired while starting chaincode” 这个问题是如何解决的？谢谢
@Glen seems problem with ur config. And can u try the latest stable version 1.0 (released on July)?
@baohua 您好，请问在 peer chaincode instantiate 时候，出现 Error starting container: API error (404): {"message":"No such network: blockchain_net"} 这个错误可能是什么原因？
@KevinBai more information would be helpful. Now i can only guess, seems you are using docker? And maybe you can have a look at the config of `CORE_VM_DOCKER_HOSTCONFIG_NETWORKMODE`.
@baohua 请问这个错误可以从什么地方入手呢 2017-10-16 04:33:35.727 UTC [shim] userChaincodeStreamGetter -> ERRO 001 Error trying to connect to local peer: x509: cannot validate certificate for 172.18.0.10 because it doesn't contain any IP SANs
Error starting Simple chaincode: Error trying to connect to local peer: x509: cannot validate certificate for 172.18.0.10 because it doesn't contain any IP SANs
也是 Instantiating chaincode 时候遇到的 使用的 docker
what version of code are u using?
1.0.3
@baohua 我用的是 kafka 的
对照示例看了好久，实在是没有思路了 😓
错误出现在 cli 中 instantiate chaincode 的时候
我这个错误时在
ok, here u may have a look for the 1.0.3 demo: https://github.com/yeasy/docker-compose-files/tree/master/hyperledger/1.0.3
👍 ths
@baohua 还有个问题请教您，就是在crypto-config.yaml中关于 CA 字段中 Country 的设置不会生效吗？
Has joined the channel.
Has joined the channel.
FAB-5592 @KevinBai 在1.1中才有，这个是我做的
👍 谢谢 @liuwenliang0632
Has joined the channel.
Has joined the channel.
Has joined the channel.
Dear all, we will have group meeting at 10AM this Wednesday morning, pls help update the agenda/attendee at https://wiki.hyperledger.org/groups/twgc/meeting/2017-10-25, thanks!
@baohua 您好，我正在看您的新书《区块链 原理、设计与应用》，有个问题，咨询一下。第130页中以Ubuntu 16.04为例进行操作实例，安装一些依赖库，但是我想使用CentOS 7，不知道对应的是什么？我使用的是 yum install snappy-devel zlib-devel bzip2-devel libtool-ltdl-devel libtool，但是后面章节9.2.4里安装fabric-peer报错。
报错如下：$ CGO_CFLAGS=" " go install -ldflags "$LD_FLAGS -linkmode external -extldflags '-static -lpthread'" github.com/hyperledger/fabric/peer
# github.com/hyperledger/fabric/peer
/usr/local/go/pkg/tool/linux_amd64/link: running gcc failed: exit status 1
/usr/bin/ld: cannot find -lltdl
/usr/bin/ld: cannot find -lltdl
/tmp/go-link-315188194/000000.o: In function `_cgo_cb4050e05860_C2func_getaddrinfo':
/tmp/workdir/go/src/net/cgo-gcc-prolog:46: warning: Using 'getaddrinfo' in statically linked applications requires at runtime the shared libraries from the glibc version used for linking
/usr/lib/gcc/x86_64-redhat-linux/4.8.5/../../../../lib64/libpthread.a(libpthread.o): In function `sem_open':
(.text+0x6a23): warning: the use of `mktemp' is dangerous, better use `mkstemp'
collect2: error: ld returned 1 exit status
@baohua 您好，我正在读您的新书《区块链 原理、设计与应用》，第 130 页里，书中使用 Ubuntu 16.04 为例的，我想在 CentOS 7 下使用，不知道需要安装哪些依赖库？
目前我使用的是 yum install snappy-devel zlib-devel bzip2-devel libtool-ltdl-devel libtool
结果报最上面这个错误，不知道安装的版本问题还是少安装了哪个库？
@baohua @jimthematrix 现在是打了块的交易才算是成功了的, 有没有可以设置先让交易成功 然后在打快
因为交易比较少的时候基本上就是一个交易一个块好像很浪费啊
@opengloves from the logs, seems u're missing the lltdl, can u install that first?
sorry, i do not have centos, has anyone else tried at centos?
@CarlXK i guess ether set the maxsize or use the timeout..if you do not care of latency, maybe can set to a larger timeout. And can i know in what scenario you have so few transactions?
@CarlXK better not try to do that. You will be in the risk of that block not being generated. @baohua In Yijian we set timeout to 1second. In the current workload, there are many cases one block has just one tx.
[ ](https://chat.hyperledger.org/channel/twg-china?msg=iHumKFj6574mHh2h3) @liutc 我们现在也是设置的1秒, 但是时间长了块太多啊
@liutc not to do setting large latency?
@CarlXK try 10 seconds then :) Your system seems to have more transactions than mine
@CarlXK 在应用层可以通过proposal response里面的endorsement对比背书策略，认可交易成功，当然这是在可以排除双花的前提下
如果交易量很少，基本可以排除双花，但是这样应用层需要做很多校验
@baohua I personally do not like this 1-second setting. But the application is designed in a synchronized way so we do not have other option.
比如确认前面那个“自认”成功的交易确实被成功写进区块了
[ ](https://chat.hyperledger.org/channel/twg-china?msg=z9nJJX89TpsmXcJdv) @jimthematrix 排除双花之外也有风险吧, 如果只是比较背书返回成功但是发给orderer因为其他原因失败了, 后续还是要去确认这个交易是不是成功了, 还不如等待打快成功
@jimthematrix 我想对来说喜欢你这个方法。交易认可后应用认为交易被成功“提交”给区块链，但只说明大概率成功、并不保证成功写进区块（交易真正完成）。后续操作以区块链中数据为准。
最终成功就是打入块才算成功, 这个就是现在的设计, 感觉不太好有其他方案做啊
呵呵我说的就是这个意思，在应用层做做不是一个100%确认的机制
最终成功是写入状态数据库才算成功
需要有后续校验，发现失败情况再roll back
相当于“optimistic locking"
那不能100%确认, 这个就得看应用的场景了, 如果有后续逻辑依赖前面的数据就不能这么干, 如果不依赖就没啥事
@jimthematrix 感觉上，好多时候需要借鉴流程引擎的做法了，按异步来做。
应该可以适用某些场景
[ ](https://chat.hyperledger.org/channel/twg-china?msg=zciEFsrH5fnCKDP67) @liutc 这个用引擎流也很烦把, 不得恶心死
@CarlXK 同步的简单，但区块链这种广域共识的本质就决定了它不是个同步系统。没办法了。
能不能从设计上做到orderer返回确认就表示100%成功, 但是还没有打入区块, 等于把数据缓存异步打入区块
好像并不能...
orderer没有办法看state，也没有背书策略，所以没办法确认交易
要是让orderer做那些事，就又快回到0.6的架构了
要是让orderer做那些事，就又快回到0.6的架构了（orderer又变回了peer）
那现在只能这样看了, 低频的交易就设置1秒一个块, 高频交易根据场景来设置
那现在只能这样了, 低频的交易就设置1秒一个块, 高频交易根据场景来设置
设置成0.1秒行吗
你也可以设置每个块一笔交易
这样交易来了就打包
这样块太多, 如果你要加节点或者进行同步什么的就太麻烦了
这样块太多, 如果你要加节点或者进行同步什么的就太慢了
Has joined the channel.
大家好，我现在用Composer REST server开发，发现调用api的延迟很高，大概2s，而且吞吐量不行，发送大量请求的时候会被拒绝。这应该不是Hyperledger的问题吧，是不是Composer的性能问题？
还是我的配置不对？
Has joined the channel.
动态添加的组织，加入channel后 如何更新锚节点
自己构造了几个更新锚节点的配置 都被ordererer验证失败了
Has joined the channel.
2017-10-27 01:59:41.578 UTC [gossip/gossip] handleMessage -> WARN 488 Message GossipMessage: tag:EMPTY alive_msg:
这个日志有人碰到过没
@labcoinpoc 可以到 #composer 群里确认，不过2s是正常的，因为Composer REST是等交易成功验证以后才返回，而2s正好是区块间隔的时间（实际上API返回时间应该是在0-2s之间不等）
发送大量请求如果都是改变同一个状态变量，那只有每个区块的第一个交易会被接受
这是fabric设计本身的要求
@jimthematrix 受教了，我再去做一下测试，之前测试是直接忽略返回值，发送大量交易给rest server，我试试操作不同值看还会不会被拒绝。 如你所说是不是意味着如果按照当前设置，在某个商业逻辑下，比如更改A
客户的余额这种操作每2s只能执行一次？
@jimthematrix 试了一下，对不同值操作确实不会被拒绝了，非常感谢！
Has joined the channel.
Has joined the channel.
@labcoinpoc “客户的余额这种操作每2s只能执行一次“，https://github.com/hyperledger/fabric-samples/tree/release/high-throughput尝试用不同值的办法结合”pruning“来实现客户余额场景
@labcoinpoc “客户的余额这种操作每2s只能执行一次“，https://github.com/hyperledger/fabric-samples/tree/release/high-throughput 尝试用不同值的办法结合”pruning“来实现客户余额场景
@jimthematrix 正是我需要的，多谢！
@jimthematrix 我尝试照着例子改写composer的代码，使用数组存储更改纪录，但好像composer的数组在fabric中仍是一个key，测试的时候多个请求还是会被拒绝。我去composer频道再问问吧，看看有没有别的解决方法。
@jimthematrix 最近做了一个测试，发现一个问题，没用具体去查看代码，猜测是commiter的时候只检查了版本号的问题 ，能帮忙分析一下吗
fabric-samples里面 初始化a=100000 b=200 然后我把peer0.org1.example.com的stateleveldb拷贝出来 把b改成210 然后放回peer0.org1.example.com里面 查询peer0.org1 结果是210 查询peer0.org2 结果是200 然后我在peer0.org1上做了一笔a转b 10 结果所有结点全部都变成220 这是不是有问题阿
endorsement policy指定了吗？
原来是什么policy 就是什么policy 都是or的 只要自己背书就行
指定别人为背书应该是过不了 但是如果这样的话 背书节点不是可以联合起来作恶了吗
我正打算测试别人为背书
嗯，我猜测因为自己背书就行所以order会接受修改过的交易，然后分发给所有节点同步？
这种问题在0.6应该不会存在，0.6会同步worldstate，1.0的话看来只能靠大家背书了。本来共识就是少数服从多数，如果所有背书节点都联合起来那也是共识啊
如果说背书节点说了算 那没有办法 只是对于联盟中的其他成员 自己对了 还非要被诬陷成错的 这有点冤阿
假设我们的联盟是国企 银行 而他们并不是背书结点 那么现实中联盟所有成员都知道这个问题 肯定自己也要背书 那么所有人都成背书了 又回到0.6了
嗯，呼唤1.0的bft
正好我想请教一下，客户端需要根据背书策略来发请求吗？我现在用composer倒是支持背书策略，但因为直接打包了rest API所以这一块基本是黑盒。如果有两个组织，每个组织两个peer，背书策略要求每个组织一个peer背书，那客户端是先申请peer0.Org1和peer0.Org2，如果有超时的话再申请peer1，还是干脆向所有peer申请，尽可能多的接收背书结果？会不会第二个策略要好一些？
不考虑tps的话 我觉得 第二种 因为你发了peer申请就要执行背书 2个执行总比4个执行快 我是这么想的 不知道对不对
composer 还没玩过 干嘛用的
就是在fabric上抽象了一层商业网络定义，能用nodejs写，然后可以生成rest API，用app直接调API就行。用起来比直接在Fabric上做要简单一些吧
有guide的链接吗 发一个看看
https://hyperledger.github.io/composer/tutorials/developer-guide.html 官网上的教程有例子
composer
不用管底层的key value读写，抽象出来的就是participant asset 和 transaction三个概念
多谢
请教一个问题，不同的 chaincode 可以共享 worldstate 吗？
Has joined the channel.
可以，通过chaincode间调用就可以了
也就是说对于worldstate的访问还是需要记录该worldstate的chaincode提供接口？
@ylsGit
我理解是这样的
因为worldstateDB中完整的key是ChannelName+chaincodeNam+chaincode中设置的key，这样连接成的
所以认为不同的chaincode设置的state其key实不一样的，自己存的state只能自己能取出来
哦 原来是这样 受教了。我本来的想法是同一个channel下都是共享worldstate的，在一个 chaincode中实现管理功能，在另一个chaincode中实现使用的功能，昨天发现读取不到，所以不太清楚是不能这么做还是我在install chaincode 中配置的不对
不知对不对，但我在源码里还没找到将ChannelName连接进去的代码:joy:
Has joined the channel.
目前只能对应chaincode来读写；通过管理chaincode可以防护数据被无权限他人操作。
@here Dear all, we will cancel the group meeting this week due to the Hyperledger summit, pls help discuss offline and continue the work items, thanks!
See you in another two weeks! Looking forward to your experience sharing for the summit!
@baohua 我看你那本书里面写的chaincode之间调用还只支持query，现在可以支持invoke（写操作）了？
for different channel, the answer should be still no writing.
@baohua orderer访问kafka的时候需要token吗？这个token在哪里设置的
在tls关闭的时候
i don't think so, kafka natively doesn't require a token to access.
这样的话，随便哪个order都能连上kafka？
按照github上的那个docker-compose配置文件，用docker-compose启动的时候，orderer能从kafka上取到数据，直接使用docker的时候，不能，我怀疑是不是kafka需要凭证才能访问
Has joined the channel.
@liutc 支持的
@baohua @Haghighat please look at the patch for all-in-one doc again, I created the jira issue to integrate dashboard with agent created fabric network. I think when we have a clearer idea how this is done, the document can be moved around.
Has joined the channel.
https://gerrit.hyperledger.org/r/#/c/15133/
Has joined the channel.
请问如果需要某个组织的所有peer都背书，背书策略如何指定？
有人在用区块链浏览器的项目吗 block-explorer
我在用
启动项目的时候报个错，能帮我看一下吗，谢谢了
Clipboard - November 7, 2017 10:46 AM
我没用TSL，你是不是开了TSL？
用node启动的时候后台报错，然后浏览器没有生成块的信息。
开了tls
不开tls，能启动吗
嗯，tls
你用的的是fabric那个版本
我印象中好像explorer中说了不支持tls？
我按照网上教程下的是1.02
现在看来是支持了
是吗。额
最新教程上
Clipboard - November 7, 2017 10:49 AM
配置把tls打开了
1.0.0
嗯，我fabric那边也没配tls，所以没有开
```
{
"host":"localhost",
"port":"8080",
"channelsList": ["composerchannel"],
"GOPATH":"../artifacts",
"keyValueStore":"/tmp/fabric-client-kvs",
"eventWaitTime":"30000",
"enableTls":false,
"users":[
{
"username":"admin",
"secret":"adminpw"
}
],
"mysql":{
"host":"10.19.193.110",
"port":"13306",
"database":"fabricexplorer",
"username":"root",
"passwd":"123456"
}
}
```
我没有开tls，刚试了一下
Clipboard - November 7, 2017 11:17 AM
又报另一错误
:worried:、
这个看起来像是keyvalue store设置的问题
我的证书和key是自己新做的，没有用默认的，
我去看下我的证书
下面那个cannot read low报错可以不用管，不影响
@qingsongGuo 你的证书有问题 你用于交易的用户证书 没法被认证
证书使用cryptogen工具生成的
你应该ca启动的时候 不是用的 你实际想用的ca证书
打开ca启动的 yaml文件 里面ca启动的时候 会用到cert 和key
那个地方要改成 你实际的那个ca的cert和key
我去看看
还需要确认 你发送proposal的用户 是你从ca注册得到的 还是你自己直接加载本地的证书的
我看helper.js里是从配置文件读的用户名和密码啊，
```
var getAdminUser = function(userOrg) {
var users = config.users;
var username = users[0].username;
var password = users[0].secret;
var member;
var client = getClientForOrg(userOrg);
```
@qingsongGuo 好像你的配置文件里没指定？
我用的是composer，启动的时候就enroll了admin
Clipboard - November 7, 2017 2:28 PM
这是config.json那个配置文件
Clipboard - November 7, 2017 2:30 PM
@zhuxubin01 是该这两个地方吗，我把这两个地方的key。改成了用 。./byfn -m generate 脚本后生成的 key
然后还是报错
一样的错误
如果这里之前就用错了的话，是不是在fabric启动的时候加入peer就会报错？
@qingsongGuo 贴一下你的network-config.json
Clipboard - November 7, 2017 2:43 PM
区块链网络是正常的
你清理过这个目录吗 `rm -rf /tmp/fabric-client-kvs_peerOrg*`
@labcoinpoc 而且每次启动，证书都市重新生成的
没有清理过
清理一下然后重起看看，那个目录下是旧的证书
没有这个目录呀
我用的是first-network这个区块链网络
这个目录是explorer建的
Clipboard - November 7, 2017 2:50 PM
没有找到你说的这个目录
我找找，我把explorer塞到docker里了，或许做过映射
Clipboard - 2017年11月7日午後3時54分
我去查查，莫非现在版本变了？
可能是
现在版本。在关闭区块链网络时，使用的脚本 。./byfn -m down
这个脚本会删除所有的证书文件
我好像有点印象，因为这里存着旧的证书，新的覆盖不了会出错，所以我启动容器的时候加了一句
不是那些证书，我说的这些是explorer起来以后才有的
Clipboard - November 7, 2017 2:58 PM
不是这些，我上面的图是已经起来explorer的容器了，在容器里面的目录
区块链网络关闭后，crypto-config。这个文件夹就饿被删了
你找找服务器根目录/tmp下
好饿，我看看。找到后把你说的那个文件删了吗
嗯，删了没事，下次起来还会建
Clipboard - 2017年11月7日午後4時3分
就是你配置的第五行的路径，你那应该有
Clipboard - 2017年11月7日午後4時5分
我这是没问题的
能贴一下你的容器吗
Clipboard - November 7, 2017 3:09 PM
Clipboard - 2017年11月7日午後4時9分
我没有explore的容器呀
我自己做的
因为要打包部署到别的地方，我就都塞到docker里了
```
blockchain-explorer:
tty: true
container_name: blockchain-explorer
image: blockchain-explorer:latest
environment:
- NPM_CONFIG_LOGLEVEL=warn
working_dir: /etc/blockchain-explorer
command: sh -c 'rm -rf /tmp/fabric-client-kvs_peerOrg* && node main.js'
ports:
- 8080:8080
volumes:
- ../hlfv1/composer/crypto-config:/etc/blockchain-explorer/crypto-config
- ./config.json:/etc/blockchain-explorer/config.json
- ./network-config.json:/etc/blockchain-explorer/app/network-config.json
depends_on:
- mysql
```
我用这个浏览器项目，我看到它每次启动区块链网络，都是重新生成的证书和文件，还有初始区块，交易信息
这些每次启动都重新生成
要是每次启动都需要配置，教程里一点提示都没有呀
他只是写在脚本里了，实际没必要
我这是稍微早一点的版本，没有first-network,他默认让用的是svt
里面有脚本每次换key的
```
function replacePrivateKey () {
ARCH=`uname -s | grep Darwin`
if [ "$ARCH" == "Darwin" ]; then
OPTS="-it"
else
OPTS="-i"
fi
#docker-compse-e2e.yaml
cp docker-compose-e2e-template.yaml docker-compose-e2e.yaml
CURRENT_DIR=$PWD
cd crypto-config/peerOrganizations/org1.example.com/ca/
PRIV_KEY=$(ls *_sk)
cd $CURRENT_DIR
sed $OPTS "s/CA1_PRIVATE_KEY/${PRIV_KEY}/g" docker-compose-e2e.yaml
cd crypto-config/peerOrganizations/org2.example.com/ca/
PRIV_KEY=$(ls *_sk)
cd $CURRENT_DIR
sed $OPTS "s/CA2_PRIVATE_KEY/${PRIV_KEY}/g" docker-compose-e2e.yaml
#docker-compose-cli.yaml
cp docker-compose-cli-template.yaml docker-compose-cli.yaml
cd crypto-config/peerOrganizations/org1.example.com/ca/
PRIV_KEY=$(ls *_sk)
cd $CURRENT_DIR
sed $OPTS "s/CA1_PRIVATE_KEY/${PRIV_KEY}/g" docker-compose-cli.yaml
cd crypto-config/peerOrganizations/org2.example.com/ca/
PRIV_KEY=$(ls *_sk)
cd $CURRENT_DIR
sed $OPTS "s/CA2_PRIVATE_KEY/${PRIV_KEY}/g" docker-compose-cli.yaml
}
```
:nerd:我再研究一下
好像好多人都遇到问题了
我当时也花了2个礼拜搞定这个，后面还有别的问题，比如peer list，我看explorer里说是马上要修，实际上最近他只修了peer数的问题
我当时也花了2个礼拜搞定这个，后面还有别的问题，比如peer list，我看explorer频道里说是马上要修，实际上最近他只修了peer数的问题
list还是写死的
:nerd:一步步来吧
我改了点代码，反正就是展示用，放那就没再管了
我去 explorer频道里。都翻到8月份的聊天记录了，也没找到解决办法。提问题的倒不少:smile:
@qingsongGuo 你怎么启动的 一键启动的那个好像是每次都生成密钥的
用脚本 ./byfu -m up
就是一键启动吧
那你应该每次都过不了
你先看看脚本 里面他每次都生成新的证书密钥
我刚才生成秘钥之后，改的yam文件
也没过
改了没有用
你改了 他每次都又重新生成 那等于没改
仔细看看byfu 里面他会生成证书密钥
你现在去看看 是不是又跟你的实际证书 密钥不一样了
看org 下面 ca目录下的私钥的名字 和你启动的时候的那个私钥的名字
看来svt里面的换密钥脚本没有移到first-network那边
是不一样了
我看能不能把脚本改下，不让它重新生成
有阿
```
# The next steps will replace the template's contents with the
# actual values of the private key file names for the two CAs.
CURRENT_DIR=$PWD
cd crypto-config/peerOrganizations/org1.example.com/ca/
PRIV_KEY=$(ls *_sk)
cd "$CURRENT_DIR"
sed $OPTS "s/CA1_PRIVATE_KEY/${PRIV_KEY}/g" docker-compose-e2e.yaml
cd crypto-config/peerOrganizations/org2.example.com/ca/
PRIV_KEY=$(ls *_sk)
cd "$CURRENT_DIR"
sed $OPTS "s/CA2_PRIVATE_KEY/${PRIV_KEY}/g" docker-compose-e2e.yaml
# If MacOSX, remove the temporary backup of the docker-compose file
if [ "$ARCH" == "Darwin" ]; then
rm docker-compose-e2e.yamlt
fi
}
```
可能脚本哪里出问题了，不行还是自己写吧
把它生成密钥的部分改下就行 如果存在就不生成
Clipboard - November 7, 2017 3:53 PM
脚本跟之前版本的不一样的好像，改改试试吧
不知道能不能行
跟ca的key没关系，我试了好几次。docker-compose-cli.yaml文件里面配的和实际一致。启动脚本也改为用-cli.yaml文件启动
一样的报错
tmp下那个文件夹清了没？
没有tmp文件夹呀
Clipboard - November 7, 2017 5:27 PM
没有:sweat_smile:
tls设为false了，应该和ca的key值没关系了
就是不知道为啥还报错
正在找
tls设置 2边应该需要设置成一样吧
在根目录下
都设成false了
[ ](https://chat.hyperledger.org/channel/twg-china?msg=FQkZCxnh7DxpnThGo) @zhuxubin01 前一阵RC账号出问题了不能登录，直到昨天早上才修复。回答你的问题，首先如果背书策略是设置到需要所有org的签名（默认策略是只需要一个签名），那这个交易会被拒绝（你只有org1的签名）。我猜你的实验是用的默认策略，那么这个过程是SDK收到org1的proposal response以后，送到orderer然后在每个节点通过VSCC验证，VSCC简单比较rwset的版本号，确认没变，然后看也符合背书策略，就把writeset的值提交了。所以220是预期的结果
要想加强对共享账本的保护，防止被恶意节点或者被攻击的节点篡改，比较直接的办法是两个方面：1）每次交易提交给多个org的多个节点背书，2）背书策略要求100%的channel成员签名
@labcoinpoc ^^^
[ ](https://chat.hyperledger.org/channel/twg-china?msg=Fq8z76FJBnW4n6m8G) @labcoinpoc 目前的办法只有利用背书策略里的"identity"类而不是通常的“role”类，“identity”是对应每个具体的certificate，这样就可以把所有org里面的节点的signing certificate列出来作为背书策略的签名列表。不过问题有两个，1）node SDK暂时不支持，2）容错性差（一个节点宕机了就没办法玩了）
@jimthematrix 感谢解答！如你所说，确实指定全部certificates可能不是一个好主意，我想如果按照文档中的语法 T(2, 'A', 'B', 'C') 指定ABC为具体的certificate，能提供1/3的容错性？另外不知道AND( 'Org1.member', 'Org1.member', 'Org1.member') 会被解释为需要三个不同的member还是同一个member被check三次。我去测试一下。
"T(2, 'A', 'B', 'C') 指定ABC为具体的certificate，能提供1/3的容错性?" - :thumbsup:
Has joined the channel.
原来组织在这里:blush:
@lcj :wink:utc+9 日本还是韩国？
日本
me too
哈哈哈
你也正在做fabric吗？
学习尝试中
偶偶，加油！！
以后有不会的地方，会向你多请教哦:pray:
不敢当，这里牛人很多，我也是新手，一起努力吧
一起加油！！！
@jimthematrix 我在尝试写endorsement policy，请问指定具体identity的语法是什么样的？ 以字符串的形式传入 cert 和 private key? composer应该是使用nodejs的sdk传入endorsement policy，那么是不是目前还不能指定identity？
@lcj welcome :)
@baohua 谢谢杨老师，请多关照！！:pray:
我尝试了这样的endorsement policy:
```
```
我尝试了这样的endorsement policy:
```
{
"identities": [
{
"role": {
"name": "member",
"mspId": "Org1MSP"
}
}
],
"policy": {
"3-of": [
{
"signed-by": 0
},
{
"signed-by": 0
},
{
"signed-by": 0
},
{
"signed-by": 0
}
]
}
}
```
好像是起作用的，如果endorsement数量不够3个的话就会触发ENDORSEMENT_POLICY_FAILURE，但是Composer存在一些问题，如果在连接配置中配置了4个节点的地址，如果其中一个无响应composer就报错停止。。。实际上这种情况应该允许提交
Has joined the channel.
```2017-11-03 13:51:38.206 UTC [orderer/kafka] startThread -> CRIT 018 [channel: prodchannel1] Cannot set up channel consumer = kafka server: The requested offset is outside the range of offsets maintained by the server for the given topic/partition.
panic: [channel: prodchannel1] Cannot set up channel consumer = kafka server: The requested offset is outside the range of offsets maintained by the server for the given topic/partition.
goroutine 11 [running]:
panic(0xb30c60, 0xc42036c180)
/opt/go/src/runtime/panic.go:500 +0x1a1
github.com/hyperledger/fabric/vendor/github.com/op/go-logging.(*Logger).Panicf(0xc4201cd5c0, 0xc70b70, 0x31, 0xc4205760c0, 0x2, 0x2)
/opt/gopath/src/github.com/hyperledger/fabric/vendor/github.com/op/go-logging/logger.go:194 +0x127
github.com/hyperledger/fabric/orderer/kafka.startThread(0xc42008b8c0)
/opt/gopath/src/github.com/hyperledger/fabric/orderer/kafka/chain.go:173 +0xafb
created by github.com/hyperledger/fabric/orderer/kafka.(*chainImpl).Start
/opt/gopath/src/github.com/hyperledger/fabric/orderer/kafka/chain.go:94 +0x3f 我们的fabric网络中有3个orderer，其中有一个节点因物理机故障造成账本没有同步，现在一启动这个orderer就会报以上错误，感觉应该是kafka日志对应部分已经清除了导致的，请问有什么解决办法吗？ ```
2017-11-03 13:51:38.206 UTC [orderer/kafka] startThread -> CRIT 018 [channel: prodchannel1] Cannot set up channel consumer = kafka server: The requested offset is outside the range of offsets maintained by the server for the given topic/partition.
panic: [channel: prodchannel1] Cannot set up channel consumer = kafka server: The requested offset is outside the range of offsets maintained by the server for the given topic/partition.
goroutine 11 [running]:
panic(0xb30c60, 0xc42036c180)
/opt/go/src/runtime/panic.go:500 +0x1a1
github.com/hyperledger/fabric/vendor/github.com/op/go-logging.(*Logger).Panicf(0xc4201cd5c0, 0xc70b70, 0x31, 0xc4205760c0, 0x2, 0x2)
/opt/gopath/src/github.com/hyperledger/fabric/vendor/github.com/op/go-logging/logger.go:194 +0x127
github.com/hyperledger/fabric/orderer/kafka.startThread(0xc42008b8c0)
/opt/gopath/src/github.com/hyperledger/fabric/orderer/kafka/chain.go:173 +0xafb
created by github.com/hyperledger/fabric/orderer/kafka.(*chainImpl).Start
/opt/gopath/src/github.com/hyperledger/fabric/orderer/kafka/chain.go:94 +0x3f 我们的fabric网络中有3个orderer，其中有一个节点因物理机故障造成账本没有同步，现在一启动这个orderer就会报以上错误，感觉应该是kafka日志对应部分已经清除了导致的，请问有什么解决办法吗？
```2017-11-03 13:51:38.206 UTC [orderer/kafka] startThread -> CRIT 018 [channel: prodchannel1] Cannot set up channel consumer = kafka server: The requested offset is outside the range of offsets maintained by the server for the given topic/partition.
panic: [channel: prodchannel1] Cannot set up channel consumer = kafka server: The requested offset is outside the range of offsets maintained by the server for the given topic/partition.
goroutine 11 [running]:
panic(0xb30c60, 0xc42036c180)
/opt/go/src/runtime/panic.go:500 +0x1a1
github.com/hyperledger/fabric/vendor/github.com/op/go-logging.(*Logger).Panicf(0xc4201cd5c0, 0xc70b70, 0x31, 0xc4205760c0, 0x2, 0x2)
/opt/gopath/src/github.com/hyperledger/fabric/vendor/github.com/op/go-logging/logger.go:194 +0x127
github.com/hyperledger/fabric/orderer/kafka.startThread(0xc42008b8c0)
/opt/gopath/src/github.com/hyperledger/fabric/orderer/kafka/chain.go:173 +0xafb
created by github.com/hyperledger/fabric/orderer/kafka.(*chainImpl).Start
/opt/gopath/src/github.com/hyperledger/fabric/orderer/kafka/chain.go:94 +0x3f 我们的fabric网络中有3个orderer，其中有一个节点因物理机故障造成账本没有同步，现在重新启动这个orderer, parent consumer可以设置成功，但channel consumer似乎没有设置成功（正常启动会有channel consumer set up successfully, Start phase completed之类的），过段时间就会报以上*offset out of range*错误，感觉应该是kafka日志对应部分已经清除了导致的，但是又没有搞清楚为什么channel consumer不能设置成功，请问有人知道吗，有什么解决办法吗？```
``` 2017-11-03 13:51:38.206 UTC [orderer/kafka] startThread -> CRIT 018 [channel: prodchannel1] Cannot set up channel consumer = kafka server: The requested offset is outside the range of offsets maintained by the server for the given topic/partition.
panic: [channel: prodchannel1] Cannot set up channel consumer = kafka server: The requested offset is outside the range of offsets maintained by the server for the given topic/partition.
goroutine 11 [running]:
panic(0xb30c60, 0xc42036c180)
/opt/go/src/runtime/panic.go:500 +0x1a1
github.com/hyperledger/fabric/vendor/github.com/op/go-logging.(*Logger).Panicf(0xc4201cd5c0, 0xc70b70, 0x31, 0xc4205760c0, 0x2, 0x2)
/opt/gopath/src/github.com/hyperledger/fabric/vendor/github.com/op/go-logging/logger.go:194 +0x127
github.com/hyperledger/fabric/orderer/kafka.startThread(0xc42008b8c0)
/opt/gopath/src/github.com/hyperledger/fabric/orderer/kafka/chain.go:173 +0xafb
created by github.com/hyperledger/fabric/orderer/kafka.(*chainImpl).Start
/opt/gopath/src/github.com/hyperledger/fabric/orderer/kafka/chain.go:94 +0x3f
我们的fabric网络中有3个orderer，其中有一个节点因物理机故障造成账本没有同步，现在重新启动这个orderer, parent consumer可以设置成功，但channel consumer似乎没有设置成功（正常启动会有channel consumer set up successfully, start phase completed之类的），过段时间就会报以上offset out of range错误，感觉应该是kafka日志对应部分已经清除了导致的，但是又没有搞清楚为什么channel consumer不能设置成功，请问有人知道吗，有什么解决办法吗？
Has joined the channel.
大家好，第一次到这里，冒个泡，请多关照，嘻嘻
:flag_cn:
大家早上好，请教大家一个问题，启动peer的时候，会设定MSP的路径，启动后会加载这些msp信息。我的问题是，如果证明书重新做成了，有没有不容器重新启动容器，可以直接更新的方法？调用系统chaincode？
重新做了证书不就是一个新的peer了吗，作为新peer加入就可以吧
@labcoinpoc 证书是可以吊销和更新的
@labcoinpoc 比如证书到期的时候
这个？
```
Reenrolling an Identity
Suppose your enrollment certificate is about to expire or has been compromised. You can issue the reenroll command to renew your enrollment certificate as follows.
export FABRIC_CA_CLIENT_HOME=$HOME/fabric-ca/clients/peer1
fabric-ca-client reenroll
```
@labcoinpoc 这只是重新注册证书，执行完这个命令会返回给你新的证书，然后你拿到这个证书，如果更新peer的证书，就不知道了。
我理解你是说peer要用一个全新创建的证书？那没法通过ca的认证吧
@labcoinpoc ca只是一个发放证书的机构，发完了就不管了
@labcoinpoc 是的，就是要给peer全新的证书
@labcoinpoc 目前，如果生成出始块之前，做出新的证书，给peer，然后生成初始块，启动peer，跑脚本，这样的过程我实验了，没有问题。就是系统运行中，更新证书没有思路
我认为如果想要新证书，应该找ca申请，而不是自己创建，在网络创建之前就做出的那些证书也是因为你先提供了网络结构，按照证书的生成规则生成的。其实先启动CA，然后再一个一个注册也是一样的
`http://hyperledger-fabric-ca.readthedocs.io/en/latest/users-guide.html#registering-a-new-identity`
http://hyperledger-fabric-ca.readthedocs.io/en/latest/users-guide.html#registering-a-new-identity
@labcoinpoc 更新证书找CA是没有问题的，但是CA给你最新的时候，是不会帮你更新到系统里面的，需要你自己去做
@labcoinpoc 你一直没明白我的意思，证书不只是第一次启动的时候做成的，系统运行途中也可以更新的，那么这个时候，你拿到最新的证书，要如何去更新？？这是问题的关键
放在peer配置的CORE_PEER_MSPCONFIGPATH下面吧
@labcoinpoc CORE_PEER_MSPCONFIGPATH只是设置了一个路径，这个路径下会存放很多文件，公钥和私钥。如何分别去更新，还是不知道。。。。
@labcoinpoc 如果容器可以重新加载这个路径，自动更新也可以。那样的话就只能把容器删除再启动。。这样做非常不好。
@labcoinpoc 所以最终的问题就是如何动态加载配置文件。
容器倒是能做到，用volumes映射到外部的路径就可以
msp的目录格式是固定的，要更新也只是换证书和私钥两个
@labcoinpoc 这种msp信息应该是加载到内存里的，虽然文件映射更新，但是如何修改内存信息还是个问题。另外，公钥还要提供给其他节点，如何提供还是个问题。。。
Has joined the channel.
终于找到组织了
Has joined the channel.
上来向各位问个好
[ ](https://chat.hyperledger.org/channel/twg-china?msg=nMTp8hGkN9qEgaZNd) @nauqnew 3个orderer连的同一个kafka？ 我之前一个orderer连接一个Kafka集群，机器重启后，Kafka数据丢失（Kafka存盘时间设置太长），导致orderer获取的offset大于kafka保存的数据。
@barry_liang in fabric, kafka should be set to keep all messages and store permanently. otherwise, order node may not be able to pull missing messages currently.
@baohua 是的，我的意思是kafka flush 硬盘时间设置太长，机器直接断电的话导致Kafka最新数据还没有存硬盘，数据丢失。Kafka重启后记录的数据比orderer少。
i remember there's recommendation to force strict ack settings in kafka: hyperledger-fabric.readthedocs.io/en/latest/kafka.html. feel free to have a look.
@baohua thanks，
大家有遇到ca生成的证书时间，比主机时间慢家分钟的吗？比如主机时间10:20,证书Not Before时间是10:15.我确认了，主机和容易还有数据库时间都是同步的。
主机时间10:20的情况下，用cryptogen生成的证书时间都在10:20分以后，但是用ca生成的证书在10:20之前
[ ](https://chat.hyperledger.org/channel/twg-china?msg=rtZaXQwdJy6Z4bHdt) @lcj 这个有说明的,
[ ](https://chat.hyperledger.org/channel/twg-china?msg=WJHEayeHSEDMmqy5M) @barry_liang kafka是集群，应该是日志删了，我现在的疑问是，这几个orderer的ledger是不是都不一样，因为切块的时候有orderer自己的签名，一个orderer落后之后，数据能不能从其它orderer拷贝过去？
Has joined the channel.
@asaningmaxchain 非常感谢您的回答，能否提示一下，在什么地方可以看到这个说明。
@lcj 等一下我找找给你回复
@asaningmaxchain :pray:
大家早上好，和大家探讨一个关于ca的问题
-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
先用cryptogen把所有证书和私钥，tls文件都生成(这时没有做成初始块)。
然后，用ca重新生成了admin，peer0,peer1的证书和私钥，并替换相应路径下的文件，
然后，做成了初始块，启动各个容器。
接下来执行e2e脚本的时候，在执行到Instantiating的时候，chaincode容器里面出现下面的错误。
感觉是tls的问题，于是，我把orderer,peer,peer-cli容器的tls都设置了false，重新执行一遍e2e脚本的时候，一切正常结束了。
我想问，用ca生成的证书会影响tls吗？他们是两个分支啊。
Instantiating chaincode on org1/peer0...
CORE_PEER_TLS_ROOTCERT_FILE=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org1.example.com/peers/peer0.org1.example.com/tls/ca.crt
CORE_PEER_TLS_KEY_FILE=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org1.example.com/peers/peer0.org1.example.com/tls/server.key
CORE_PEER_LOCALMSPID=Org1MSP
CORE_VM_ENDPOINT=unix:///host/var/run/docker.sock
CORE_PEER_TLS_CERT_FILE=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org1.example.com/peers/peer0.org1.example.com/tls/server.crt
CORE_PEER_TLS_ENABLED=true
CORE_PEER_MSPCONFIGPATH=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org1.example.com/users/Admin@org1.example.com/msp
CORE_PEER_ID=cli
CORE_LOGGING_LEVEL=DEBUG
CORE_PEER_ADDRESS=peer0.org1.example.com:7051
2017-11-13 09:01:51.621 UTC [shim] userChaincodeStreamGetter -> ERRO 001 Error trying to connect to local peer: x509: certificate signed by unknown authority (possibly because of "x509: ECDSA verification failure" while trying to verify candidate authority certificate "tlsca.org1.example.com")
Error starting Simple chaincode: Error trying to connect to local peer: x509: certificate signed by unknown authority (possibly because of "x509: ECDSA verification failure" while trying to verify candidate authority certificate "tlsca.org1.example.com")
tls在传输层，生成证书的时候在tlsca目录下，ca生成的证书是签名交易的，在cacerts下
tls在传输层，生成证书的时候在tlsca目录下，ca生成的证书是签名交易的，在signcerts下
tls在传输层，生成证书的时候在tlscacerts目录下，ca生成的证书是签名交易的，在signcerts下
@labcoinpoc 谢谢，[生成证书的时候在tlscacerts目录下]是什么意思？
cryptogen生成的目录结构
这个我知道
cryptogen生成的目录结构我很清晰，问题在于，ca生成的证书会影响到tls吗？
两者应该没有关系
不会，tls只在传输层，跟传什么内容无关
那我现在实验的结果就是，ca生成的证书影响tls了
你在最一开始没有更换证书之前是运行成功的吗
是成功的
看了一下你的环境变量，似乎msppath用的admin，peeraddress用的peer0，会不会是这个问题？
哦，这是cli的设定，那没啥问题
@labcoinpoc 是的，tls的设定我没有改动，只是改动msp下面的东西了
有人通过main函数直接启动peer的吗？
Has joined the channel.
Has joined the channel.
报道
Has joined the channel.
大家好，我想问的是如何使用fabric CA实现动态加入peer，还有是否可以通过链码进行动态添加peer？
@labcoinpoc 昨天的问题解决了，和tlsca没有关系，是我重新运行的时候，忘记把上一次chaincode录下的镜像文件删除了。
@zhoujunshan 动态加入就是给peer颁发私钥和证明书，然后这个peer启动。你现在会用ca发证明书吗？
@lcj 发证书是enroll 命令保存的证书文件吗
[ ](https://chat.hyperledger.org/channel/twg-china?msg=PdguraTkjr6mwB5mC) @zhoujunshan 这个命令可以获得证书，在fabric-ca-server中它返回来的
@tedljw 是的，然后你去找对应关系，把相应的文件替换一下
@tedljw http://blog.csdn.net/weixin_36630015/article/details/78480809
@tedljw 这是我的个人空间，里面的内容你可以参考一下
ca 这东西很多人都不会用，我最近在调查，希望能给大家带来邦族
[ ](https://chat.hyperledger.org/channel/twg-china?msg=PdguraTkjr6mwB5mC) @zhoujunshan 在fabric-ca-server中的handleEnroll函数内，"cert, err := ca.enrollSigner.Sign(req.SignRequest)" 这个函数获得证书 ，bese64加密后放在resp中给fabric-ca-client，然后fabric-ca-client获得resp中的证书，在runEnroll函数中err = ID.Store()这一步保存下来证书
请教群里的大大，你们是如何在多台主机上部署Fabric集群的？
[ ](https://chat.hyperledger.org/channel/twg-china?msg=XpJh8sZRio8pp9iYd) @marryton007 我知道的有3中方法，第一种是利用/etc/hosts，第二种利用docker swarm，第三种利用k8s
朋友们，fabric-ca-server-config.yaml里面有registry项目，
在registry里面可以定义一个用户，这个用户的type是自定义的吧？比如我定义一个cooker
registry:
# Maximum number of times a password/secret can be reused for enrollment
# (default: -1, which means there is no limit)
maxenrollments: -1
# Contains identity information which is used when LDAP is disabled
identities:
- name: admin
pass: adminpw
type: client
affiliation: ""
maxenrollments: -1
attrs:
hf.Registrar.Roles: "client,user,peer,validator,auditor"
hf.Registrar.DelegateRoles: "client,user,validator,auditor"
hf.Revoker: true
hf.IntermediateCA: true
当然hf.Registrar.Roles里面也得有cooker这个值
@tedljw 第二种是指docker swarm mode吧？ 第一种没有尝试过，改hosts文件是什么意思？
@tedljw 在多机Fabric集群里，有没有试过重启某个节点的docker Daemon或是reboot这台主机？这样操作之后有出现过部署的chaincode无法查询的情况吗？
[ ](https://chat.hyperledger.org/channel/twg-china?msg=7heCKB4Nu6p8ssY5w) @marryton007 该/etc/hosts,也就是让peer，orderer，ca之间知道通信的地址是什么，做一下dns，不过这个设置需要让dokcer变成主机模式
[ ](https://chat.hyperledger.org/channel/twg-china?msg=fv5Ek2a4ymF5NByBa) @marryton007 docker restart后，chaincode容器是exit的状态，你做一下交易操作，链代码容器就会up了。你的情况貌似没有，我用的是v1.0的版本，你用的是什么版本。
@tedljw 我用的是1.0.0版，先后用k8s和docker swarm mode 2种方式搭建了fabric1.0的集群。https://github.com/hainingzhang/articles/tree/master/fabric_on_kubernetes
https://github.com/ChoiSD/hyperledger_on_swarm
他们都有一个问题，就是集群中的某个节点(k8s节点或swarm node)重启，原来部署好的链就丢失了，我猜测可能是k8s和swarm的内部调度机制导致Docker容器被干掉，又重新启动了新的容器，但数据没有备份或(迁移)。
@marryton007 听别人说过，是有这种情况，chaincode的状态不好控制
@lcj 我正准备把容器内的数据用volumn的形式导出来，不再放到容器里了，这样再试试。
Has joined the channel.
peer签名策略，算一种共识么
貌似大家说起共识，只是说orderer上面
[ ](https://chat.hyperledger.org/channel/twg-china?msg=xou3iGTRFRG29o2av) @leo 我个人感观上觉得，peer上的escc，vscc，orderer上的solo和kafka，共同组成了fabric的共识策略。。。。不知道大家怎么看
orderer现在只是简单的排序，无论kafka和solo都是一个目的，就是排序出块。但是真正决定交易是否有效的，确是committer的职责。我认为交易是否有效，才是共识的作用吧？
比特币只记正确的交易在块上，而fabric的账本里面无效交易也会记录上去。所以共识的发生点应该在committer层面而不是出块的层面，不知道我这样理解是不是对的
[ ](https://chat.hyperledger.org/channel/twg-china?msg=JdGcWRMjg3KoFWWWG) @leo 我有点疑惑，你说的committer是指fabric的哪部分，是orderer和peer上写块代码的那部分？？？
committer是peer的一种角色，负责对区块和里面的交易进行验证，并记账的
@leo 但现在的”共识“的算法代码是在ordered中
@RocMax 所以这就是我想问的问题，到底什么是共识？背书策略算不算共识？
[ ](https://chat.hyperledger.org/channel/twg-china?msg=Sqr2AcNTGEfw2R8SE) @leo 我认为算的。。。总不能就是做个排序吧
背书策略的检查似乎是在commit阶段，由peer完成的
大家好，我在看Fabric的权限这块，了解到权限是由策略（Policy）来定义的，有默认的策略，然后我想能不能自定义策略时，找不到答案，而是在文档中看到这样一句：在Fabric的早期版本中，我们计划提供默认策略，用coauthdsl包的策略框架定义，看来目前改策略可行性不高。是这样吗？
另外，我在看CA注册用户时，看到role参数，但是没有找到更详细的资料，以便以解它可以定义哪些角色，以及角色的区别
@RocMax 是的，endorsement由committer完成，so my question is，whether endorsement policy is some kind of consensus
Has joined the channel.
@here Dear all, we will have group meeting at 10AM this Wednesday morning, pls help update the agenda/attendee at https://wiki.hyperledger.org/groups/twgc/meeting/2017-11-22 (Notice we are using the new zoom system), thanks!
各位，orderer和endorser的IP可以通过config_update修改吗？
@tedljw 在使用Docker swarm方式搭建多主机Fabric集群时，需要将peer,orderer,CA中的数据导出来放在磁盘上，不然会出现，如果集群中某台机器重启后整个链无法访问的问题。可以参考这个项目https://github.com/mrwenhui/hyperledger_on_swarm
谁遇到这个问题？fatal error: unexpected signal during runtime execution
[signal SIGSEGV: segmentation violation code=0x1 addr=0x63 pc=0x7f95608b0259]
runtime stack:
runtime.throw(0xc6da92, 0x2a)
/opt/go/src/runtime/panic.go:566 +0x95
runtime.sigpanic()
/opt/go/src/runtime/sigpanic_unix.go:12 +0x2cc
goroutine 24 [syscall, locked to thread]:
runtime.cgocall(0x9efc20, 0xc4207f25f8, 0xc400000000)
/opt/go/src/runtime/cgocall.go:131 +0x110 fp=0xc4207f25b0 sp=0xc4207f2570
net._C2func_getaddrinfo(0x7f95500008c0, 0x0, 0xc4203201e0, 0xc42002c020, 0x0, 0x0, 0x0)
??:0 +0x68 fp=0xc4207f25f8 sp=0xc4207f25b0
net.cgoLookupIPCNAME(0xc4201a7a70, 0x6, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0)
/opt/go/src/net/cgo_unix.go:146 +0x37c fp=0xc4207f2718 sp=0xc4207f25f8
net.cgoIPLookup(0xc4202e0180, 0xc4201a7a70, 0x6)
/opt/go/src/net/cgo_unix.go:198 +0x4d fp=0xc4207f27a8 sp=0xc4207f2718
runtime.goexit()
/opt/go/src/runtime/asm_amd64.s:2086 +0x1 fp=0xc4207f27b0 sp=0xc4207f27a8
created by net.cgoLookupIP
/opt/go/src/net/cgo_unix.go:208 +0xb4
goroutine 1 [IO wait]:
net.runtime_pollWait(0x7f9560b2a430, 0x72, 0x0)
/opt/go/src/runtime/netpoll.go:160 +0x59
net.(*pollDesc).wait(0xc4202f8300, 0x72, 0xc4201c5c00, 0xc42000c150)
/opt/go/src/net/fd_poll_runtime.go:73 +0x38
net.(*pollDesc).waitRead(0xc4202f8300, 0x1225ca0, 0xc42000c150)
/opt/go/src/net/fd_poll_runtime.go:78 +0x34
net.(*netFD).accept(0xc4202f82a0, 0x0, 0x1223ce0, 0xc4200c8f40)
/opt/go/src/net/fd_unix.go:419 +0x238
net.(*TCPListener).accept(0xc4201aa600, 0xc4201c5ce8, 0xc4201c5cf8, 0x459800)
/opt/go/src/net/tcpsock_posix.go:132 +0x2e
net.(*TCPListener).Accept(0xc4201aa600, 0xcb9d50, 0xc420284780, 0x122d120, 0xc4201aa600)
/opt/go/src/net/tcpsock.go:222 +0x49
github.com/hyperledger/fabric/vendor/google.golang.org/grpc.(*Server).Serve(0xc420284780, 0x122d120, 0xc4201aa600, 0x0, 0x0)
/opt/gopath/src/github.com/hyperledger/fabric/vendor/google.golang.org/grpc/server.go:454 +0x196
github.com/hyperledger/fabric/core/comm.(*grpcServerImpl).Start(0xc4201ba2a0, 0xc4202dc490, 0x1)
/opt/gopath/src/github.com/hyperledger/fabric/core/comm/server.go:208 +0x41
main.main()
/opt/gopath/src/github.com/hyperledger/fabric/orderer/main.go:79 +0x4c0
goroutine 17 [syscall, locked to thread]:
runtime.goexit()
/opt/go/src/runtime/asm_amd64.s:2086 +0x1
goroutine 34 [select]:
github.com/hyperledger/fabric/vendor/github.com/syndtr/goleveldb/leveldb/util.(*BufferPool).drain(0xc4201bb260)
/opt/gopath/src/github.com/hyperledger/fabric/vendor/github.com/syndtr/goleveldb/leveldb/util/buffer_pool.go:206 +0x247
created by github.com/hyperledger/fabric/vendor/github.com/syndtr/goleveldb/leveldb/util.NewBufferPool
/opt/gopath/src/github.com/hyperledger/fabric/vendor/github.com/syndtr/goleveldb/leveldb/util/buffer_pool.go:237 +0x1bc
已解决https://yq.aliyun.com/articles/238940
我怎么没碰到这个问题
zuijin刚部署的
偶尔碰到，而且只在阿里云上出现了。
fabric-ca-client 向二级ca发起register申请的时候总是报错：`Failed to verify certificate: Failed to verify certificate: x509: certificate signed by unknown authority`
有人遇到过没有
Has joined the channel.
Has joined the channel.
分布式环境部署，peer端口总是无法访问
请问有人能帮忙回答一下吗？
通过/etc/hosts方式
peer额7051/7052/7053端口无法被别的服务器访问
对一个二级ca执行fabric-ca-client getcacert操作，没有发现有其他证书写入到msp/intermediatecerts路径下，二级ca没有配置parerent ca，但是配置了chainfile
这种情况下没法获取证书链？
Has joined the channel.
Has joined the channel.
@ylsGit 阿里云遇到同样的问题, 参考你的方案修改后OK, 谢谢提供解决方案!
Has joined the channel.
有人在研究更换组织机构的证书没？
突然发现组织机构的证书一更换，他的Admin证书和peer的同名证书都要更换
这样是不是要重启peer啊
chaincode使用xx,_:=GetStateByPartialCompositeKey()查询时，xx..Next()超时，这个超时时间在哪控制？
2017-11-28 08:32:49.700 UTC [shim] handleQueryStateNext -> ERRO 00a [2d83fb56]Received ERROR
2017-11-28 08:32:49.700 UTC [shim] nextResult -> ERRO 00b Failed to fetch next results [transaction context not found (timed out ?)]
2017-11-28 08:32:49.703 UTC [shim] handleQueryStateClose -> ERRO 00c [2d83fb56]Received ERROR
Has joined the channel.
Has joined the channel.
@baoyangc 你最开始用的是默认证书？
@here Dear all, we will have group meeting at 10AM this Wednesday morning, pls help update the agenda/attendee at https://wiki.hyperledger.org/groups/twgc/meeting/2017-12-06 (Notice we are using the new zoom system), thanks!
区块提交验证的时候，readset数据只验证version，没有验证value， 那么，如果我修改了背书节点的值（这样背书节点与其他节点值不一致了）， 那么做交易后，其他的节点会直接提交背书节点背书的数据。 意思是如果手动修改了背书节点的数据，做一次交易后，其他节点也跟着变了。
这是否合理？
not really, the commit node will accept the same write set, hence the result will be the same, as the endorsed one.
Has joined the channel.
sm2 support proposal is here, welcome everyone to help update and join to contribute: https://docs.google.com/document/d/1Qrt2PcHvkj9NHeQyY7HJ9pM1uHD00e3cxBMKb0z7bos/edit#heading=h.fxg3c3klpg71
@baohua missed yesterday's call. Is there anything new on Mongo support?
请教一下大家，我在试着跑fabric自己提供的chaincode/chaincode_example02/go里面的chaincode, peer chaincode instantiate的时候我输的参数是这么写的'{"Args":["a", "100", "b", "90"]}'，但是跑起来报错了，错误是Incorrect number of arguments. Expecting 4，不知道为啥，确实是4个参数啊
[ ](https://chat.hyperledger.org/channel/twg-china?msg=RTiQdFiQjWR5Pf4ec) @ZheliangLiu "invoke", "a", "b", "10“” 看一下
刚才看到弹消息@我了，但是我一打开这个那条消息又消失了，刚才那位朋友可以再发一次吗？麻烦了
[ ](https://chat.hyperledger.org/channel/twg-china?msg=9i5bCdvzS7kYGAjTH) @ZheliangLiu 你试一下"init","a","100","b","200"
哦哦，好的
可以了！谢谢啦！！
@liutc u dislike couchdb/leveldb, hmmm
@baohua it is somehow hard to find people who are very familiar with couchdb...
yeap, supporting more db backend is a good idea, there are some implementation work on-going
Has joined the channel.
找到组织啦
《区块链原理、设计与应用》估计下周一就能到手，准备细读。gitbook上粗览了一遍，@baohua 写的很棒。
@qurikuduo thanks, and welcome for advice
Clipboard - December 10, 2017 9:18 AM
@liutc u may have a look at FAB-3067. Base on some quick experiments, with large records, this new feature can improve the query performance nearly an order of magnitude.
@baohua got! I'd try to see if index can help to improve query performance -- now we have control over all couchdb so manually creating all indexes won't be an issue.
Has joined the channel.
Has joined the channel.
@baohua I meet an error in my project, the error log [premature execution -chaincode (%s) is being launched] from line 539 in fabric/core/chaincode/chaincode_support.go sometimes occurred when I restart the peer and then invoke the chaincode, we are testing the sence that peer node is crashed unexpectedly, any suggestions can help me?
@cs-wang Perhaps you could check if the chaincode proccess is still running while your peer is shutdown.
how to check chaincode process? does chaincode process mean the chaincode container?
Has joined the channel.
Yes, you can check if the container is still there.
OK,3Q
@cs-wang u may wait a while after the first invocation, as the chaincode container is stopped when peer stop
a invocation will wake them up, take a while, whatever
Has joined the channel.
大家好，请教个问题，tlsca这个东东应该如何理解好？
tlsca有私钥和证明书，这两个文件是从ca服务器生成的吗？还是通过openssl这样的工具生成的？弄不清他们的来源。
@baohua 杨老师，打扰了，关于tlsca，我在ca那边的聊天记录看到有下面这样的解释，这个解释正确吗？
The tls folder is used by the server-side of TLS and the tlsca folder is used by the client-side of TLS
It depends. Usually, the `tls` is the runner side's cert/key. While `tlsca` is for other purpose, it means the ca for signing new identity, which is used for tls.
@baohua 谢谢杨老师回答，是不是可以理解成，生成tls的时候用tlsca来签名?
tls 是server需要用的，tlsca可以用来验证这个节点的身份。用处不一样。
server的tls证书是对应的tlsca签的。tlsca的证书保存在tlsca文件夹下
@dijun 你要这么说我就明白了，和我理解一样，用openssl生成tls的时候需要签名，这个时候tlsca就用上了。
另外，cryptogen,openssl或者ca都可以产生，看你的具体应用场景
@dijun 那tlsca就是用openssl生成的自签名的证书和私钥
可以
@baohua @dijun 欧拉，谢谢大家！！！！:handshake:
* 'Organizations[0]' has invalid keys: BCCSP
执行 configtxgen -profile TwoOrgsOrdererGenesis 出现 * 'Organizations[0]' has invalid keys: BCCSP的 错误，是不是可能版本不同 导致的阿？ 书本 p148
新手想请教一下，用hyperledger composer 可以开发实际的完整的应用吗？网上看着是说可以加快开发，但之前听一个人说composer 只能用来模拟，不能用来实际开发，最近又觉得他说的不对:sweat:
p148, 当我运行 configtxgen 的时候 报 错误： 【 has invalid keys: BCCSP 】， 然后我看了源码 tag 1.0.0 和 master 源码：
type Organization struct {
Name string `yaml:"Name"`
ID string `yaml:"ID"`
MSPDir string `yaml:"MSPDir"`
AdminPrincipal string `yaml:"AdminPrincipal"`
// Note: Viper deserialization does not seem to care for
// embedding of types, so we use one organization struct
// for both orderers and applications.
AnchorPeers []*AnchorPeer `yaml:"AnchorPeers"`
}
都没有BCCSP的定义，是不是书本p147-148中的configtx.yaml中应该去掉 BCCSP内容？
去掉后 运行是没有报错的。
@ZheliangLiu https://github.com/hyperledger/composer-sample-applications 这有些应用的例子可以参考
好的，我去看看，谢谢
@here Dear all, we will have group meeting at 10AM this Wednesday morning, pls help update the agenda/attendee at https://wiki.hyperledger.org/groups/twgc/meeting/2017-12-20 (we will collect feedbacks to the work in past year, welcome to prepare and join), thanks!
Has joined the channel.
我遇到一个问题，registerChaincodeEvent
我遇到一个问题，registerChaincodeEvent之后 之前注册的txEvent就被阻塞了。
Has joined the channel.
这篇文章，我想翻译成中文。问一下，这个文章有中文版吗？ 这个：https://hyperledger.github.io/composer/unstable/tutorials/deploy-to-fabric-multi-org.html
@lcj 不小心看到你问CA的问题。我整理过一个很长的文章：https://github.com/wbwangk/wbwangk.github.io/wiki/SSL%E7%A0%94%E7%A9%B6
@wbwangk 那篇文章是sstone1写的，之前只能在他的github里看到，最近才合并到官网上
@labcoinpoc 谢谢。我是先学习的Fabric BYFN。Composer官网的其他文章无法将Fabirc BYFN与Composer集成起来，至少我没找到。我很喜欢这篇文章。按我的习惯，会把有好文章翻译成中文，以便整理和掌握。
chaincode里可以调用其他Services吗？比如在链码里调用获取天气API，根据传入的参数获取不同城市的天气信息？这样可行吗？
@zeroest certainly, just be aware that if u have multiple chaincode containers simultaneously, then the api will be called several times. Better make it idempotent.
Has joined the channel.
@baohua 谢谢。chaincode需要安装到所有节点吗？org1开发的chaincode, 必须安装到org2的节点上org2才可以调用吗？
those peer that supports chaincode, must have the chaincode installed firstly.
Has joined the channel.
@baohua ，杨老师，您对fabric访问链外数据源有什么解决方案吗？
是什么样的数据源 碰到啥具体问题？
Has joined the channel.
比如，在链上存储数据的指纹，但是数据在第三方的数据库中，这时候，怎么智能合约能够安全，正确的访问原文数据。
Has joined the channel.
听起来你担心的是安全问题。一方面是数据库那边要有acl，另外一方面信道要做加密处理。
Has joined the channel.
Has joined the channel.
@here
Dear all, we will have group meeting at 10AM this Wednesday morning, pls help update the agenda/attendee at https://wiki.hyperledger.org/groups/twgc/meeting/2018-01-03, welcome to join, thanks!
Has joined the channel.
does anyone know how to fix this : # github.com/miekg/pkcs11
..\..\miekg\pkcs11\pkcs11.go:26:18: fatal error: ltdl.h: No such file or directory? I tried `go build --tags nopkcs11` but it did not work , my platform is windows by the way
Has joined the channel.
@WalkerLiu would u like to try the linux or macOS platform?
[ ](https://chat.hyperledger.org/channel/twg-china?msg=RYtgxHZKaoCscGqoY) @baohua Thank you for your reply anyway ， I switch to java to code my ChannleCode
Has joined the channel.
Has joined the channel.
Hello, I'm Eleonora. I would like to know if there are tutorials or resources to understand how to instantiate an Hyperledger Fabric network over different physical nodes. Right now, we were able to instantiate only a debug network, using different docker containers in the same computer.
Has joined the channel.
Has joined the channel.
1.1版本在哪里下载
大家好，请教一个ca的问题。ca启动的时候设置了下面的参数，从设置上来看，ca的root证明书可以作为tls证明书来用，是这样理解吗？
- FABRIC_CA_SERVER_CA_CERTFILE=/etc/hyperledger/fabric-ca-server-config/ca.org1.example.com-cert.pem
- FABRIC_CA_SERVER_CA_KEYFILE=/etc/hyperledger/fabric-ca-server-config/0e729224e8b3f31784c8a93c5b8ef6f4c1c91d9e6e577c45c33163609fe40011_sk
- FABRIC_CA_SERVER_TLS_CERTFILE=/etc/hyperledger/fabric-ca-server-config/ca.org1.example.com-cert.pem
- FABRIC_CA_SERVER_TLS_KEYFILE=/etc/hyperledger/fabric-ca-server-config/0e729224e8b3f31784c8a93c5b8ef6f4c1c91d9e6e577c45c33163609fe40011_sk
原理上可以，不推荐。
好的，谢谢杨老师！！
java sdk 收集玩 背书 调用 _channel.sendTransaction(successful).get(testConfig.getTransactionWaitTime(), TimeUnit.SECONDS); 发给orderer的时候 超时无响应。 orderer 出现如下日志， 怀疑是 与Ignoring stale time-to-cut-message for block 。 版本为fabric 1.0.0，运行七个小时，后出现的这种情况，出错之前以前写入都正常，有知道这个问题的吗？
{"log":"\u001b[36m2018-01-11 03:45:42.526 UTC [fsblkstorage] indexBlock -\u003e DEBU ab9\u001b[0m Indexing block [blockNum=519924, blockHash=[]byte{0xc9, 0xa6, 0xea, 0x7e, 0x41, 0x9c, 0x24, 0x97, 0x6c, 0xa0, 0x8b, 0x79, 0x9f, 0x9, 0x31, 0xf6, 0xbe, 0x39, 0xf4, 0x5d, 0xc5, 0xc2, 0x3d, 0x71, 0xef, 0x6e, 0xe7, 0x6b, 0x41, 0x3d, 0xa6, 0x95} txOffsets=\n","stream":"stderr","time":"2018-01-11T03:45:42.527018114Z"}
{"log":"txId=f814688bc1ff46031cab9ee6de623bea50f7b67216544c446e343e1a213c36c7 locPointer=offset=72, bytesLength=5004\n","stream":"stderr","time":"2018-01-11T03:45:42.527097784Z"}
{"log":"]\n","stream":"stderr","time":"2018-01-11T03:45:42.527127607Z"}
{"log":"\u001b[36m2018-01-11 03:45:42.526 UTC [fsblkstorage] updateCheckpoint -\u003e DEBU aba\u001b[0m Broadcasting about update checkpointInfo: latestFileChunkSuffixNum=[66], latestFileChunksize=[30873016], isChainEmpty=[false], lastBlockNumber=[519924]\n","stream":"stderr","time":"2018-01-11T03:45:42.527133387Z"}
{"log":"\u001b[36m2018-01-11 03:45:42.526 UTC [orderer/multichain] WriteBlock -\u003e DEBU abb\u001b[0m [channel: cbca] Wrote block 519924\n","stream":"stderr","time":"2018-01-11T03:45:42.527137396Z"}
{"log":"\u001b[36m2018-01-11 03:45:42.526 UTC [orderer/kafka] processTimeToCut -\u003e DEBU abc\u001b[0m [channel: cbca] Proper time-to-cut received, just cut block 519924\n","stream":"stderr","time":"2018-01-11T03:45:42.527143398Z"}
{"log":"\u001b[36m2018-01-11 03:45:42.526 UTC [orderer/kafka] processMessagesToBlocks -\u003e DEBU abd\u001b[0m [channel: cbca] Successfully unmarshalled consumed message, offset is 1895887. Inspecting type...\n","stream":"stderr","time":"2018-01-11T03:45:42.527154602Z"}
{"log":"\u001b[36m2018-01-11 03:45:42.527 UTC [orderer/kafka] processTimeToCut -\u003e DEBU abe\u001b[0m [channel: cbca] It's a time-to-cut message for block 519924\n","stream":"stderr","time":"2018-01-11T03:45:42.527158414Z"}
{"log":"\u001b[36m2018-01-11 03:45:42.527 UTC [orderer/kafka] processTimeToCut -\u003e DEBU abf\u001b[0m [channel: cbca] Ignoring stale time-to-cut-message for block 519924\n","stream":"stderr","time":"2018-01-11T03:45:42.527162223Z"}
{"log":"\u001b[36m2018-01-11 03:45:42.527 UTC [orderer/kafka] processMessagesToBlocks -\u003e DEBU ac0\u001b[0m [channel: cbca] Successfully unmarshalled consumed message, offset is 1895888. Inspecting type...\n","stream":"stderr","time":"2018-01-11T03:45:42.527165907Z"}
{"log":"\u001b[36m2018-01-11 03:45:42.527 UTC [orderer/kafka] processTimeToCut -\u003e DEBU ac1\u001b[0m [channel: cbca] It's a time-to-cut message for block 519924\n","stream":"stderr","time":"2018-01-11T03:45:42.527169167Z"}
{"log":"\u001b[36m2018-01-11 03:45:42.527 UTC [orderer/kafka] processTimeToCut -\u003e DEBU ac2\u001b[0m [channel: cbca] Ignoring stale time-to-cut-message for block 519924\n","stream":"stderr","time":"2018-01-11T03:45:42.527172301Z"}
{"log":"\u001b[36m2018-01-11 03:46:01.122 UTC [grpc] Printf -\u003e DEBU ac3\u001b[0m grpc: Server.Serve failed to complete security handshake from \"127.0.0.1:41212\": EOF\n","stream":"stderr","time":"2018-01-11T03:46:01.12252874Z"}
{"log":"\u001b[36m2018-01-11 03:46:14.214 UTC [grpc] Printf -\u003e DEBU ac4\u001b[0m grpc: Server.Serve failed to complete security handshake from \"47.95.252.108:37790\": EOF\n","stream":"stderr","time":"2018-01-11T03:46:14.214805542Z"}
@baohua 现在能确定 1.0.2版本数据格式上完全兼容1.0.0的版本吗？ 我们想升级下下版本.
Has joined the channel.
请教一个问题：如果一个私有\需要授权的区块链应用系统的其他参与方都是以client的身份进行集成或者manual操作，所有节点（peer）都是由系统的搭建方进行控制和维护，那么这样的企业应用系统除了应用了区块链技术本身外，还有什么吸引人的亮点呢？
Has joined the channel.
Has joined the channel.
hyperledger fabric 用-P "AND ('Org1MSP.member','Org2MSP.member') AND这种背书策略，在org1的一个节点做了交易以后，这个记录不会被记到账本里边，query出来的还是做交易前的数据，我要怎么样才能让这个交易成功的写到账本里呢
Has joined the channel.
Has joined the channel.
@emmansun 两个互不信任的企业要把两个信息系统连接起来做“交易”或其他工作，可以用区块链技术建立互信。如果是一个企业内，那么这个企业必须足够大，部门众多，存在大量部门级应用，则跨部门应用之间通过区块链建立互信
@wbwangk ,那是不是每个企业(部门)必须有自己的"节点"呢？但是这样的话，运行维护就麻烦了
@emmansun 区块链是个“民主”的系统，两个部门要互信，当然都得部署peer，不信任别人部署的peer。
这是个理想的样子，真这么做的不多。。。
@crj Fabric很麻烦，不如直接引入Composer，背书啥的被Composer干了，更简单了
@wbwangk，对啊，一般都是一个第三方平台，号称用了区块链，譬如超级账本，部署在云上，然后让别人接入，而且那些“接入客户”的IT能力都很弱，或者不想投入那么多开发维护成本。
Composer在Fabric外面包裹了一层，让区块链开发者的入门门槛大大降低了
现在我在做一个公司内的决算系统，确实感觉就是为了区块链而区块链
@emmansun 部署在云端的区块链也有用，必须保留了不可篡改性。现在数字资源的产权保护是个很火的区块链应用场景。
应用场景这方面很不好定位感觉
现在好多时候区块链是个噱头，还处于探索阶段，用错场景是难免的
@wbwangk 写入链的数据是不可篡改，但是如何保证写入前就一定是真实的呢，比如在企业中多个部门间部署，区块链本身倒是可以保证提交的数据不可更改，而且可以保证数据处理的逻辑不可更改，但提交之前没办法确保啊，感觉还是不能解决全部问题
“不可篡改性”或许是一个点，但是需要客户真的理解和认识其价值并且买账，要不然的话，在一个传统的“集中式”应用系统，人家也可以通过一些第三方托管隔离、安全认证等方式取得信任。
@labcoinpoc 这就像是你花钱在银行租了一个保险箱，然后在里面放了一些垃圾，银行是不管的，愿意放就放
我们公司也在尝试区块链技术，想找一个应用场景，感觉不好找
hyperledger相对于bitcoin和以太坊来说倾向于集团链，但是集团链随着集中度提高又跟去中心化越来越冲突。
@labcoinpoc ，这就是公共链和私有链的最大区别
@wbwangk 没错，现在的疑惑就是想要使用区块链来实现可信，但是除了牺牲了性能以外，没有实现相比传统系统更好的效果
个人认为"民主"是区块链的核心思想，考虑它的使用场景的时候多多从这个角度考虑问题
公共链充分使用和体现了区块链的优势，私有链的应用有点尴尬。“民主”、“对等”、“共识”、“自治”这些都是区块炼的应有之义，但是在私有链中这个就需要参与方的对等参与了。
Dear all, we will have group meeting at 10AM this Wednesday morning, pls help update the agenda/attendees at https://wiki.hyperledger.org/groups/twgc/meeting/2018-01-17, welcome to join, thanks!
@here
Clipboard - 2018年1月16日下午4点41分
我都是按步骤一步步来的，都没有错，但是 register的时候错了[ERROR] No certificates found for provided serial and aki
Has joined the channel.
@duwenhui 一般情况下，生产环境下，大家都在用node sdk，使用java sdk很少，看你的错误，是TLS握手错误。
请教一下大家，有直接使用fabric-ca替代crypto-config生成身份证书，用于多机部署fabric网络的朋友吗？ fabric-ca服务可以用于生成TLS的证书吗？
Has joined the channel.
@liurf 谢谢你的回复， 我在fabric群里问题，这个问题是1.0.0的一个bug，已经在1.0.2以后的版本解决了。
https://jira.hyperledger.org/browse/FAB-5709
Orderer of v1.0.0 has a bug in cutting a block caused by the number of transactions or by the size of transactions in a block exceeding a threshold (i.e., not the case of Time-To-Cut). According to the JIRA item, this issue is fixed in v1.0.2. I am not sure this is related to the time out you observed.
Clipboard - 2018年1月19日下午5点25分
Has joined the channel.
twg china 之前组织过很多events，meetingup，最近才开始关注fabric错过了，请问大家谁有 events 上面提到的一些案例（场景）的资料？
大牛们， 目前fabric 1.0.5 事件只支持blockevent吗？ client app如何有效地（e.g.性能因素）确认一个transaction 写入成功？然后再执行下一步去调用另外一个系统
Has joined the channel.
Clipboard - 2018年1月22日上午10点48分
Clipboard - 2018年1月22日上午10点49分
composer network start 失败后我就去docker ps ,像上面这样，有人遇到这样的问题吗
Clipboard - 2018年1月22日中午11点35分
Has joined the channel.
问题解决，似乎是.bna文件是旧的造成，我换了个新的.bna文件就可以了
大家好， 最近在测试Read-Write sets排序这块， 有以下场景：
在一个block中只有一个交易，交易涉及world state中三个key-value，分别为A，B，C
chaincode的操作顺序为 Read A-->Read B-->Read C-->Write A-->Write B
执行结果Transaction的ValidationCode为11（MVCC_READ_CONFLICT）
请帮忙解释下， 这种结果的原因是什么？个人理解操作顺序是不冲突的。
Has joined the channel.
Has joined the channel.
Has joined the channel.
Has joined the channel.
有没有人研究fabric go sdk
Has joined the channel.
各位朋友，这chat有没有客户端工具？使用起来会方便点？
pc端和手机端都有，可以搜索 rocketchat
Has joined the channel.
Has joined the channel.
Has joined the channel.
Has joined the channel.
Has joined the channel.
大家好
@here
Dear all, we will have group meeting at 10AM this Wednesday morning, pls help update the agenda and attendees at https://wiki.hyperledger.org/groups/twgc/meeting/2018-01-31, welcome to join, thanks!
@baohua 所有人都可以参加吗？
所有人都能参与的
Has joined the channel.
@here 请问一下谁比较了解用Fabric如何创建积分系统？ 我了解到Fabric没有nativ
e的currency，需要用MSP来自行设计currency类的asset，可以使用UTXO或者account model,但是我不确定如何开始呢？ 有没有类似的sample network可以参考，谢谢 :)
@here 请问一下谁比较了解用Fabric如何创建积分系统？ 我了解到Fabric没有native的currency，需要用MSP来自行设计currency类的asset，可以使用UTXO或者account model,但是我不确定如何开始呢？ 有没有类似的sample network可以参考，谢谢 :)
大家好，请问下各位有使用过hyperledeger composer playground的朋友吗？ 我使用palyground链接自己多机部署的fabric区块链服务(非docker脚本安装)。
大家好，请问下各位有使用过hyperledeger composer playground的朋友吗？ 我使用palyground链接自己多机部署的fabric区块链服务(非docker脚本安装)。
然后Create A Business Network Card 选择Hyperledger Fabric v1.0 并填写相应的ca 、orderer 、peer节点的地址，以及msp用户证书和私钥
接着选择 Deploy New Business Network 创建一个empty-business-network ，并且输入相应的msp用户证书以及私钥。接着点击 Deploy 按钮。
但是节点日志提示：
·
大家好，请问下各位有使用过hyperledeger composer playground的朋友吗？ 我使用palyground链接自己多机部署的fabric区块链服务(非docker脚本安装)。
然后Create A Business Network Card 选择Hyperledger Fabric v1.0 并填写相应的ca 、orderer 、peer节点的地址，以及msp用户证书和私钥
接着选择 Deploy New Business Network 创建一个empty-business-network ，并且输入相应的msp用户证书以及私钥。接着点击 Deploy 按钮。
但是节点日志提示：
`
2018-01-30 13:37:37.408 CST [chaincode] Launch -> ERRO 056 launchAndWaitForRegister failed: Failed to generate platform-specific docker build: Error returned from build: 2 "# composer/vendor/gopkg.in/olebedev/go-duktape.v3
In file included from chaincode/input/src/composer/vendor/gopkg.in/olebedev/go-duktape.v3/api.go:7:0:
chaincode/input/src/composer/vendor/gopkg.in/olebedev/go-duktape.v3/api.go: In function '_duk_error':
chaincode/input/src/composer/vendor/gopkg.in/olebedev/go-duktape.v3/duktape.h:510:127: warning: right-hand operand of comma expression has no effect [-Wunused-value]
(duk_error_raw((ctx), (duk_errcode_t) (err_code), (const char *) (DUK_FILE_MACRO), (duk_int_t) (DUK_LINE_MACRO), __VA_ARGS__), (duk_ret_t) 0)
^
chaincode/input/src/composer/vendor/gopkg.in/olebedev/go-duktape.v3/api.go:153:2: note: in expansion of macro 'duk_error'
duk_error(ctx, err_code, "%s", str);
^
# composer/vendor/gopkg.in/olebedev/go-duktape.v3
chaincode/input/src/composer/vendor/gopkg.in/olebedev/go-duktape.v3/duktape.go:134: constant 18446744073709551615 overflows int
"
error starting container
2018-01-30 13:37:37.409 CST [endorser] simulateProposal -> ERRO 057 failed to invoke chaincode name:"lscc" on transaction aa31cf05ba9e455b19d0d2455d32ef5da5432a27d523c9d7398f5a15b182c2f6, error: Failed to generate platform-specific docker build: Error returned from build: 2 "# composer/vendor/gopkg.in/olebedev/go-duktape.v3
In file included from chaincode/input/src/composer/vendor/gopkg.in/olebedev/go-duktape.v3/api.go:7:0:
chaincode/input/src/composer/vendor/gopkg.in/olebedev/go-duktape.v3/api.go: In function '_duk_error':
chaincode/input/src/composer/vendor/gopkg.in/olebedev/go-duktape.v3/duktape.h:510:127: warning: right-hand operand of comma expression has no effect [-Wunused-value]
(duk_error_raw((ctx), (duk_errcode_t) (err_code), (const char *) (DUK_FILE_MACRO), (duk_int_t) (DUK_LINE_MACRO), __VA_ARGS__), (duk_ret_t) 0)
^
chaincode/input/src/composer/vendor/gopkg.in/olebedev/go-duktape.v3/api.go:153:2: note: in expansion of macro 'duk_error'
duk_error(ctx, err_code, "%s", str);
^
# composer/vendor/gopkg.in/olebedev/go-duktape.v3
chaincode/input/src/composer/vendor/gopkg.in/olebedev/go-duktape.v3/duktape.go:134: constant 18446744073709551615 overflows int
"
error starting container
`
等错误信息。
通过控制台 peer chaincode list --installed 可以查看到链码已经安装成功，但是初始化的时候失败，导致创建链码容器错误。
error.bmp
@james3443112 最后一行说整数越界了，估计需要检查一下链码
感谢，不过我直接运行的playground里面的模板样例
Clipboard - 2018年1月31日上午9点55分
杀container。。。
杀掉，一会儿又高了.
@baohua zoom 上啥都木有啊
Done, the meeting is from 10am to 11am, as in agenda. should be on time for next one :)
请问下， 1月25，上海的活动， 1月27日，北京的活动 ， 有 ppt 等类似资料下载吗 ？
slides link 会放到https://wiki.hyperledger.org/groups/twgc/team_eo
谢谢
群组里面有研究过composer-playground的朋友吗？
大家好，我在macos下按照官方文档一步步做下来，想build my first network, 但是在最后一步执行 ./byfn.sh -m up命令时出现错误：
Shimingbookmini:first-network Shiming$ ./byfn.sh -m up
Starting with channel 'mychannel' and CLI timeout of '10' seconds and CLI delay of '3' seconds
Continue (y/n)? y
proceeding ...
Pulling orderer.example.com (hyperledger/fabric-orderer:latest)...
ERROR: manifest for hyperledger/fabric-orderer:latest not found
ERROR !!!! Unable to start network
Error response from daemon: No such container: cli
Shimingbookmini:first-network Shiming$
在网上查了很久，没有解决。我参照的是这份文档 https://hyperledger-fabric.readthedocs.io/en/release/build_network.html
我发现jira上有个issue提到同样的问题，不过是几个月前了，issue也关闭了，为什么我又会碰到呢。群组里有同学知道怎么回事吗？
issue url： https://jira.hyperledger.org/browse/FAB-5412
@baohua 能指点一下吗？
我在博客中记录下了详细过程，https://www.cnblogs.com/huahuayu/p/8394653.html
@ShimingLiu i guess u do not have correct images at local, may check with `docker images`. Besides, can look at https://github.com/yeasy/docker-compose-files/tree/master/hyperledger_fabric/ for a reference.
Has joined the channel.
CLI报错
@baohua 老师，谢谢回复，我根据Jira这个issue中的评论 https://jira.hyperledger.org/browse/FAB-5412 重新执行了一下 curl -sSL https://raw.githubusercontent.com/hyperledger/fabric/master/scripts/bootstrap.sh | bash -s 1.1.0-alpha， （上次是用的1.0.5版本）其他步骤仍按官方文档操作。这次执行后看到这个画面了
Shimingbookmini:first-network Shiming$ ./byfn.sh -m up
Starting with channel 'mychannel' and CLI timeout of '10'
Continue (y/n)? y
Creating orderer.example.com ... done
Creating cli ... done
Creating orderer.example.com ...
Creating peer0.org2.example.com ...
Creating peer1.org1.example.com ...
Creating peer1.org2.example.com ...
Creating cli ...
____ _____ _ ____ _____
/ ___| |_ _| / \ | _ \ |_ _|
\___ \ | | / _ \ | |_) | | |
___) | | | / ___ \ | _ < | |
|____/ |_| /_/ \_\ |_| \_\ |_|
但是最后CLI报错
!!!!!!!!!!!!!!! Channel creation failed !!!!!!!!!!!!!!!!
========= ERROR !!! FAILED to execute End-2-End Scenario ===========
cli error.log
请问 fabri v1.0.5 运行链码例子02 ， 查询交易金额的时候会报错：{"Error":"Nil amount for a"} 这个错误要怎么修复？
1.0.0版本好像没这个问题呢
fabric和composer我都部署过，也碰到过和解决了很多问题。可以到我的wiki下去找，有很多笔记。地址是：https://github.com/wbwangk/wbwangk.github.io/wiki
Has joined the channel.
@wbwangk 不错
Has joined the channel.
Clipboard - 2018年2月5日上午10点57分
@Randyshu2018 -->相当于引用，o是定义。org.example.OrderItem#orderItem1这种是relationship，可以resolve为对象，一般来说composer里的引用是会自动resolve，但可能像图里这种两层引用只能取到relationship，resolve的方法是按照#前面的类型获取registry，然后用#后面的id获取到对象 参考这里https://stackoverflow.com/questions/43639867/how-to-resolve-a-relationship-to-get-a-hold-of-the-reference-being-pointed-to
@labcoinpoc 谢谢
请问一下 fabric 1.10 alpha 版本 peer 节点 peer channel create 创建通道的时候orderer节点提示错误：
2018-02-05 14:12:49.829 CST [common/deliver] deliverBlocks -> WARN 2d8 Rejecting deliver for 10.121.60.4:43596 due to envelope validation error: timestamp 2018-02-05 06:12:49 +0000 UTC is more than the 0s time window difference above/below server time 2018-02-05 14:12:49.829137972 +0800 CST m=+116.727101276. either the server and client clocks are out of sync or a relay attack has been attempted
但是我peer节点的主机还有orderer节点的主机都是同步了系统时间，时间是一致的。并且不论什么时候创建通道“due to envelope validation error: timestamp 2018-02-05 06:12:49 +0000 UTC is more than ”这个时间永远是不变的
有朋友遇到过这样的情况吗？
@james3443112 会不会是你的genesis块里写的时间戳有问题？生成genesis块的机器的时间不对？
不会 时间是一样的
我同步时间了
确定两台机器的时间是一致的
如果多次跑命令时间不变说明是写死在某个地方了，我想只可能是在genesis块里。你可以试试用configtxgen -inspectBlock genesis.block 解开看看，搜搜那个不变的时间在不在其中
确实在
在channel_head里面
哦，明白了，你生成初始块的机器的时区不对
我修改时区了
难道不能用中国的时区？
你看初始块的时区是UTC0，中国是＋8
看不出来 但是感觉像是 差了8个时区
原来的版本没有这个问题呢
我需要把时区改成UTC-0的？
估计是生成块的机器因为时区的原因比现在时间晚吧，所以区块链不接受
应该都一致就行吧，或者估计放置8小时后问题就解决了:sweat_smile:
我在创建以前同步时间了。。。
Clipboard - 2018年2月5日下午2点39分
Clipboard - 2018年2月5日下午2点39分
我也是醉了 难道不是取的系统时间吗？
如果orderer的时间是当前时间的话没理由比这个时间早啊。。。现在都6：５１utc0了
我系统时间14.38的时候创建的genesis.block，查看genesis.block文件， timestamp: 06.37 晚了8个时区
1.10-alpha版本的创建创世区块获取时间的方式跟原来的不一样了？
大家有过跟银行或者券商这种机构共同部署联盟链的经验吗？假如银行想部一个orderer，一个endorser，并且*不想开放公网IP加端口*的访问方式，而是通过VPN，这个可以实现吗？
我使用别的版本的configtxgen 创建genesis.block也是utc0时区的
我发现1.1.0-alpha版本有个问题，fabirc/common/deliver/deliver.go line 289 行 判断系统时间与环境时间（区块头的时间戳） 是不是这个判断有问题？
1.1.0-alpha 需要设置环境变量 CORE_AUTHENTICATION_TIMEWINDOW=15m
Has joined the channel.
@baohua 你好， Feb 04, Sunday, 2018 上海活动的资料可以放到wiki里面分享出来么，想了解一下，谢谢
Has joined the channel.
@henryhs, would u like to help collect the slides and put on wiki for Feb 4 meetup? Thanks!
Has joined the channel.
@henryhs many thanks
henry is doing that, as long as the speakers are fine with the sharing. keep watch the page and feel free to ping us if have any further questions!
Has joined the channel.
Has joined the channel.
这些图出自什么地方，谁能给个链接
Clipboard - 2018年2月7日下午2点41分
Has joined the channel.
Has joined the channel.
Has joined the channel.
Has joined the channel.
Hyperledger Fabric 代码解析。
@Hengming thanks
Has joined the channel.
Has joined the channel.
Has joined the channel.
Has joined the channel.
Has joined the channel.
Happy Spring Festival to everyone!
:stuck_out_tongue_winking_eye:
Has joined the channel.
Has joined the channel.
:stuck_out_tongue:
Looking for a new Hyperledger internship program chance.
want to launch or participate.
Has joined the channel.
仔细研究了这个项目，真是博大精深啊！
请教大家一个问题：fabric composer做好的商业网络包部署在fabric后，与账本的交互是直接通过sdk，不用调用链码了么。如果是这样，对交易的背书模拟执行链码这些操作是怎么执行的？ 如果还是通过composer部署了链码，那么与文档里说的链码只目前支持golang语言的说法不是有冲突了。
原生的链码现在支持go、java和nodejs了。composer对一些特定场景的链码支持了一些高级API，如果想偷懒不写太多代码可以用用。不过很多人还是直接开发链码，也不难学。
@lingtony fabric1.0版本以下不支持nodejs链码，当时Composer采用了一个go编写的js运行环境来支持nodejs链码，如杨老师所说，现在Fabric已经原生支持Nodejs链码，Composer17.x版本是基于Fabric1.1.0alpha的，已经改为直接部署nodejs
@lingtony fabric1.0版本以下不支持nodejs链码，当时Composer采用了一个go编写的js运行环境来支持nodejs商业逻辑，如杨老师所说，现在Fabric已经原生支持Nodejs链码，Composer17.x版本是基于Fabric1.1.0alpha的，已经改为直接部署nodejs
@lingtony fabric1.0版本以下不支持nodejs链码，当时Composer采用了一个go编写的js运行环境来支持nodejs商业逻辑，如杨老师所说，现在Fabric已经原生支持Nodejs链码，Composer0.17.x版本是基于Fabric1.1.0alpha的，已经改为直接部署nodejs
Has joined the channel.
请问一下大家，我现在在instantiate chaincode的时候总报这个错误是什么原因啊？我在网上也没找到答案 Error: Error endorsing chaincode: rpc error: code = Unknown desc = Failed to deserialize creator identity, err MSP Org1MSP is unknown,我docker 版本是17.12.0-ce ，install chaincode 的时候显示成功了的
@here Dear all, we will have the group meeting at 10AM this Wednesday morning, pls help update the agenda and attendees at https://wiki.hyperledger.org/groups/twgc/meeting/2018-02-28, welcome to join, thanks!
我知道哪里的问题了，打扰大家了
WechatIMG182.jpeg
Screen Shot 2018-02-14 at 19.34.43.png
@baohua 杨老师您好。我拜读了您的《区块链原理、设计与应用》这本书。自己也跑起来了cello，有几个问题想咨询您。
@baohua 首先，cello里的chain对应fabric的哪个组件？应该是区块链网络还是channel？，其次，是不是意味着一个host只能运行一个chanin？，但是如果一个第三方的节点在chain运行之后才申请加入这个chain可行吗？
大家好，执行v1.0.6/ network_setup.sh 有遇到mod_policy not set这个错误的吗
Clipboard - February 26, 2018 5:12 PM
Has joined the channel.
@jack21 可以到 #cello channel 里讨论 cello 相关问题
明天例会上讨论的 活动组织指南，欢迎大家提前准备 review：https://wiki.hyperledger.org/groups/twgc/events/guideline
Has joined the channel.
大家好，请教一个问题，请问是否有在一个已经运行的channel中添加注册一个新org和新peer的例子？谢谢
@Foen1x https://www.ibm.com/developerworks/cloud/library/cl-add-an-organization-to-your-hyperledger-fabric-blockchain/index.html
请问把orderer节点分别分配到不同的组织（例如orgOrderer0，orgOrderer1， orgOrderer2），而不是一个orgOrderer，是否可行？我考虑的是后续假如orderer的配置更新，就不能只用orgOrderer的Admin权限了，而需要多个org的Admin权限去做peer channel update，这个有什么办法实现吗？
@nauqnew 谢谢
Has joined the channel.
https://wiki.hyperledger.org/groups/twgc/meeting/2018-02-28
Has joined the channel.
Has joined the channel.
Has joined the channel.
大家好，请问有Indy讨论channel 吗？
Has joined the channel.
[ ](https://chat.hyperledger.org/channel/twg-china?msg=QK9jn4Wk4iSMsfbYh) @baohua 明白了，谢谢杨老师
Has joined the channel.
Has joined the channel.
Has joined the channel.
有没有人用这个 开发虚拟货币的
[ ](https://chat.hyperledger.org/channel/twg-china?msg=XGoPoD64v3BE7wNdb) @vnobo 这个不是面向虚拟货币的，个人觉得：节点有限，如果做虚拟货币应用，要控制这个货币很容易
[ ](https://chat.hyperledger.org/channel/twg-china?msg=9RiidvYApf5DrhB5X) @nauqnew 我想 等 sbft 实现后的事情。
今天的weekly meeting取消了？
Has joined the channel.
Has joined the channel.
Has left the channel.
it's bi-weekly: https://wiki.hyperledger.org/groups/tsc/technical-working-group-china
Has joined the channel.
大家好:grinning:
Has joined the channel.
welcome~ @no02
Has joined the channel.
有人在吗
hello, 根据《hyperledger-fabric-document.pdf》完成环境安装和相关工具下载，运行byfn.sh 时，在“ Genesis block”时出错，原因如下
root@george-VirtualBox:/project/hyperledger/fabric-samples/first-network# ./byfn.sh -m generate -c mychannel
Generating certs and genesis block for with channel 'mychannel' and CLI timeout of '10' seconds and CLI delay of '3' seconds
Continue? [Y/n] y
proceeding ...
/project/hyperledger/platform/bin/cryptogen
##########################################################
##### Generate certificates using cryptogen tool #########
##########################################################
+ cryptogen generate --config=./crypto-config.yaml
org1.example.com
org2.example.com
+ res=0
+ set +x
/project/hyperledger/platform/bin/configtxgen
##########################################################
######### Generating Orderer Genesis block ##############
##########################################################
+ configtxgen -profile TwoOrgsOrdererGenesis -outputBlock ./channel-artifacts/genesis.block
2018-03-11 12:19:26.987 CST [common/configtx/tool] main -> INFO 001 Loading configuration
2018-03-11 12:19:27.003 CST [common/configtx/tool/localconfig] Load -> CRIT 002 Error unmarshaling config into struct: 4 error(s) decoding:
* '' has invalid keys: capabilities
* 'Profiles[TwoOrgsChannel].Application' has invalid keys: Capabilities
* 'Profiles[TwoOrgsOrdererGenesis]' has invalid keys: Capabilities
* 'Profiles[TwoOrgsOrdererGenesis].Orderer' has invalid keys: Capabilities
+ res=1
+ set +x
Failed to generate orderer genesis block...
root@george-VirtualBox:/project/hyperledger/fabric-samples/first-network#
已经检测过cryptogen 和第二步中的相关路径，没有发现问题，谁能帮解释下，为什么第二步出现invalid key错误，我没有修改过key信息。谢谢了
@george19120 是不是检查一下crypto-config.yaml
每一次chaincode执行的Read write Sets都会上链，如果一次执行chaincode需要修改大量的Key-value有什么好办法吗？
Has joined the channel.
Installing chaincode on org1/peer0...
CORE_PEER_TLS_ROOTCERT_FILE=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org1.example.com/peers
CORE_PEER_TLS_KEY_FILE=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org1.example.com/peers/peer
CORE_PEER_LOCALMSPID=Org1MSP
CORE_VM_ENDPOINT=unix:///host/var/run/docker.sock
CORE_PEER_TLS_CERT_FILE=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org1.example.com/peers/pee
CORE_PEER_TLS_ENABLED=true
CORE_PEER_MSPCONFIGPATH=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org1.example.com/users/Adm
CORE_PEER_ID=cli
CORE_LOGGING_LEVEL=DEBUG
CORE_PEER_ADDRESS=peer0.org1.example.com:7051
2018-03-12 07:24:02.850 UTC [grpc] Printf -> DEBU 001 grpc: addrConn.resetTransport failed to create client transport: connectial tcp: lookup peer0.org1.example.com on 127.0.0.11:53: no such host"; Reconnecting to {peer0.org1.example.com:7051
root@blockchain:~/go/src/v1.0.6# make setup
bash scripts/env_setup.sh # Installing Docker and Docker-Compose
Docker already installed
Docker-Compose already installed
bash scripts/download_images.sh # Pull required Docker images
Downloading images from DockerHub... need a while
=== Pulling fabric images 1.0.6 from yeasy repo... ===
1.0.6: Pulling from yeasy/hyperledger-fabric-base
Digest: sha256:6a3c512635ac57ea2ee6f0cd9dd7ae01fc83dc76ebb8947ff9ee05b571d84f25
Status: Image is up to date for yeasy/hyperledger-fabric-base:1.0.6
1.0.6: Pulling from yeasy/hyperledger-fabric-peer
Digest: sha256:679d95562233404629f8b67c13a838d3b2ac3338f6595bc5d4b1cadb908a10b7
Status: Image is up to date for yeasy/hyperledger-fabric-peer:1.0.6
1.0.6: Pulling from yeasy/hyperledger-fabric-orderer
Digest: sha256:069b09ef78913a28beec3d2b68ad574cb0d0aa40cdd8190fc3117963649fc965
Status: Image is up to date for yeasy/hyperledger-fabric-orderer:1.0.6
1.0.6: Pulling from yeasy/hyperledger-fabric-ca
Digest: sha256:892a408d2c5dad80b4707ce565af98281db68c5b445bc8ddc9ece42317fc02f5
Status: Image is up to date for yeasy/hyperledger-fabric-ca:1.0.6
1.0.6: Pulling from yeasy/hyperledger-fabric
Digest: sha256:0d975977d02132f030fd2dc8858efaed0e7c5c1b365808b5193ff33c18774ba4
Status: Image is up to date for yeasy/hyperledger-fabric:1.0.6
0.1.0-preview: Pulling from yeasy/blockchain-explorer
Digest: sha256:afaabf01f15ef0be3922ac501365db78f35cc52f0856907899daeb2839dc574e
Status: Image is up to date for yeasy/blockchain-explorer:0.1.0-preview
=== Pulling base images 0.3.2 from fabric repo... ===
x86_64-0.3.2: Pulling from hyperledger/fabric-baseimage
Digest: sha256:22bf2179146117c3a9e9a890bdd22f977d3b9d96d1c4a150e82bdff6d6e93017
Status: Image is up to date for hyperledger/fabric-baseimage:x86_64-0.3.2
x86_64-0.3.2: Pulling from hyperledger/fabric-baseos
Digest: sha256:df3d05e438bcdc3454469877bb5dc99b77dd37a78b9343848aacfdb918b34ca4
Status: Image is up to date for hyperledger/fabric-baseos:x86_64-0.3.2
=== Pulling fabric images 1.0.6 from fabric repo... ===
x86_64-1.0.6: Pulling from hyperledger/fabric-peer
Digest: sha256:0644a13f2d663364df4f413ae18d3b03647a70f9b08cde0c9b235006488e6001
Status: Image is up to date for hyperledger/fabric-peer:x86_64-1.0.6
x86_64-1.0.6: Pulling from hyperledger/fabric-tools
Digest: sha256:f755c8eb5d38de3c5a5c933eb2a73984fd1c03af85d4a6b07c9dc13781a1c30b
Status: Image is up to date for hyperledger/fabric-tools:x86_64-1.0.6
x86_64-1.0.6: Pulling from hyperledger/fabric-orderer
Digest: sha256:c74234ffdc4ea6bb2fb97767786bc4800c851f740ef14180115926432ed0aeea
Status: Image is up to date for hyperledger/fabric-orderer:x86_64-1.0.6
x86_64-1.0.6: Pulling from hyperledger/fabric-ca
Digest: sha256:4e36ca05f3bfe17b2efcbf231d3489f3ce9128a7bf2b2272919ec66a6b0436ee
Status: Image is up to date for hyperledger/fabric-ca:x86_64-1.0.6
x86_64-1.0.6: Pulling from hyperledger/fabric-ccenv
Digest: sha256:1df4ca28b14d395761b7c0df8f71ae2672175d93d27fbf9d608325ce59a29f71
Status: Image is up to date for hyperledger/fabric-ccenv:x86_64-1.0.6
x86_64-1.0.6: Pulling from hyperledger/fabric-couchdb
Digest: sha256:0908777cf9d3617060b8f1d7107ea518632b713e3cb429426b9dbbe66a3235ad
Status: Image is up to date for hyperledger/fabric-couchdb:x86_64-1.0.6
x86_64-1.0.6: Pulling from hyperledger/fabric-kafka
Digest: sha256:f9780a41129fe7872b1522b5c7f06f95d7961899125c64fe5ebbc30b0342b9bf
Status: Image is up to date for hyperledger/fabric-kafka:x86_64-1.0.6
x86_64-1.0.6: Pulling from hyperledger/fabric-zookeeper
Digest: sha256:b50e27e5b476ccd9443b882324877adf7bdf55a903f14924c6d1a8935ac860f9
Status: Image is up to date for hyperledger/fabric-zookeeper:x86_64-1.0.6
8.0: Pulling from library/mysql
Digest: sha256:a01485bf022e22af276164c595ae14eaf34d84fb326eea062c1b0d55635b6754
Status: Image is up to date for mysql:8.0
Image pulling done, now can startup the network using docker-compose...
fabric 1.0.6 这步报错，请问怎么解决
Has joined the channel.
@yinzhiwu you can have a look at https://github.com/yeasy/docker-compose-files/blob/master/hyperledger_fabric/ for reference.
Dear all, we will have the group meeting at 10AM this Wednesday morning, pls help update the agenda at https://wiki.hyperledger.org/groups/twgc/meeting/2018-03-14 before the meeting, welcome to join, thanks!
@baohua Thanks for your precious guide. I have started to run,later see the results.:smile:
Has joined the channel.
@nolimitkun 谢谢答复，已经确认过这个文件了，没看出什么异常。
root@blockchain:~/go/src/v1.0.6# make test
Run test with docker-compose-2orgs-4peers-solo.yaml
Please make sure u have setup Docker and pulled images by 'make setup'.
make ready # Finish all testing
make[1]: Entering directory '/root/go/src/v1.0.6'
make stop
make[2]: Entering directory '/root/go/src/v1.0.6'
Stop the fabric network with docker-compose-2orgs-4peers-solo.yaml...
/bin/sh: 1: Syntax error: Bad fd number
Makefile:81: recipe for target 'stop' failed
make[2]: *** [stop] Error 2
make[2]: Leaving directory '/root/go/src/v1.0.6'
Makefile:38: recipe for target 'ready' failed
make[1]: *** [ready] Error 2
make[1]: Leaving directory '/root/go/src/v1.0.6'
Makefile:30: recipe for target 'test' failed
make: *** [test] Error 2
make test后报错，how to deal with
@baohua
i'm sorry, cannot understand how to repeat to create the problem... could you help post the steps?
Clipboard - 2018年3月12日晚上10点27分
Pick up a fabric version
Enter the subdir of specific version, e.g.,
$ cd 1.0.6 # select a fabric version
Quick Test
The following command will run the entire process (start a fabric network, create channel, test chaincode and stop it.) pass-through.
$ make setup # Install docker/compose, and pull required images
$ make test # Test with default fabric solo mode
ubuntu 16.04 , docker docker-compose ready
Clipboard - 2018年3月12日晚上10点30分
these pre-installed images are right,or need to delete
what's the result of `make setup`?
very strange, not seen this error before.
root@blockchain:~/go/src/v1.0.6# make setup
bash scripts/env_setup.sh # Installing Docker and Docker-Compose
Docker already installed
Docker-Compose already installed
bash scripts/download_images.sh # Pull required Docker images
Downloading images from DockerHub... need a while
=== Pulling fabric images 1.0.6 from yeasy repo... ===
1.0.6: Pulling from yeasy/hyperledger-fabric-base
Digest: sha256:6a3c512635ac57ea2ee6f0cd9dd7ae01fc83dc76ebb8947ff9ee05b571d84f25
Status: Image is up to date for yeasy/hyperledger-fabric-base:1.0.6
1.0.6: Pulling from yeasy/hyperledger-fabric-peer
Digest: sha256:679d95562233404629f8b67c13a838d3b2ac3338f6595bc5d4b1cadb908a10b7
Status: Image is up to date for yeasy/hyperledger-fabric-peer:1.0.6
1.0.6: Pulling from yeasy/hyperledger-fabric-orderer
Digest: sha256:069b09ef78913a28beec3d2b68ad574cb0d0aa40cdd8190fc3117963649fc965
Status: Image is up to date for yeasy/hyperledger-fabric-orderer:1.0.6
1.0.6: Pulling from yeasy/hyperledger-fabric-ca
Digest: sha256:892a408d2c5dad80b4707ce565af98281db68c5b445bc8ddc9ece42317fc02f5
Status: Image is up to date for yeasy/hyperledger-fabric-ca:1.0.6
1.0.6: Pulling from yeasy/hyperledger-fabric
Digest: sha256:0d975977d02132f030fd2dc8858efaed0e7c5c1b365808b5193ff33c18774ba4
Status: Image is up to date for yeasy/hyperledger-fabric:1.0.6
0.1.0-preview: Pulling from yeasy/blockchain-explorer
Digest: sha256:afaabf01f15ef0be3922ac501365db78f35cc52f0856907899daeb2839dc574e
Status: Image is up to date for yeasy/blockchain-explorer:0.1.0-preview
=== Pulling base images 0.3.2 from fabric repo... ===
x86_64-0.3.2: Pulling from hyperledger/fabric-baseimage
Digest: sha256:22bf2179146117c3a9e9a890bdd22f977d3b9d96d1c4a150e82bdff6d6e93017
Status: Image is up to date for hyperledger/fabric-baseimage:x86_64-0.3.2
x86_64-0.3.2: Pulling from hyperledger/fabric-baseos
Digest: sha256:df3d05e438bcdc3454469877bb5dc99b77dd37a78b9343848aacfdb918b34ca4
Status: Image is up to date for hyperledger/fabric-baseos:x86_64-0.3.2
=== Pulling fabric images 1.0.6 from fabric repo... ===
x86_64-1.0.6: Pulling from hyperledger/fabric-peer
Digest: sha256:0644a13f2d663364df4f413ae18d3b03647a70f9b08cde0c9b235006488e6001
Status: Image is up to date for hyperledger/fabric-peer:x86_64-1.0.6
x86_64-1.0.6: Pulling from hyperledger/fabric-tools
Digest: sha256:f755c8eb5d38de3c5a5c933eb2a73984fd1c03af85d4a6b07c9dc13781a1c30b
Status: Image is up to date for hyperledger/fabric-tools:x86_64-1.0.6
x86_64-1.0.6: Pulling from hyperledger/fabric-orderer
Digest: sha256:c74234ffdc4ea6bb2fb97767786bc4800c851f740ef14180115926432ed0aeea
Status: Image is up to date for hyperledger/fabric-orderer:x86_64-1.0.6
x86_64-1.0.6: Pulling from hyperledger/fabric-ca
Digest: sha256:4e36ca05f3bfe17b2efcbf231d3489f3ce9128a7bf2b2272919ec66a6b0436ee
Status: Image is up to date for hyperledger/fabric-ca:x86_64-1.0.6
x86_64-1.0.6: Pulling from hyperledger/fabric-ccenv
Digest: sha256:1df4ca28b14d395761b7c0df8f71ae2672175d93d27fbf9d608325ce59a29f71
Status: Image is up to date for hyperledger/fabric-ccenv:x86_64-1.0.6
x86_64-1.0.6: Pulling from hyperledger/fabric-couchdb
Digest: sha256:0908777cf9d3617060b8f1d7107ea518632b713e3cb429426b9dbbe66a3235ad
Status: Image is up to date for hyperledger/fabric-couchdb:x86_64-1.0.6
x86_64-1.0.6: Pulling from hyperledger/fabric-kafka
Digest: sha256:f9780a41129fe7872b1522b5c7f06f95d7961899125c64fe5ebbc30b0342b9bf
Status: Image is up to date for hyperledger/fabric-kafka:x86_64-1.0.6
x86_64-1.0.6: Pulling from hyperledger/fabric-zookeeper
Digest: sha256:b50e27e5b476ccd9443b882324877adf7bdf55a903f14924c6d1a8935ac860f9
Status: Image is up to date for hyperledger/fabric-zookeeper:x86_64-1.0.6
8.0: Pulling from library/mysql
Digest: sha256:a01485bf022e22af276164c595ae14eaf34d84fb326eea062c1b0d55635b6754
Status: Image is up to date for mysql:8.0
Image pulling done, now can startup the network using docker-compose...
baohua
@yinzhiwu can u run `make` after that. besides, what's your os type?
@all Dear all, we will have the group meeting at 10AM this Wednesday morning, pls help update the agenda at https://wiki.hyperledger.org/groups/twgc/meeting/2018-03-14 before the meeting, welcome to join, thanks!
root@blockchain:~/go/src/v1.0.6# lsb_release -a
LSB Version: core-9.20160110ubuntu0.2-amd64:core-9.20160110ubuntu0.2-noarch:security-9.20160110ubuntu0.2-amd64:security-9.20160110ubuntu0.2-noarch
Distributor ID: Ubuntu
Description: Ubuntu 16.04.3 LTS
Release: 16.04
Codename: xenial
run make, the same question too
ali yun server
@baohua
interesting, i've tested with the same os in my local vm, and it works.
can u help run a vm using virtualbox on your client laptop or pc? People have reported several issues with aliyun to run fabric, i cannot guess whether it's related now.
vmware is also ok?
I shall try
Has joined the channel.
meeting agenda today: https://wiki.hyperledger.org/groups/twgc/meeting/2018-03-14
https://wiki.hyperledger.org/groups/twgc/events/guideline
Has joined the channel.
@baohua 3月24日 北京大学的活动的 门票url 能否 在这里也发一下阿 ？
活动页面创建后会在这里发出报名link
谢谢
嗯 为了及时收到各种活动信息，可以注册到邮件列表：https://lists.hyperledger.org/mailman/listinfo/hyperledger-twg-china
注册了，还没有通过。
Has joined the channel.
Has joined the channel.
Hyperledger Technical Working Group in China
wiki.hyperledger.org/groups/tsc/twgc
Maillist: hyperledger-twg-china@lists.hyperledger.org
wiki.hyperledger.org/groups/twgc
谁能提供一些fabric多服务器部署的案例
Has joined the channel.
Has joined the channel.
请教一个问题：
请教一个具体问题，在fabric-samples/basic-network 中的docker-compose.yml 文件（部分摘录如下）。
image: hyperledger/fabric-ca
environment:
- FABRIC_CA_HOME=/etc/hyperledger/fabric-ca-server
- FABRIC_CA_SERVER_CA_NAME=ca.example.com
- FABRIC_CA_SERVER_CA_CERTFILE=/etc/hyperledger/fabric-ca-server-config/ca.org1.example.com-cert.pem
- FABRIC_CA_SERVER_CA_KEYFILE=/etc/hyperledger/fabric-ca-server-config/4239aa0dcd76daeeb8ba0cda701851d14504d31aad1b2ddddbac6a57365e497c_sk
问题：在/etc 路径下，我的系统没有hyperledger 文件夹以及后面的文件或者文件夹，为什么这个docker-compose.yml 文件environment要这么定义，同时《hyperledger-fabric-document .pdf》中没有关于如何修改这环境变量的说明，真不知道我使用“docker logs -f ca.example.com
”查找日志看到的错误“Error: Failed to find private key for certificate in '/etc/hyperledger/fabric-ca-server-config/ca.org1.example.com-cert.pem': Could not find matching private key for SKI: CSP:500 - Failed getting key for”是否与docker-compose.yml 有关？
@george19120 参考docker-compose的volumes配置，要把本地文件夹映射到容器里
Has joined the channel.
@baohua vitualbox, ubuntu16.04, Fabric 1.0.5, work
@baohua virtualbox, ubuntu16.04, Fabric 1.0.5, work
thanks
http://www.huodongxing.com/event/5431230398100
超级账本北京面对面（Hyperledger Beijing Meetup）
请问有hyperledger的微信讨论群吗
@labcoinpoc,谢谢，你的提醒，问题已经解决。
@siyuyifang ，深圳什么时候有活动。
Has joined the channel.
@george19120 深圳什么时候有活动，我不清楚哈~ 你可以关注下微信的 “Hyperledger超级账本官微”公众号，上周五的时候有发布北京、武汉、上海、杭州的Meetup。其他的暂时没有吧~
目前，深圳的志愿者团队暂时还未建立，欢迎各位在深圳的热心同仁积极牵头，组织当地的技术交流活动。
工作组这边可以帮忙联络讲师和进行指导、宣传。
请问用户链码中输出到标准输出的内容/fmt.Printf(...)之类，如何显示/查看？
Has joined the channel.
Has joined the channel.
Has joined the channel.
Has joined the channel.
Has joined the channel.
各位大牛， 请问一下如果在区块链上记录复杂的数据结构， 有什么可以推荐的私链选择
Has joined the channel.
我问一个跨链的问题：peer0.org1在通道mychannel上安装了chaincode_example02，Peer0.org2在通道testchannel上安装了chaicode_example04，peer0跨链调用不成功
chaincode_exmple04调用chaincode_example02
Has joined the channel.
blockchain.001.jpeg
hyperledger.001.jpeg
可以一起交流关于hyperledger方面的知识
hyperledger.001.jpeg
Screen Shot 2018-03-21 at 22.25.10.png
Screen Shot 2018-03-21 at 22.24.58.png
@jack21 群已满，邀请我一下：jchenibm
多谢
Has joined the channel.
Has joined the channel.
[ ](https://chat.hyperledger.org/channel/twg-china?msg=BWAK7dXMC2njFjPGy) @songyuanjie 必须在同一peer上安装才可以调用
@Hangyu 在同一个peer上安装了，是不是还得是同一个安装者才能调用，比如peer0在mychannel上安装chaincode_example02，在testchainnel上安装chaincode_example04，然后04才能进行跨链调用02？
[ ](https://chat.hyperledger.org/channel/twg-china?msg=taMGgCLFskpM5PCRF) @songyuanjie 对的。而且跨channel调用只能读不能写
@Hangyu 嗯，看来我的测试结果是对的。另外，是不是在同一个通道上，进行链码的相互调用也不能改变被调用链码的状态，比如：peer0在同一个通道mychannel上部署了chaincode_example04和chaincode_example02，那么peer0通过04调用02，尽管调用成功，但是没有改变02中的变量状态，即同通道中只读不写？
[ ](https://chat.hyperledger.org/channel/twg-china?msg=ehKmYQQBtoPc64KJ2) @songyuanjie 在同一通道上是可以写的啊。。。只有不同channel的时候只能读不能写
@Hangyu 在同一个通道中我跑chaincode_example04例子，都未能改变chaincode_example02的状态
[ ](https://chat.hyperledger.org/channel/twg-china?msg=gDqHSkaMjrYrZuNKT) @songyuanjie https://github.com/hyperledger/fabric/blob/release-1.1/examples/chaincode/go/passthru/passthru.go 试下这个例子
@Hangyu 嗯，我试一下。你也是通过CLI进行调用的吧？
[ ](https://chat.hyperledger.org/channel/twg-china?msg=xZCkwDn8qgQPDeAn4) @songyuanjie 是的。
@Hangyu 在CLI容器中peer chaincode 命令如果太长，它不会自动换行，这个很痛苦，你有什么更好的方法吗？
为一个问题：fabric中的链码deploy是将链码放到区块链中，同一通道中的peer都可以从链上查询到这个链码，这样的话还需要peer还需要install吗？
问一个问题：fabric中的链码deploy是将链码放到区块链中，同一通道中的peer都可以从链上查询到这个链码，这样的话还需要peer install吗？
@songyuanjie \
@yinzhiwu \:grin:这个也是很无奈
Clipboard - 2018年3月23日上午11点04分
有没有做过性能测试的, 大致做了下看起来性能并不是很乐观啊
@baohua 官方有没有出过性能报告
v1.1的关键的新功能包括：
Node.js的链码支持 - 开发人员现在可以使用世界上最流行的编程语言和最流行的框架编写chaincode了
基于通道的事件服务 - 使客户能够按每个通道订阅区块和区块交易事件
能够使用chaincode打包CouchDB索引，以提高性能
能够生成证书吊销列表（CRL）
能够动态更新客户身份和隶属关系
Node.js SDK连接配置文件可简化与Fabric节点的连接
Fabric节点之间以及客户端和节点之间的双向传输层安全性（TLS）
能够使用链码加密库加密账本数据，保证机密性
链码新增对基于属性的访问控制的支持
提供Chaincode API检索获取客户端标识以便进行访问控制决策
提高了交易吞吐量和响应时间的性能
https://mp.weixin.qq.com/s/Uv6HTPKzIxwEYUvxn_0XcA
https://jira.hyperledger.org/browse/FAB-3156，这里说的实例化策略审查起到什么作用？
@CarlXK 官方有篇论文你可以看看，里面有些性能数据：Hyperledger Fabric: A Distributed Operating System for Permissioned Blockchains
Has joined the channel.
Has joined the channel.
rocket chat address
Has joined the channel.
Finally, in this experiment, we measured over 3560 transactions per second (tps) average spend (end-to-end) throughput at the 32- vCPU peer. The mint throughput is, in general, slightly lower than that of spend, but the di erence is within 10%, with 32-vCPU peer reaching over 3420 tps average mint throughput.
tps 已经这么高了, 这么牛逼?
@baohua
@baohua 上周六 在北京大学举办的 超级账本北京面对面 活动，有视频吗？
@CarlXK it should make sense, but i've never found where is the testbed code. maybe u can contact the authors to ask for it.
@xiangyue there's live video, but seems no replay. maybe u can watch the wikipage to find the slides.
https://wiki.hyperledger.org/groups/twgc/team_eo
@baohua 谢谢, 我找找看
@baohua 谢谢。
1.1.0加入了拜占庭算法了么? @baohua 我看这个文档里面很多出提到了拜占庭
@CarlXK 没有
Screen Shot 2018-03-26 at 15.02.16.png
Has joined the channel.
Has joined the channel.
@all Dear all, we will have the group meeting at 10AM this Wednesday morning, pls help update the agenda at https://wiki.hyperledger.org/groups/twgc/meeting/2018-03-28 before the meeting, welcome to join, thanks!
请教个问题，peer joinchannel的时候 通过gprc调用服务端的chat 然后就stream.on(data,...) stream.on(end,...) 接着写了一个signedEvent流 这里的stream.on在什么时候会触发 是做了joinchannel的时候触发 还是跟joinchannel没关系？ 如果没关系为什么要做个注册
@baohua 杨老师请教一下，fabric1.1的版本我看去掉了pbft算法，只有kafka，是为什么呢？
https://wiki.hyperledger.org/groups/twgc/meeting/2018-03-28?&#agenda
@mrFranklin since 1.0, it's removed :)
Has joined the channel.
Has joined the channel.
substitute with SBFT right？终于找到twg-China，还以为没这个聊天组
Has joined the channel.
good evening everyone, this is Rich from IBM, I am glad to be here
I am in Shenzhen, I can org meetup in shenzhen
Has joined the channel.
also in shenzhen
I wish i'm in ShenZhen:sob:
各位大神请教个问题，composer开发环境搭建好后创建的peeradminCard是什么，card也是指BNA包吗？
地址
@davidhu card打包了连接配置文件和用户身份
Has joined the channel.
Welcome @richzhao
谢谢杨老师
I want to host a meetup in sz，any suggestion everyone?
hi, u mean shenzhen?
yes, In shenzhen
it's a great idea! Hyperledger has several member companies in Shenzhen including tencent and huawei, i guess it would be good to collaborate together to make the meetup.
yes, I agree. do you have their contacts?
yes, @jiangyaoguo is from huawei
ok
besides, we will have bi-weekly meeting in the morning of next Wednesday, welcome to attend and share the plan: https://wiki.hyperledger.org/groups/twgc
sure
any meetup experience in other city can be shared with me?
sure, in summary, we need some hosting place and speakers, and usually 100~200 people is a good size
and be care of: 1) the sharing topic should be focused on techniques, better related to hyperledger specifically; 2) non-recorded commercial advertisement.
If you need help on more speakers, can come to the meeting, let's find more candidate there including experts from LF or other companies.
of cause
Has joined the channel.
Has joined the channel.
Has joined the channel.
话说在杭州有hyperledger定期的技术交流会吗？
有人遇到这个问题吗
Clipboard - 2018年4月8日下午4点08分
grpc 传输最大限制 4M，有人知道在哪里改吗
Has joined the channel.
@liutuol 我也是杭州的
现在超级账本有中文社区嘛
我找了一圈都没有找到
有的，杭州的趣链、浙江区块链应用协会都是超级账本会员，上个月刚开了一期meetup
有的，杭州的趣链、复杂美、浙江区块链应用协会等都是超级账本会员，上个月刚开了一期meetup
https://wiki.hyperledger.org/groups/twgc/hangzhou-meetup-2018-03
杭州本地贡献者可加超级账本杭州社区微信群
@here Dear all, we will have the group meeting at 10AM this Wednesday morning, pls help update the agenda at https://wiki.hyperledger.org/groups/twgc/meeting/2018-04-11 before the meeting, welcome to join, thanks!
@baohua 谢谢
[ ](https://chat.hyperledger.org/channel/twg-china?msg=pwrhpNFi9WXHj53dF) @qingsongGuo sdk config文件里
2018-04-10 16:58:39.029 CST [orderer/common/broadcast] Handle -> WARN 20e [channel: testchannel] Rejecting broadcast of config message from ipaddress:51618 because of error: error authorizing update: error validating DeltaSet: policy for [Group] /Channel/Application not satisfied: Failed to reach implicit threshold of 1 sub-policies, required 1 remaining
2018-04-10 16:58:39.029 CST [orderer/common/server] func1 -> DEBU 20f Closing Broadcast stream
When I want to create channel the orderer output the above error message. It's about firewall or Cert and other issue?
Has joined the channel.
https://wiki.hyperledger.org/groups/twgc/meeting/2018-04-11?&#agenda
https://wiki.hyperledger.org/groups/twgc/team_ie/guideline
https://wiki.hyperledger.org/groups/twgc/team_eo
Could anyone send me a link of the wechat group of Beijing? I will soon come to Beijing as a blockchain developer. I would like to promote our team to consider fabric as the primary option. Wanting to join the community.
hi，you can add wechat `a1141628710`, and noted that wanna join the beijing group.
@baohua Thank you very much.
Has joined the channel.
Has joined the channel.
求教，目前联盟链网络跑起来之后如果希望添加新的 Org 进入的话，是必须要重启整个网络的吧？
@yuqian0218 http://hyperledger-fabric.readthedocs.io/en/release-1.1/channel_update_tutorial.html 这有个教程，不需要重启，不过也挺复杂
好的，谢谢
深圳的社区群成立啦，深圳的小伙伴可以加入！
Clipboard - April 13, 2018 11:26 AM
请问有没有北京的群？
各位好，我最近在看 A Distributed Operating System for Permissioned Blockchains 这篇文章，对里面提到的 Fabric 1.0 execute-order-validate 模型有点疑问，想向大家请教下
我的理解，在 execute 阶段，每个 endorser 会基于本地最新的 state db，将 proposal 模拟执行的结果封装成 readset 和 writeset ，返回给 client。 readset/writeset 分别是由一组 (key, value, version) 构成。
在 validate 阶段，PTM (Peer transaction manager) 会依次对 block 中的 transaction 进行 validate，如果 transaction 依赖的 readset 中的 version 和当前最新的 state db 中不一致，则该 transaction 会被标记为 invalid。
这么看的话，如果需要对某个 state 频繁修改（例如一个 block 内包含多个对该 state 的修改），invalid transaction 的概率是不是会非常高？
或者说，如果 Tx1 和 Tx2 都需要对某个 state 进行修改，在 Tx1 未被 validate 前，能否做到 Tx2 的 readset 里依赖的是 Tx1 的输出（writeset）？
这是分布式模型的老问题，可参考： https://github.com/hyperledger/fabric-samples/tree/release/high-throughput
多谢杨老师，我先看下这个文档
@baohua 我看了您发的文档，介绍的是如何在 chaincode 内去避免对同一个全局 state 的频繁修改，从而实现 high throughput 。主要的方法还是将业务数据增量化表示，每个 transaction 里包含的是某个业务数据的增量信息而不是全量信息，不知道这样理解对吗？
其实我想问的就是，在 Fabric 的 execute-order-validate 层面，readset/writeset 中对 state db 的修改，是增量的还是全量的？ 如果是全量的，那就必须得在 chaincode 层面去解决高并发的问题了
rwset中仅对里面相关的数据进行check，并非整个world state
嗯，这个我理解
总结下，您看对吗：
1. Fabirc 1.0 的 execute-order-validate 模型下，如果两个 Tx 对 world state db 中同一个 KV 进行了修改（它们都还未被 validate），则最多只有一个 Tx 可以被认定为有效；
2. 业务方需要在 chaincode 里去避免对 world state db 中同一个 KV 的频繁修改，从而实现 high throughout。
总结下，您看对吗：
1. Fabirc 1.0 的 execute-order-validate 模型下，如果两个 Tx 对 world state db 中同一个 KV 进行了修改（它们都还未被 validate），则最多只有一个 Tx 可以被认定为有效；
2. 业务方需要在 chaincode 里去避免对 world state db 中同一个 KV 的频繁修改，从而实现 high throughput。
总结下，您看对吗：
1. Fabirc 1.0 的 execute-order-validate 模型下，如果两个 Tx 对 world state db 中同一个 KV 进行了修改（它们都还未被 validate），则最多只有一个 Tx 可以被认定为有效；
2. 业务方需要在 chaincode 里去避免对 world state db 中同一个 KV 的频繁修改（例如文章中 Fabcoin 的 UTXO 实现），从而实现 high throughput。
对的
多谢解惑 :)
Has joined the channel.
各位好，可以使用本地的安全模块产生秘钥后提交公钥到 ca 中申请证书吗？
Has joined the channel.
TWGC's new mail list is ready now (old data has been migrated): https://lists.hyperledger.org/g/twg-china
有武汉社区吗？
大家好，有个问题请教一下大家：
我目前部署了一套多节点的环境，1orderer，2peer。版本是1.1.0
以及 composer-playground，版本是0.19.1
运行 composer-playground 以后，通过浏览器，创建新的 BNC：
大家好，有个问题请教一下大家：
我目前部署了一套多节点的环境，1orderer，2peer。版本是1.1.0
以及 composer-playground，版本是0.19.1
运行 composer-playground 以后，通过浏览器，创建新的 BNC：
Hyperledger Fabric v1.1
Connect to a new v1.1 Blockchain
录入相关节点的信息，orderer、peer 节点的 ip 地址以及域名信息，ca 服务器的名称以及url，点击 next 创建，
在接下来的页面输入 admin 节点的证书文件信息以及私钥信息，点击创建，创建该 BNC
创建好 BNC 后，在这个新创建的 card 下创建新的商业网络（Deploy a new business network），
选择任意模板，并填入 admin 节点的证书文件信息以及私钥信息。
在点击deploy 部署该商业网络后，从后台peer 节点的 debug 日志信息可以看到peer节点在创建链码的容器，在等待了大概12分钟以后，链码容器创建成功，
但是 composer-playground前端页面返回错误信息：
An error has occurred
Error:Failed to import identity.Error:priavtekey not specified or not a string
请教一下：
1. peer 节点创建链码容器的时候为什么会那么慢？有什么解决办法？
2. fabric 服务已经创建成功，为什么前端会有这个错误？
屏幕快照 2018-04-20 下午8.55.29.png
当我在创建 bnc ，以及部署链码的时候使用 fabric-ca-server的用户名密码去 enroll 用户证书的时候。会返回如下错误信息：
Error: Error trying to start business network. Error: Error: 2 UNKNOWN: access denied: channel [composerchannel] creator org [Org1MSP]
Has joined the channel.
R6hFclSbnuvhm0QqpaPo.jpeg
大家好，我在运行fabric-samples的first-network中的byfn.sh时，出现如下问题：
IMG_0185.jpeg
请大师指点一下！
Attempting to Query PEER0 ...3 secs
Attempting to Query PEER0 ...6 secs
Attempting to Query PEER0 ...9 secs
Attempting to Query PEER0 ...13 secs
Attempting to Query PEER0 ...16 secs
Attempting to Query PEER0 ...19 secs
Attempting to Query PEER0 ...22 secs
Attempting to Query PEER0 ...25 secs
Attempting to Query PEER0 ...28 secs
Attempting to Query PEER0 ...31 secs
Attempting to Query PEER0 ...34 secs
Attempting to Query PEER0 ...38 secs
Attempting to Query PEER0 ...41 secs
Attempting to Query PEER0 ...44 secs
Attempting to Query PEER0 ...47 secs
Attempting to Query PEER0 ...50 secs
Attempting to Query PEER0 ...53 secs
Attempting to Query PEER0 ...56 secs
Attempting to Query PEER0 ...59 secs
Attempting to Query PEER0 ...62 secs
2018-04-21 03:28:29.956 UTC [msp] GetLocalMSP -> DEBU 001 Returning existing local MSP
2018-04-21 03:28:29.956 UTC [msp] GetDefaultSigningIdentity -> DEBU 002 Obtaining default signing identity
2018-04-21 03:28:29.956 UTC [chaincodeCmd] checkChaincodeCmdParams -> INFO 003 Using default escc
2018-04-21 03:28:29.956 UTC [chaincodeCmd] checkChaincodeCmdParams -> INFO 004 Using default vscc
2018-04-21 03:28:29.956 UTC [msp/identity] Sign -> DEBU 005 Sign: plaintext: 0A95070A6708031A0C08DDDFEAD60510...6D7963631A0A0A0571756572790A0161
2018-04-21 03:28:29.957 UTC [msp/identity] Sign -> DEBU 006 Sign: digest: 40A5B2539AFF5B8E45008ACFE6542A9F64AC887215260DA8D948202CFAC443C0
Error: Error endorsing query: rpc error: code = Unknown desc = could not find chaincode with name 'mycc' - make sure the chaincode mycc has been successfully instantiated and try again -
Has joined the channel.
chaincode启动不成功，具体原因看不出来。你用的是啥版本
@here
Dear all, we will have the group meeting at 10AM this Wednesday morning, pls help update the agenda at https://wiki.hyperledger.org/groups/twgc/meeting/2018-04-25 before the meeting, welcome to join, thanks!
国内有什么超级账本的技术群， 求拉
请问我在使用 “peer chaincode instantiate” 后会出现一个新的 docker container，名字会是 “dev-peer0”，请问这个 dev 是开发模式吗？但是我并没有设置 --peer-chaincodedev=true。
杨老师好，我跑的是1.0版本
java-sdk 1.0.0版本 与 fabric 1.1.0版本 能兼容吗 @baohua
go sdk是兼容的，java的我没试过
@baohua 上海微信群能加入吗
Has left the channel.
@chenxi
可加yudianbabasheng 好友拉入
北京有微信群吗？
@YorkYu see here: https://wiki.hyperledger.org/groups/twgc
请问：超级账本中的背书节点是如何选择的？
-p 指定链码背书节点策略
一系列环境变量，比如CORE_PEER_ADDRESS
Has joined the channel.
现在官方文档使用fabric-samples案例帮助用户入手，环境是基于单机docker下部署，有这么一点想提一下：关于动态添加节点，其中Bring Org3 into the Channel Manually 部分，执行命令“./eyfn.sh down”即删除所有容器，这不符合实际应用场景，只应该停掉新增的节点。整个文档都是基于单机docker 部署的，这种例子还有很多。给初学者一种错觉，就好像本机入口是一个上帝视角，超级管理员，随时对整个网络有启停操作，这不符合区块链实际场景。 http://hyperledger-fabric.readthedocs.io/en/release-1.1/channel_update_tutorial.html
新增组织时，规则是：多数组织（不是全部组织）给修改channel的配置交易进行签名。
但是，在许可链上，难道不应该是全部组织都给这个交易签名才可以吗？这个规则难道是可定制的？
新增组织，这种低频且重要的操作，相信每一个链上组织都不会放弃控制权而提升效率的。
真正效率低的情况可能仅仅是个别组织内所有节点都离线，签名过程阻塞，组织一般会极力避免这种情况发生。
即使发生了，发生的同时又遇到新增组织的交易的概率当然更低。
即使仍然发生了，底层也应该等待该组织上线才行。
除非新组织加入channel对链上组织没有利益冲击，或者只有益处没有坏处。
如果仍然考虑到效率问题，那真的有可察觉的效率降低情况，必然是组织总数已经很庞大，而Fabric的场景本身就不是用于这种大量节点的情况。
Has joined the channel.
权限管理的policy是可以定制的，根据具体需求来细化的控制。
fabric-samples-1.1.0里面的first-network项目，背书策略是"OR ('Org1MSP.peer','Org2MSP.peer')"，这个是可定制的，但是新增组织时是按多数节点的规则来的。我的疑点：1、要么背书策略对配置交易无效，只对普通交易有效，配置交易的“大多数规则”是在别处定制的或者是在代码里面hardcode的。2、要么背书策略是对所有交易有效，包括增加组织的配置交易，那么在sample项目提到的“大多数原则”是同时存在的一个规则，只有满足“大多数原则”又满足背书策略，配置交易才有效？
在这个项目里面，只有两个Org都签名才可以新增组织，这个规则文档解释是大多数规则，按背书策略任选一个即可，但是按照“大多数原则”2个组织1不能构成大多数，只能是两个
Has joined the channel.
哈哈，总算找到组织了
想在节 peer 和应用直接加一层 rest api，请问哪套框架比较好用?
[ ](https://chat.hyperledger.org/channel/twg-china?msg=sNWunBHffTdia4x9N) @KevinBai peer和application之间本来就有官方基于grpc的SDK通信，为什么再加一层rest API？
Problem：fabric-1.1.0相对1.0.6升级，限制了fabric的扩展性
要求：必须是整个channel的所有peer和orderer都升级才能保持账本的一致性，否则就会分叉
问题：根据业务场景的相关性，一个网络中的多个channel一般是互联在一起的，如果一个channelA升级，相关channelB和channelA的交叉节点就和channelB之间产生分叉的情况，除非全网络升级，但是因为区块链网络的分布式特性，又不可能全网升级，所以现在的升级策略不是一个好的方案。
结论：fabric-1.1.0相对1.0.6升级，限制了fabric的扩展性
要求：必须是整个channel的所有peer都升级或者所有orderer都升级才能保持账本的一致性，否则就会分叉
Problem：根据业务场景的相关性，一个网络中的多个channel一般是互联在一起的，如果一个channelA升级，相关channelB和channelA的交叉节点就和channelB之间产生分叉的情况，除非全网络peers升级，但是因为区块链网络的分布式特性，又不可能全网升级，所以现在的升级策略不是一个好的方案。
Capability的管理粒度太粗，解决不了上面这个问题
大家好，请问大家使用composer-playground部署链码的时候有没有遇到这个错误？
Error: 2 UNKNOWN: access denied: channel [tc1] creator org [Org1MSP]
大家好，请问大家使用composer-playground部署链码的时候有没有遇到这个错误？
Error: Failed to import identity. Error: privateKey not specified or not a string
client和背书节点进行通信，根据CORE_PEER_ADDRESS指定了背书节点的IP地址，但是PEER_ADDRESS只可能制定一个背书节点，当有多个背书节点时，又给怎样指定，client与这些背书节点又该怎么链接？
[ ](https://chat.hyperledger.org/channel/twg-china?msg=v6fWXX5SAKD66Dorv) @guolidong 主要是客户那使用 c# 写的，只能中间加一层东西了，不知道您有什么其他方案没 ？目前好像做一个 rest 服务最简单了？
[ ](https://chat.hyperledger.org/channel/twg-china?msg=t3DwfymJqvup5e44t) @KevinBai 客户数据上链肯定是经过你们的application吧？不然就不叫你们的客户了，你们application里面使用fabric SDK，这包括应用是在同一层。然后对客户提供API。客户用不用C#跟你们没关系，只要调用API就可以了。
@guolidong 我们算是和他们合作，想帮他们现有业务的部分改成 blockchain，会给他们建立一个 peer
@KevinBai 那没有C#的SDK，所以肯定要有一层API了。这样也好，你们跟他们的合作很解耦。
@guolidong 目前想到的这样最简单了，之前看了下 composer 项目，好像人家不是为了干这个用的
Has joined the channel.
大家好。看杨老师的书过来的，报个到，学习中:smile:
欢迎多交流！
@here Dear all, we will have the group meeting at 10AM this Wednesday morning, pls help update the agenda at https://wiki.hyperledger.org/groups/twgc/meeting/2018-05-09 before the meeting, welcome to join, thanks!
:ok_hand:
Has joined the channel.
大家好，我是一名研究生，来自南京农业大学，在看杨老师的书，请大家多多指导！多谢。:grinning:
welcome~
我在make生成docker镜像的时候报了一个错，是包不找不到，但是对应的包是存在的，不知道哪位高手能给点帮助，错误提示如下`bccsp/sw/ecdsa.go:27:2: cannot find package "crypto/gm" in any of:
/opt/gopath/src/github.com/hyperledger/fabric/vendor/crypto/gm (vendor tree)
/opt/go/src/crypto/gm (from $GOROOT)
/opt/gopath/src/crypto/gm (from $GOPATH)`
Jietu20180509-091647.jpg
大家注意zoom的地址更新为 https://zoom.us/my/hyperledger.community，别走错了/::P
@panzheng 用的是最新代码？看下几个目录下有没有那个包
https://wiki.hyperledger.org/groups/twgc/meeting/2018-05-09
@baohua 杨老师，我们这边用的是fabric1.0，这个包在gopath目录下是可以找到的，所以很困惑
北京的怎么加？
group 看到了 :blush:
@panzheng 怪了，你清理下已有的容器，看看是不是临时镜像干扰
Has joined the channel.
[ ](https://chat.hyperledger.org/channel/twg-china?msg=Btn9BmsJy4wKYzeW2) @panzheng 这个问题曾经困扰我很久才解决，这是因为你改了golang 源码在go/src/crypto/下面新增了东西，go已经不是官方的go了，所以你必须在fabric-baseimage镜像里面打包你修改之后的go，你下载fabric-baseimage的源码会看到脚本里面是在线下载官方go.tar.gz。你替换掉它就可以了。相关修改在我GitHub主页有分享相关代码，https://github.com/JulienGuo/fabric-baseimage-addsm
[ ](https://chat.hyperledger.org/channel/twg-china?msg=Btn9BmsJy4wKYzeW2) @panzheng 这个问题曾经困扰过我。这是因为你改了golang 源码在go/src/crypto/下面新增了东西，go已经不是官方的go了，所以你必须在fabric-baseimage镜像里面打包你修改之后的go，你下载fabric-baseimage的源码会看到脚本里面是在线下载官方go.tar.gz。你替换掉它就可以了。相关修改在我GitHub主页有分享相关代码，https://github.com/JulienGuo/fabric-baseimage-addsm
你编译fabric的peer，orderer这些component的时候，默认是从fabric-baseimage找的依赖，而不是从你local的go 环境找的依赖。
[ ](https://chat.hyperledger.org/channel/twg-china?msg=rvZXX5LzDL5Haj29L) @panzheng 这个问题曾经困扰过我。这是因为你改了golang 源码在go/src/crypto/下面新增了东西，go已经不是官方的go了，所以你必须在fabric-baseimage镜像里面打包你修改之后的go，你下载fabric-baseimage的源码会看到脚本里面是在线下载官方go.tar.gz。你替换掉它就可以了。相关修改在我GitHub主页有分享相关代码，https://github.com/JulienGuo/fabric-baseimage-addsm
请问上海的微信群管理员 yudianbabasheng 怎么用户不存在？ :eyes:
有问题可以发个信到 twg-china@lists.hyperledger.org 问下 @zhuquanbin
fabric-sdk-java1.1.0版本。启动fabric网络那个ccenv老是exitd的，直接跑End2endIT.java，一切都还好，只有这里error
问题1：是不是ccenv exited造成这个error的？
问题2：为什么ccenv exited我还是可以完整的跑完一次测试
peer1.org2.example.com | 2018-05-11 07:45:46.013 UTC [eventhub_producer] Chat -> ERRO 7ab error during Chat, stopping handler: rpc error: code = Canceled desc = context canceled
peer1.org2.example.com | 2018-05-11 07:45:46.014 UTC [eventhub_producer] deRegisterHandler -> DEBU 7ac deregistering event type: BLOCK
peer0.org2.example.com | 2018-05-11 07:45:46.014 UTC [eventhub_producer] Chat -> ERRO 82e error during Chat, stopping handler: rpc error: code = Canceled desc = context canceled
ccenv 每次创建node合约的时候都会去网络下载依赖 网络环境不好 每次都要下好久
各位专家和大牛～ 有个问题请教下，Java sdk一般是调用HFCAClient去进行操作，如果Org和peer和用户是通过cyrptogen创建的，没有启用CA，Java sdk去做调用chaincode，怎么获取用户等信息？
Has joined the channel.
@baohua cnofigtx.yaml里的Application section定义的是什么角色？共识节点、记账节点还是连接记账节点的客户端应用。
@baohua cnofigtx.yaml里的Application section定义的是什么角色？共识节点、记账节点还是连接记账节点的客户端应用。明白了
@baohua cnofigtx.yaml里的Application section定义的是什么角色？共识节点、记账节点还是连接记账节点的客户端应用。明白了，是orderer或peer的成员。
2018-05-13 18-27-41屏幕截图.png
我该怎么样才能获取fabric镜像
请各位大佬给个帮助
我们实验室的网是可以访问外网的，不过网速很慢，不知道是不是这方面的原因还是我哪里配置有错
请教各位一个问题，如果一个内部网络没有开启组播（MULTICAST），fabric还可以正常使用吗？如果不能，有没有解决方案？谢谢
跟组播没关系，走的是点对点构造的gossip算法
@here 超级账本2018首场深圳meetup将于5月26日在清华大学深圳研究生院举行，开放报名中：http://www.huodongxing.com/event/6440053577100?td=1932897455728。
谢谢
请问应用服务器和 peer 直接的连接是长时间的还是短时间的？发现我的应用在和 peer 长时间连接后，一段时间做查询会出现 grpc 的错误： TCP Read failed
我不太清楚在实际使用过程中是应该保持长时间连接，还是每次有请求在连接到 peer
我用的是 fabric-sdk-node
@baohua 杨老师，深圳的微信群二维码能发一下么，之前发的过期了，谢谢！
Has joined the channel.
[ ](https://chat.hyperledger.org/channel/twg-china?msg=viGat37ygYkxM26zE) 找到原因了，是 azure 的 vm load balancer 有 4分钟的 TCP keep-alive 限制，问题是最长只允许修改到 30 分钟，不知道有类似的问题的朋友没？
@chenshiok 看这里 第3部分有加入方式：https://wiki.hyperledger.org/groups/twgc#communications
Clipboard - May 18, 2018 5:09 PM
[ ](https://chat.hyperledger.org/channel/twg-china?msg=oKjDTfauekd5JJ576) @KevinBai 我这里的AWS的LB也是一分钟没数据就切断连接，所以我们有个基于websocket的应用现在每30s发个ping给服务器
zoom的会议开始了吗
搞错了
@labcoinpoc 谢谢您，我把几个 vm 放在了 azure 的同一个组里，使用内网 ip 连接貌似不会出现类似的问题，而且也可以节省资源。我不太懂运维这块，不知道哪位了解这方面帮忙做个科普？
@here Dear all, we will have the group meeting at 10AM this Wednesday morning, pls help update the agenda at https://wiki.hyperledger.org/groups/twgc/meeting/2018-05-23 before the meeting, welcome to join, thanks!
咨询个问题：如果 channel genesis block 里的 OrdererAdresses 不存在了（创始 orderer 挂掉了，通过 channel 更新已经增加了新的 orderer 到 config block 里），那么新启动的 peer 还能同步到该 channel 的 block 吗？
genesis block 可以有多个orderer地址。但没有genesis block，peer没法启动。
[ ](https://chat.hyperledger.org/channel/twg-china?msg=Xn4Kx6ncayG94TPoP) @baohua
[ ](https://chat.hyperledger.org/channel/twg-china?msg=Xn4Kx6ncayG94TPoP) @baohua 假设以下操作步骤：
1. channelA 创建时只有 ordererA 的地址
2. 通过 channelA update 加入了 ordererB 和 ordererC 地址
3. ordererA 因为某些原因挂掉了（或失效了）
4. 新的 peer 启动能获取 channelA 的区块吗？
如果peer用的是1中的gb，则不能，因为压根都连不到orderer上。
如果peer(leader)用的是1中的gb，则不能，因为压根都连不到orderer上。如果不是leader，则不影响。
peer 可以用非 genesis block 来 join channel 吗？
应该不行，目前还不支持prune/checkpoint
[ ](https://chat.hyperledger.org/channel/twg-china?msg=4YXu9AM5BpQQhY49v) @baohua 那这是一个很严重的 bug 啊，如果 channel genesis block 里只有一个 orderer（而这个 orderer 恰好挂掉了），其它 peer 就再也无法加入这个 channel 了
well, i would say in practical, there should be multiple orderers, otherwise, it's a SPF and no one can help :)
[ ](https://chat.hyperledger.org/channel/twg-china?msg=yBPdrAuia4ufBcre8) @baohua 只是 genesis block 里只有一个 orderer，随着组织的增加会把新的 orderer 更新到 channel config 里的。如果 peer 必须 genesis block 才能加入 channel，这种限制显然不合理
not really, you can feel free to add more orderers, and remember at any time, at least keep one of them (those in the channel cfg) active. Then there will be no problem.
so peer can use "last config block" (not only the genesis block) of the channel to join this channel?
i'm not aware of that feature. is there any specific requirement to do so? save local storage?
[ ](https://chat.hyperledger.org/channel/twg-china?msg=ZXjM4qu2XmjCE6Rcv) @baohua channel 创始块中的 orderer 退出了，后续的 peer 无法再加入这个 channel 了（即使这个 channel 最新的配置块里还有其它存在的 orderer）。这个需求还是很常见的吧
hmm, in case that leader peers join/leave frequently and orderers change frequently, that might be true.. That's why we suggest avoid this case in practical, e.g., make the ordering service HA with multiple nodes, instead of single.
Has joined the channel.
Has joined the channel.
AY{E%A%GJS]][NI@6)3M{_9.png
请问 谁遇到过 “Failed to locate an MSP instance matching the endorser identity” 这个错误
Has joined the channel.
Has joined the channel.
大家好，我想问一下，通过不同的chiancode，可以在不同的channel中通信吗？invokechaincode的方式
Has joined the channel.
Has joined the channel.
Has joined the channel.
Has joined the channel.
Has joined the channel.
跨channel读可以
Clipboard - May 31, 2018 3:32 PM
这种情况谁知道什么原因？
Has joined the channel.
我想请教一下：在fabric共识机制的BFT模式下，没有了kafka的支持怎么实现多通道隔离来确保数据隐私？
Has joined the channel.
Has joined the channel.
Has joined the channel.
@here Dear all, we will have the group meeting at 10AM this Wednesday morning, pls help update the agenda at https://wiki.hyperledger.org/groups/twgc/meeting/2018-06-06 before the meeting, welcome to join, thanks!
@baohua 老师 想问下出现这个问题是为什么 一直卡在这里，网络端口也都正常开放 ping也没问题 ````
Instantiating chaincode on org2/peer2...
CORE_PEER_TLS_ROOTCERT_FILE=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org2.example.com/peers/peer0.org2.example.com/tls/ca.crt
CORE_PEER_TLS_KEY_FILE=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org1.example.com/peers/peer0.org1.example.com/tls/server.key
CORE_PEER_LOCALMSPID=Org2MSP
CORE_VM_ENDPOINT=unix:///host/var/run/docker.sock
CORE_PEER_TLS_CERT_FILE=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org1.example.com/peers/peer0.org1.example.com/tls/server.crt
CORE_PEER_TLS_ENABLED=true
CORE_PEER_MSPCONFIGPATH=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org2.example.com/users/Admin@org2.example.com/msp
CORE_PEER_ID=cli
CORE_LOGGING_LEVEL=DEBUG
CORE_PEER_ADDRESS=peer0.org2.example.com:7051
2018-06-05 01:47:00.257 UTC [msp] GetLocalMSP -> DEBU 001 Returning existing local MSP
2018-06-05 01:47:00.257 UTC [msp] GetDefaultSigningIdentity -> DEBU 002 Obtaining default signing identity
2018-06-05 01:47:00.260 UTC [chaincodeCmd] checkChaincodeCmdParams -> INFO 003 Using default escc
2018-06-05 01:47:00.260 UTC [chaincodeCmd] checkChaincodeCmdParams -> INFO 004 Using default vscc
2018-06-05 01:47:00.261 UTC [msp/identity] Sign -> DEBU 005 Sign: plaintext: 0A92070A6408031A0B0894D7D7D80510...324D53500A04657363630A0476736363
2018-06-05 01:47:00.261 UTC [msp/identity] Sign -> DEBU 006 Sign: digest: 2E08BE203DC920AEB6155F98218367AFFAB7AF64EA314DE99DA5BD00C9ACFBB4
Error: Error endorsing chaincode: rpc error: code = Unknown desc = Timeout expired while starting chaincode mycc:1.0(networkid:dev,peerid:peer0.org2.example.com,tx:f6407bf677b132ab87e894385cdf9913153da021f4fe4cf273ad512b6b7c0963)
Usage:
peer chaincode instantiate [flags]
``` `
从有限的信息上来看，我只能猜cc容器起不来。
Has joined the channel.
Has joined the channel.
@baohua 杨老师，你能拉我进北京的区块链学习群嘛？
@muuzisoft pls see here how to join: https://wiki.hyperledger.org/groups/twgc?&#communications.
Has joined the channel.
@baohua 好的，谢谢杨老师，已经进去了
Has joined the channel.
@baohua 同态加密目前有什么好的实现嘛？
Has joined the channel.
Has joined the channel.
大家好, 我用官方的fabric-ca sample建立的本地fabric网络, 在使用fabric-sdk-go 安装chaincode的时候, 老是报timeout的error.
Got error: lscc.getinstalledchaincodes failed: SendProposal failed: Transaction processing for endorser [localhost:7051]: Endorser Client Status Code: (2) CONNECTION_FAILED. Description: dialing connection timed out
谁能帮忙看一下吗
https://stackoverflow.com/questions/50792520/connection-timeout-when-installing-chaincode-using-fabric-sdk-go 这个是stackoverflow上的问题, 里面有docker-compose.yaml已经network-config.yaml的内容
https://stackoverflow.com/questions/50792520/connection-timeout-when-installing-chaincode-using-fabric-sdk-go
有人能帮我看看这个问题吗??
@CarlXK 目前最先进的应该还是Craig Gentry的工作，可以去搜搜看看
大家好，我最近遇到了一个动态更新系统通道上orderer组织的问题，想请教大家
hello, 各位.. 官方fabric-ca sample搭建的fabric网络. 在本地使用fabric-sdk-go安装链码时, 一直报bad certificate的错误.
net
docker
有谁知道是什么原因吗
找到原因了, 修复了
Has joined the channel.
Has joined the channel.
@here
Dear all, we will have the group meeting at 10AM this Wednesday morning, pls help update the agenda at https://wiki.hyperledger.org/groups/twgc/meeting/2018-06-20 before the meeting, welcome to join, thanks! （欢迎各地志愿者转发到地区群）
the meeting already ended today?
i advise the time of meeting in future can be arrange in the evening for Chinese developers. most of developers who are interested in open source can be available after work.
https://github.com/tjfoc/hyperledger-fabric-gm 有人编译过这个版本没有
Has joined the channel.
@abraham @baoyangc 我也同意改到晚上下班后的时间
@davidkhala 我不同意啊
上午开会有没有什么优势？
欢迎大家就自己合适的会议时间进行投票：https://doodle.com/poll/vtb4spgpc2azuw3e
Has joined the channel.
Has joined the channel.
@baohua 杨老师，我就是看您的书加的频道的:grinning:
@shuailaotou 欢迎，多多交流！
Has joined the channel.
Has joined the channel.
Has joined the channel.
请问，Fabric的数据是存储在CouchDB中，CouchDB作为一个数据库的角度，Fabric保存的数据可以通过比如utils修改吗？
请问 谁有fabric-sdk-java的api文档？
大家好，请问如何在cto定义模型的时候设置字段是可选的，看参考文档也没有说明
在后面加optional 即可
多谢
Has joined the channel.
@here Dear all, we will have the group meeting at 10AM this Wednesday morning, pls help update the agenda at https://wiki.hyperledger.org/groups/twgc/meeting/2018-07-04 before the meeting, welcome to join, thanks!
Has joined the channel.
请教个问题，composer指南上都是在本地安装业务网络，是否可以网络安装，有没有相关的资料可以参考，谢谢
网络安装具体是指什么？
我的意思是通过命令直接将本地bna文件安装到远程服务器
有没有比较活跃的QQ或者微信群，求加入
composer network install 命令需要传入一个card，而card里包含了connection profile，里面存放peer ca order等的地址和端口信息，与本地安装的差别就是这些配置的指向
是这个吗PeerAdmin@hlfv1， 我试试修改hlfv11/createPeerAdminCard.sh
你可以把脚本里面的connection profile考出来，修改后用composer card create 做一个新的card
Has joined the channel.
Has joined the channel.
请教个问题，怎样修改composer-rest-server，我想定制json返回结果和翻页，有谁做过吗
可以不使用rest server，用composer SDK自己实现API
Global forum link: https://events.linuxfoundation.org/events/hyperledger-global-forum-2018/program/cfp/?utm_source=event-promo&utm_medium=email&utm_campaign=gf18
[ ](https://chat.hyperledger.org/channel/twg-china?msg=pJQYkMa3YPzKKw3pz) 经过测试，couchdb里面的数据可以随意修改，然后通过SDK可以正常返回，block的hash正常，但是返回的数据是修改后的数据。这个时候，不同的peer的返回值是不同的。
@labcoinpoc 多谢
@davidhu 这有个例子供参考 https://developer.ibm.com/code/patterns/customer-loyalty-program-with-blockchain/
今天会议开始了吗？
Has joined the channel.
@KevinBai it's bi-weekly: https://wiki.hyperledger.org/groups/twgc. Will have it next week.
谢谢杨老师，刚才也是上网站看到的，现在正在补上次的会议记录
杨老师 实例化链码的时候报错了
Error: could not assemble transaction, err Proposal response was not successful, error code 500, msg failed to execute transaction e5a16afc0bb4c25fc67379da1cb300c60819ff6b36582511924b665f8b87e83a: error starting container: error starting container: Get https://registry-1.docker.io/v2/: dial tcp: lookup registry-1.docker.io on 127.0.1.1:53: read udp 127.0.0.1:52313->127.0.1.1:53: i/o timeout
!!!!!!!!!!!!!!! Chaincode instantiation on peer0.org2 on channel 'mychannel' failed !!!!!!!!!!!!!!!!
========= ERROR !!! FAILED to execute End-2-End Scenario ===========
ERROR !!!! Test failed
这个是什么原因呢？
我知道了，我的电脑没有网了。。。
Has joined the channel.
Has joined the channel.
Has joined the channel.
Has joined the channel.
Has joined the channel.
@here
Dear all, we will have the group meeting at 10AM this Wednesday morning, pls help update the agenda at https://wiki.hyperledger.org/groups/twgc/meeting/2018-07-18 before the meeting, welcome to join, thanks!
@baohua 杨老师, 我给 peer 和 orderer 上了 nginx 会不会影响到 gossip 协议的正常运行. 我现在新加入组织的节点同步区块, 都是从 orderer 获取的, 没有看到 p2p 同步的痕迹
@memphisw peer, orderer 用了 gRPC 协议。nginx如果做tcp转发应该问题不大，但注意配置内外地址映射关系。你说的p2p同步是？
Has joined the channel.
请教一个关于fabric1.2新特性：service discovery的问题，按照官方文档的说明，我将channel.initialize();改为channel.initialize({discover: true});后，一直报Channel:mychannel Discovery error:failed constructing descriptor for chaincodes:
hyperledger community is calling for architect: https://www.hyperledger.org/job/linux-foundation-apac-limited-hong-kong-144-community-architect-for-the-hyperledger-project-linux-foundation-apac-2
@memphisw 可以的 我们这面的环境就是通过nginx做tcp
然后gossip也没啥问题
@bluefire 谢谢
@baohua 我的状况是: 新的 peer 加入 channel, 这时候应该会有一个账本的同步环节. 但是我发现账本同步速度非常慢, 查看日志发现走的是 orderer 给 peer 发的落块的日志. 没有看到 peer 间互相同步的日志.
所以我怀疑是我的配置有问题, 我并没有给我的 channel 发送过更新 anchor 节点的 tx 消息. 是不是 gossip 协议的数据同步, 依赖于 channel 的 anchor peer 的配置呢?
因为我在阅读文档和示例的过程中发现, configtx.yaml 中对 Org 配置了 AnchorPeers 字段, 所以认为不需要在事后再重新发送一次配置 anchor peer 的 tx 了.
@memphisw 跟同步有关的是leader peer，谨慎猜测你配置了所有peer都是leader peer
反馈一下: 我们确实是没有设置 anchor 节点, 导致 gossip 的同步数据完全不工作. 哈哈哈.
[ ](https://chat.hyperledger.org/channel/twg-china?msg=KkW69CHjrbLvfhAmX) @memphisw 您好，anchor节点据我了解应该是影响的跨组织间的gossip，您这边实践中组织内的gossip也会影响到吗？
@tinywell 嗯我测试的是跨组织间的 gossip 同步, 后加入 channel 的组织的同步问题
Has joined the channel.
请教下，用composer network install的业务网络，用composer api 注册和更新asset，但重启机器后再启动fabric-dev，重新install start，之前的数据都没了是怎么回事
@davidhu 跟composer没关系，fabric的数据都是依附在容器里的，
@davidhu 跟composer没关系，fabric的数据都是依附在容器里的，删掉容器的话就没了，除非你做一些持久化设定，或者不要删除容器，使用docker-compose stop 而不是down 来停止容器
用的是fabricshutdown,容器没有删除吧，并没有teardown
如果不用容器部署是否可以避免这个问题，用代码部署组织节点，单独安装couchdb不用 docker
我查了以下，stopFabric脚本里确实用的是stop，tearDown里用的是down，按理来说只是stop然后再重启的话应该不需要重新install和start的，直接就是原样
不实用重启部署应该可以，但我觉得还是配置个volume做持久化简单一些
不使用容器部署应该可以，但我觉得还是配置个volume做持久化简单一些
https://hyperledger-fabric.readthedocs.io/en/release-1.2/build_network.html#a-note-on-data-persistence
哦，我发现问题了，不在stop脚本，而是start脚本里先调用了down
哦，我发现问题了，不在stop脚本，而是start脚本里先调用了down，启动前就都干掉了
startFabric.sh 也会干掉容器
没仔细看过
是的，可以把那里的down去掉试试看
嗯，也是个方法，多谢，我两个都试试
TSC election voting participant update: https://lists.hyperledger.org/g/twg-china/topic/tsc_election_voting/23799578?p=,,,20,0,0,0::recentpostdate%2Fsticky,,,20,2,0,23799578
Has joined the channel.
Has joined the channel.
@davidhu @labcoinpoc 我为peer/orderer/couchdb都做了数据持久化，但现在搞不清楚的是已经创建过的通道和加入通道/设置锚定peer节点这些操作，在再次启动的时候是否还需要调用一次？谢谢
我理解应该是不需要的，因为设置都保存在config block里，ledger被持久化的话这些设置都应该保存了
我用的是官方的docker，昨天@labcoinpoc 的两个方法都试过没有问题， 我是单节点，不需要重新设置
谢谢。我目前在两组织4节点中做数据持久化，如果对orderer节点的/var/hyperledger目录也做了volumes映射，启动时就问题。但是印象中peer节点加入通道这种过程是要通过orderer节点的，不知道orderer节点中保存相应数据是在什么地方？
刚发现orderer节点的/var/hyperledger/production/orderer/chains/mychannel下也有一个blockfile_000000文件，只比peer节点下的同名文件小1k多，插入数据的时候这个文件也在同步增长，估计要做数据持久化应该也要映射这个的上层目录。
有同样的疑问, 官方文档对持久化只指出了 peer 和 couchdb, 所以不确定是否要对 orderer 的 production 目录做数据持久化
Has joined the channel.
生产环境部署fabric是否也用容器？发现mount路径方式做持久化经常会出现调用transaction超时；生产环境用源码部署是否是推荐的
请教下，有谁部署过exproler没，我在client目录下run build的时候老是报这个错误'jsx-a11y/href-no-hash' was not found jsx-a11y/href-no-ha’
谁在fabric杭州社区微信群 麻烦拉我一下 我的微信号 ylj817
https://wiki.hyperledger.org/groups/twgc/
@here
Dear all, we will have the group meeting at 10AM this Wednesday morning, pls help update the agenda at https://wiki.hyperledger.org/groups/twgc/meeting/2018-08-01 before the meeting, welcome to join, thanks! （欢迎转发）
@davidhu IBM官方推荐用源码编译的方式来部署，不过建议在虚拟机里面做，便于复制。另外，能详细说一下mount路径方式做持久化经常会出现调用transaction超时问题吗？
@wangrangli 谢谢。我的开发环境是ubuntu，4核8G的虚拟机，用的是IBM 的docker开发环境。我现在的应用有两个transaction通过composer API调用，mount路径后就经常会出现调用超时，错误提示就是timeout，我是把peer和couchDB都设置了路径，个人认为是从docker写到host中间读写操作耗时
组里有人成功部署过explorer吗
@davidhu 谢谢。 explorer我部署成功过5月中的一个版本，我一个同事部署成功过最近的一个版本，都没有什么大问题
大家好，在configtx.yaml中有个配置属性，
BatchTimeout: 2s，注释是# Batch Timeout: The amount of time to wait before creating a batch.，请问这个是出块的等待时间，还是出块的超时时间？
Has joined the channel.
[ ](https://chat.hyperledger.org/channel/twg-china?msg=oLA4ZdSbvtPuJM6et) 经过验证，这个是等待时间，就是注释写的意思
能大概介绍一下吗
请问一下大家 有用fabric-sdk-go 调用 fabric-ca-release-1.2.0成功过的吗
@here 超级账本中国技术工作组 Governing Board 提名正式启动，欢迎大家积极参与：https://lists.hyperledger.org/g/twg-china/message/574
Has joined the channel.
大家好，请教一个问题。系统channel配置更新后，会同步自动更新应用channel的配置吗？
Has left the channel.
@wangrangli 请问你是按这上面说的部署的吗https://github.com/hyperledger/blockchain-explorer/tree/release-3.4
我在client/下运行npm test -- -u --coverage 就出错了
Clipboard - August 2, 2018 4_40 PM.png
node v8.11.3 npm5.6.0
这些不是报错信息吧，后面还有报错吗？
执行完这步就这些，接着继续执行 npm run build 报一堆的 jsx-a11y/href-no-hash' was not found jsx-a11y/href-no-ha’
Clipboard - August 2, 2018 5:05 PM
explorer频道里建议使用最新的master branch，你可以试试，我这里倒是没碰到这个问题。 话说 这个jsx-a11y/href-no-hash是airbnb的eslint规则相关的东西。。。竟然也影响build
试试重新安装一下eslint？
eslint 需要单独安装？步骤上没有提
应该在package.json 的devDependencies里
我看了一下现在master分支的package.json
```
"devDependencies": {
"babel-eslint": "^8.2.5",
"enzyme": "^3.3.0",
"enzyme-adapter-react-16": "^1.1.1",
"eslint": "^4.19.1",
"eslint-config-airbnb": "^17.0.0",
"eslint-plugin-import": "^2.13.0",
"eslint-plugin-jsx-a11y": "^6.1.0",
"eslint-plugin-react": "^7.10.0",
"jest-enzyme": "^4.2.0",
"mock-local-storage": "^1.0.5",
"react-addons-test-utils": "^15.6.2",
"react-test-renderer": "^16.2.0",
"redux-devtools": "^3.4.1",
"redux-mock-store": "^1.5.1",
"sinon": "^4.2.2"
},
```
会不会是你那缺了 eslint-plugin-jsx-a11y 或者没装上，试试npm install eslint-plugin-jsx-a11y --save-dev 或者重装下各种eslint和airbnb相关的包试试
"devDependencies": {
"eslint": "^4.19.1",
"eslint-config-airbnb": "^17.0.0",
"eslint-plugin-import": "^2.13.0",
"eslint-plugin-jsx-a11y": "^6.1.0",
"eslint-plugin-react": "^7.10.0"
嗯， 我试试-g安装
@davidhu 你的那个错误我们没有遇到过，不过安装就是按照那个网页上的指导来安装的，只是可以不运行 app/test 下面的两条npm命令可以不用执行
@wangrangli 不是app/test，是client,
cd client/
npm install
npm test -- -u --coverage
npm run build
@davidhu 应该就是eslint的问题，我找到几个issue比如 https://github.com/evcohen/eslint-plugin-jsx-a11y/issues/397 看起来需要调整版本或者禁用掉规则
@labcoinpoc 昨天卸载eslint相关的所有包，然后重新安装，还是报同样的错误
@labcoinpoc @wangrangli Explorer部署成功了, client下run build 给出的提示'jsx-a11y/href-no-hash' was not found jsx-a11y/href-no-ha'不用理会，只要最后提示ready to be deployed 实际上就编译通过了，然后启动fabric,再./start.sh 启动 explorer
分享下心得，如果./start.sh后浏览器没加载，就用node main.js启动方便查看错误
@davidhu :thumbsup:
Has joined the channel.
请问一下 谁有fabric-1.2.0的官方性能测试报告
同问，有1.1的性能报告吗？
目前tps都不高吧？
高不高倒不重要 我是想要个参考值
不知道谁做过这方面的测试 希望可以拿出来共享一下
请教下，目前有把钱包应用和超级账本结合起来的吗
请问，fabric是不是准备推出token机制，是否有相关文档可以参考？
尝试过caliper，但一直没有配置成功
@zerppen 你可以参考下这篇论文：http://arxiv.org/abs/1805.11390
caliper 我测试过1.1，6台8c32g ssd的机器，测试最好到1100
@grapebaba 请问你是怎么测的，调go api还是composer api，多少个接口同时测
这个跟部署方案也有关系吧
用caliper
调的nodejs
Has joined the channel.
还跟智能合约相关呢
好的 多谢 @baohua
针对 杨博士给的论文 我做了一些实际的验证 在配置项上得出的测试结果跟论文里面基本一致 除了一个 endorse policy方面
论文中这种背书策略效率最高 OR [AND(a ,b, c), AND(a, b, d), AND(b, c, d),
AND(a, c, d)]
暂时验证不了
应该说验证失败
性能的话，各个环节调好有，事务不大，一两千。
明天深圳这里有线下活动？ 朋友跟我讲才晓得，还是hyperledger中国组的名头，但是邮件组没看到
请问@各位，西安有交流群吗，以及西安的meetup有消息吗？
那种 一条合约 触发上千资产 上千用户数据更新的 常规系统里的批量过程 搞不好只算一笔原子交易
官方微信跟这里没强相关？
有点后悔来线下这个活动了 🤷♀️
Has joined the channel.
why
我倒想找人交流，可惜湖南没有组织
因为有直播呀，躺家里就能看。
看文档是一样的，参与其中没有地域限制呀。
Has joined the channel.
请教个问题，有没有多物理机搭建多节点环境的指南
默认的指南就允许多机呀，只是你docker需要与另一台物理机的docker通讯，nat和域名什么的需要注意，容器不一定继承了宿主的hosts文件。
多台orderer麻烦一点 但是官方文档 或者 yeasy的文档 按说会提到，手把手的教程时效性有限，还是要点基础
你说的是纯物理机吧 不用docker来搭建吗？不太明白 @davidhu
以前是vagrant的 后来似乎太麻烦 没给这个选项了。
Has joined the channel.
Hi there, did someone get the similar error: Sending proposal to peer0 failed because of: gRPC failure=Status{code=UNIMPLEMENTED, description=unknown service protos.Endorser, cause=null}
https://github.com/cloudhuang/fabric-vagrant-env vagrant的环境，v1.1可以直接通过vagrant up启动，（需要basebox,太大了，没有传上去）
[ ](https://chat.hyperledger.org/channel/twg-china?msg=AAukw9sN6kMP8RWr3) 我同事绑定了一个错误的端口号:sweat_smile:
Has joined the channel.
请教个问题, 请问有在链码里获取区块高度之类 channel 信息的api吗?
@larry618 有的 这是所有区块链的基本功能
请问 peer 如何移除 join 过的 channel. 我指的是 channel 参与者方面的退出 channel, 而不是 channel 拥有者对访问权限的收回.
@here It was reported that some ballots haven't arrived on time.
If your name is in any sheet of https://docs.google.com/spreadsheets/d/1-R43fMOia9P1JsFiSWe3wxkOmkzK_EM7HT2kmYNEn0M/edit#gid=31088272, you should have received the ballot.
Otherwise, please ask Todd (tbenzies@linuxfoundation.org) to retrieve.
Thanks!
@here It was reported that some TSC election ballots haven't arrived on time.
If your name is in any sheet of https://docs.google.com/spreadsheets/d/1-R43fMOia9P1JsFiSWe3wxkOmkzK_EM7HT2kmYNEn0M/edit#gid=31088272, you should have received the ballot.
Otherwise, please ask Todd (tbenzies@linuxfoundation.org) to retrieve.
Thanks!
[ ](https://chat.hyperledger.org/channel/twg-china?msg=ZcJxRyoza3HLNjHd8) @memphisw 好问题 那在channel之上的chain code以及账本怎么办？
[ ](https://chat.hyperledger.org/channel/twg-china?msg=e62fe1ce-fe65-4fda-8891-038e73b628a9) @davidkhala 我的应用场景是, 有一方的 channel 提供了一个信息共享的服务. 被允许加入的组织可以进来任意翻阅, 但是这个加入的组织一旦进入, 就没有办法退出, 平白增加了许多负担
看起来这个方案是不是用事件监听机制更好？
@memphisw 是加入组织还是节点加入channel？如果是前者的话我们可以通过修改通道配置删除整个组织的定义啊
Has joined the channel.
不是加入组织, 就是 peer 节点加入 channel, 然后 peer 节点觉得数据没啥用, 想退出 channel
@davidkhala 不是加入组织, 就是 peer 节点加入 channel, 然后 peer 节点觉得数据没啥用, 想退出 channel
这算是一个基础的功能吧~ 感觉是 missing part
@memphisw 在bft里面确实可以这样动态增删节点
但是现在的fabric, it does not make a lot of sense
怎么会 make no sense 呢, 终止合作的情况下, 权限会被收回. 那么这个 peer 将不断提示自己被该 channel 拒了. 产生垃圾信息, 这时候退出这个 channel, 不再请求消息是很自然的
@zerppen 怎么会 make no sense 呢, 终止合作的情况下, 权限会被收回. 那么这个 peer 将不断提示自己被该 channel 拒了. 产生垃圾信息, 这时候退出这个 channel, 不再请求消息是很自然的
你要想退出 你shut down你的node不就完了
[ ](https://chat.hyperledger.org/channel/twg-china?msg=uaQcfaP3MorfWsDKQ) @zerppen 我的 peer 还 join 着其他 channel 呢, 不能说 shut down 就 shut down
大家好，请教一个问题。我做了个3个orderer的集群，zk，kafka，orderer都正常，但启动cli创建channel的时候就报错，总是说channel已经被创建过了。但跳过这一步直接让peer加入channel无法执行成功。查找网上有所把docker的镜像删除掉就好，可是我的虚拟机上删除不了orderer的镜像，怎么搞？
删除容器, 重建 orderer 应该就可以了
大家好 请教个问题 有人知道 Java sdk 怎么用 idemix吗？
或者 go SDK 里有例子吗？
@memphisw 请问，如果做了orderer集群的话，创建通道时需要给每个orderer节点都调用一次peer channel create命令吗？谢谢
Has joined the channel.
@here Dear all, Hyperledger is looking at APAC Hackfest at the beginning of 2019, please help vote for your preferred time slot at: https://doodle.com/poll/fibt39eh2sbfirey. Thanks!
请问一下 罗国辉 在这吗
[ ](https://chat.hyperledger.org/channel/twg-china?msg=WkTb7BSLGxWcGhjLn) @wangrangli 不需要, 创建一次就行
请问有关于fabric 1.2 的 private data 相关的资料方便发一下吗？
fabric-1.2.0 有遇到过这个问题没的没
https://jira.hyperledger.org/browse/FAB-10540
一开始挺好的 运行几个星期以后 出现了这个问题
下面comments不是说fix了么
@OzWang No,after 3 weeks test,it appears
And i open the bug again
u should read the latest bug description
Clipboard - August 23, 2018 9:46 PM
@memphisw 谢谢。再问一个问题，我在使用composer发布一个3组织的链码的时候，第一个安装成功了，但再后来的两个都失败，错误信息如下.这可能是什么方面的问题，请给些建议。
我经常发布2个组织的链码，2个组织的所有节点都在同一台电脑上运行。但这一次，这3个组织的6个节点是分布在6台服务器上的，并且启用了zookeeper和kafka节点。
谢谢
没用过 composer 不太清楚, sry
@memphisw 谢谢
Has joined the channel.
[ ](https://chat.hyperledger.org/channel/twg-china?msg=qwZv3PheZ3wWzkLgQ) @wangrangli 你这个是证书错误了，可有检查下CORE_PEER_ID CORE_PEER_ADDRESS CORE_PEER_LOCALMSPID CORE_PEER_MSPCONFIGPATH这几个系统变量，每个peer的证书需要和自己的证书一致
Has joined the channel.
Clipboard - 2018年8月30日下午4点22分
@baohua
杨老师，这里区块链的高度不是我们通常所说的区块告诉吧，我们通常所说的区块高度就是blockNumber吧
Clipboard - 2018年8月30日下午4点28分
对，一般说高度是区块，这里还包括了交易序号
杨老师，研究fabric的源码有什么好的方式吗？怎么能单步跟踪调试源码？谢谢！ [ ](https://chat.hyperledger.org/channel/twg-china?msg=YLLDKs7TPWqWn9DbM)
@baohua 杨老师，研究fabric的源码有什么好的方式吗？怎么能单步跟踪调试源码？
@baohua 杨老师，你能拉我进北京的区块链学习群嘛？
[ ](https://chat.hyperledger.org/channel/twg-china?msg=cg4XX3Pp2WU79itqCQ) @kevinli 看这里的wechat group：https://wiki.hyperledger.org/groups/twgc
[ ](https://chat.hyperledger.org/channel/twg-china?msg=Sfcqf3w3tIbbmBEa8N) @kevinli 嗯，阅读、实现，实验
Has joined the channel.
Has joined the channel.
有人调试Fabric源码遇到这个问题吗？could not launch process: decoding dwarf section info at offset 0x0: too short
使用go 1.10和1.11都有这个问题，IDE是goland
@BenZhang 你的调试环境是什么？哪个平台？
@BenZhang 我在Windows平台遇到过你说的这个问题
@kevinli 在mac上，最后你是怎么解决的呢？我网上查了下好像是golang的问题
使用brew自动安装的
@huangliping 谢谢
Clipboard - 2018年9月4日上午11点15分
有人用过caliper没，用管方的例子跑了下fabric1.1的，这个报告该如何解读？
@BenZhang 我没解决啊，也在找方法
@kevinli :joy:
请教一下大家 调用go sdk里 Client.Execute的时候内部给peer节点发背书请求的时候会自动根据当前的背书策略选择吗
@OzWang 并不会，会根据connection profile所属organization的peer list做round robin balance
@OzWang 默认会根据connection profile所属organization的peer list做round robin balance
或者你指定发送到哪些peer
[ ](https://chat.hyperledger.org/channel/twg-china?msg=kvY5WnP5n43AicDpR) @demonkm which config are you using and what config is your server? Using one single server, the CPU is usually the bottleneck, as there're 5 clients by default, and lots of container processes.
[ ](https://chat.hyperledger.org/channel/twg-china?msg=pwxpLRTdv57Jaiph6) @baohua 我是执行的node benchmark/simple/main.js -c config.json -n fabric.json，是单个服务器
Clipboard - 2018年9月5日下午2点18分
[ ](https://chat.hyperledger.org/channel/twg-china?msg=pwxpLRTdv57Jaiph6) @baohua 看cpu使用率不是很高，为什么这里的tps才120几呢
[ ](https://chat.hyperledger.org/channel/twg-china?msg=Ejj53zcjEzZCsPRc4) @demonkm How many core do you have? Seems the sum number is several hundreds already.
[ ](https://chat.hyperledger.org/channel/twg-china?msg=jN5NWMXb7SfGBuimg) @baohua 4核的
[ ](https://chat.hyperledger.org/channel/twg-china?msg=S5mBfELMNaCh3Brgc) @demonkm It's not enough, besides, you need to enable multiple clients maybe.
这个测试不太对吧 我上个月测试tps到了400+
这个测试不太对吧 我上个月测试tps到了400+
4核8G
8核16G
[ ](https://chat.hyperledger.org/channel/twg-china?msg=PEDHDEAAxrrCGEbKP) @zerppen 你也是用caliper跑的吗？
Has joined the channel.
@BenZhang 查过了,据说要等golang1.12才会解决, 现在都没办法debug.
有人说降级到0.94可以,我试了问题依旧.
Clipboard - September 10, 2018 11:35 PM
8核CPU我之前用caliper试的稳定在200+
[ ](https://chat.hyperledger.org/channel/twg-china?msg=kvY5WnP5n43AicDpR) @demonkm 这个sendRate设置太低咯， 可以试试200，400 ,600递增
你是官方的自带的例子试的，还是连接到自己部署的fabric网络试的哈？ @davidkhala [ ](https://chat.hyperledger.org/channel/twg-china?msg=QtZq9XhcsW4H3cPGQ)
@Pillar 嗯嗯，估计要1.12了，看GitHub这个问题是解决了https://github.com/golang/go/issues/23733，本来想自己编译一个，看了下好像挺麻烦，就放弃了。你现在是怎么调试呢？
[ ](https://chat.hyperledger.org/channel/twg-china?msg=9Zq3ojrzvWZSzcByzh) @demonkm caliper默认的网络方案，我只是改了一下测试参数
https://wiki.hyperledger.org/groups/twgc/meeting/2018-09-12
开会了
@BenZhang 放弃了.:disappointed::grimacing:
没有安装chaincode的peer，也会同步channel里面所有chaincode的账本数据么？
@davidkhala 如果这个节点加入这个channel了， 就能否接收到账本。
@davidkhala 如果这个节点加入这个channel了， 就可以接收到账本。
是否安装chaincode， 决定 是否 接受 client 请求。
是否安装chaincode， 决定 是否 接受 client proposal 请求。
go 1.9.2 可以支持debug. 如果 fabric 依靠 新的 go api， 可以从 go 1.11 把相应的 source code 复制到 go 1.9.2.
@guoger fabri-proxy 有开源吗？
Screen Shot 2018-09-13 at 10.55.39 PM.png
@ping40 很怪, 我今天试又好了,golang版本1.10
@Pillar go 1.10, 跑 logging_test.go debug可以， 但是 我测试了 common/ledger/util/ioutil_test.go, common/ledger/blkstorage/fsblkstorage/block_serialization_test..go 等几个都不行。
有些测试是可以，但是大部分都不行
@ping40 ioutil_test.go我试了下.可以啊.
Screen Shot 2018-09-13 at 10.55.39 PM.png
Screen Shot 2018-09-14 at 4.38.47 PM.png
fabric: release-1.0 golang:1.10, 可能跟fabric的版本有关
@Pillar 我用的master fabric。 没法解释阿
Has joined the channel.
请教大家一个关于fabric sdk中event注册的问题。block event 和tx 的event 是什么时候产生的啊
@here Congrats David Liu to become active member of TWGC! We welcome more people to apply and to contribute more in the community!
@davidkhala congrats!
and please add your rocket.chat ID to our wiki page: https://wiki.hyperledger.org/groups/twgc
and please add your rocket.chat ID to our wiki page: https://wiki.hyperledger.org/groups/twgc
[ ](https://chat.hyperledger.org/channel/twg-china?msg=2XjDPukNEkmKhgmR5) @OzWang 都是在监听到新区块的时候产生的，时机应该是同一个
Has joined the channel.
Has joined the channel.
Has joined the channel.
Has joined the channel.
请问下 couchdb支持中文查询吗？
@yljgo 可以的
我试了下 查不出来。。
代码看看 ？
test unit 是可以的
可以了 可能是数据没落盘
@labcoinpoc 请教下，录入participant是否就得issue card
[ ](https://chat.hyperledger.org/channel/twg-china?msg=rC9TMQuEcrYZMYCqk) @davidhu 不是，只有需要使用这个participant的身份操作的时候才需要使用card
具体的操作是指那些，比如单个用户通过客户端发起一次交易？
btw: composer说不再更新feature了，我正想着改用sdk。。。
现在不是还在更新吗，才看到composercontrbutors里说发布20.1release
关键是用户使用哪个身份发起交易，如果要使用participant就需要在BusinessNetworkConnection.connect(card)里传入对应的card
https://lists.hyperledger.org/g/composer/topic/25106848#125 说是不支持1.1以后的新feature了，只作重大bug修复和新版HF的兼容。
好消息是从1.3
好消息是从1.3开始SDK里会加入类似composer的使用方式，简化操作
composer项目要流产了？
乐观的看法是composer被整合进SDK了，反正估计是得转用SDK
那也应该是转到node SDK吧
一般的操作什么的还好，我现在比较头疼的是access control，这块用SDK不知道怎么实现好，是直接在chaincode里写判断还是用policy
node SDK据说是会在1.3加入composer的操作方式 Modeling language，其它的（go，java）会在1.4加入
现在看应该是Node SDK最合适
access control 已经习惯了，policy还要花时间，还在看你发的链接，sstone分析的也没错
我现在的测试项目里感觉composer 的access control还是有点性能影响，顺序check挺费时间的，现在我这用composer的测试tps一直上不去，
另一个纠结的地方是如果SDK改成composer的操作方式，API恐怕也会有大变化，那现在开发的app到时候是不是又要重新写。。。
@here Dear all, we will have the group meeting at 10AM this Wednesday morning, pls help update the agenda at https://wiki.hyperledger.org/groups/twgc/meeting/2018-10-10 before the meeting. Welcome to attend, thanks!
Has joined the channel.
Has joined the channel.
想问下有没有人通过fabric-ca做过一个用户管理系统？谢谢！
一个peer上能不能有中心化的系统集群呢？
什么样的用户管理系统？ PKI吗
有人用过explorer3.8吗
@davidhu 是，就是fabric-ca 不是可以注册新的identity嘛？我可以当作是传统的用户注册系统嘛？（然后一个问题就是certificate该怎么保存呢？
没做过，原来看过点文档，可以用数据库，和LDAPhttps://hyperledger-fabric-ca.readthedocs.io/en/latest/users-guide.html#registering-a-new-identity
[ ](https://chat.hyperledger.org/channel/twg-china?msg=DsRR2rCbtyo6SaR7p) @davidhu 3.8貌似还没release？ 我还停在1.1，用过3.5
[ ](https://chat.hyperledger.org/channel/twg-china?msg=C5gG5Ad9A6jLAiE3c) @dexhunter 我认为不行，CA只是签发证书的， enroll密码也只是一次性密码，还是要换取证书。node sdk有keyValueStore https://fabric-sdk-node.github.io/module-api.KeyValueStore.html 保存用户证书，在它上面可以建用户注册系统，也就是说app的服务端持有证书库，用户通过注册认证系统后可以调用对应的证书。
@labcoinpoc 好的，謝謝
@davidhu Composer 的modelling language 被分离成单独模块了，应该是要整合进Node SDK https://github.com/hyperledger/composer-concerto
去 #composer-contributors 看了一下，只说是可以配合HF使用
@labcoinpoc 之前在贡献组就看他们在讨论concerto，说是比现在的建模语言有更多扩展，支持tx返回值，不知道正式立项没
Has joined the channel.
Has joined the channel.
[ ](https://chat.hyperledger.org/channel/twg-china?msg=taFFfbhFtdqb7d36v) @labcoinpoc nodesdk 1.3 里面添加了一个大目录叫做fabric-wallet，听说就是composer的人贡献回来了的
[ ](https://chat.hyperledger.org/channel/twg-china?msg=LKYfAtNh3ypmyrrgf) @davidkhala wallet应该是和Composer的CardStore一样，Composer里把用户的connection profile、identity
[ ](https://chat.hyperledger.org/channel/twg-china?msg=LKYfAtNh3ypmyrrgf) @davidkhala wallet就是Composer的CardStore，Composer里把用户的connection profile、identity和证书合并做成了一个Card，然后只要使用card就能连接fabric和操作。 concerto是composer 的modelling部分，如果整合fabric的话应该会在chaincode相关的地方
@labcoinpoc 我们可以将concerto理解成某种chaincode 的模板么？
[ ](https://chat.hyperledger.org/channel/twg-china?msg=q52hJL2Zy8bSrCd78) @davidkhala composer的business network definition包含modelling 的.cto文件 logic的.js文件，access control的.acl还有query的.qry 四种文件，composer的runtime作为chaincode安装进fabric，
[ ](https://chat.hyperledger.org/channel/twg-china?msg=q52hJL2Zy8bSrCd78) @davidkhala composer的business network definition （bna）包含modelling 的.cto文件 logic的.js文件，access control的.acl还有query的.qry 四种文件，composer的runtime作为chaincode安装进fabric，然后给bna提供运行环境。 concerto只是其中的cto文件，我想没可能会把composer runtime合并到Node SDK中，目前只是数据建模这部分独立出来了
这篇资料可能有帮助 https://docs.google.com/document/d/1_np3fnT_OludRGcF3PbubDooNsH8J-_G7UaWhk8a_cU/edit#
@labcoinpoc 感谢分享
大家好， 问个问题官方的e2e_cli例子， invoke后账户查询金额没有变化？是因为交易还没有打包到block上吗？
Chaincode invoke successful. result: status:200 返回都是成功的
現在有哪些基於fabric的成熟的開源應用了嗎？（求repo地址分享）謝謝！
请教一下 合约字段必须为非空吗？
@dexhunter 应用应该都是联盟私有的，不过开源的工具集有不少
您好，想请问一下，在0.6版本中PBFT中主节点是安装顺序分配的序号吗？
@davidkhala
您好，想请问一下，在0.6版本中PBFT中主节点是按照顺序分配的序号吗？
0.6没接触过，帮不上忙
28号北京 见面会 http://www.huodongxing.com/event/3462448095411
27号 广州 见面会 http://www.huodongxing.com/event/2462156324811
欢迎大家报名、欢迎大家推广转发
:grinning:
好的感谢
还有有谁知道，PBFT在fabric中要实现的是什么吗？为什么需要PBFT？
想请教一个问题，锚节点可以在不同的channel之间通信吗？
@here Dear all, we will have the group meeting at 10AM this Wednesday morning, pls help update the agenda at https://wiki.hyperledger.org/groups/twgc/meeting/2018-10-24 before the meeting. Welcome to attend, thanks!
Has joined the channel.
Hi guys, is there any ways I can reach out a Hyperledger Fabric contributor / experienced developer in Hong Kong?
[ ](https://chat.hyperledger.org/channel/twg-china?msg=HRarbTThRw8dD8Efw) @richzhao 這些見面會的語言是中文或是英文的？
中文为主
[ ](https://chat.hyperledger.org/channel/twg-china?msg=KLGXPC3DLqyxbhphz) @baohua 謝謝
Has joined the channel.
请教一个问题，怎么样在couchdb里面创建一个可以用来做排序(sort)的索引，我几乎用了网上说的所有创建索引的json格式，也创建过view，可是在couchdb里面带sort查询的话，还是报错Error running query. Reason: (no_usable_index) No index exists for this sort, try indexing by the sort fields.
请问下，fabric1.1.0 使用node-sdk的时候偶尔会出现channel eventhub has been shutdown ,请问这个问题有什么解决方案吗？eventhub是必须的嘛？
Has joined the channel.
hi @baohua ,请问我们有中文翻译小组吗？我之前翻译了一些 Hyperledger Indy 的文档，希望能够有些用途
我也在开始学习了解 Fabric，也希望能够翻译 Fabric 的文档
有的，文档翻译可以联系 郭立冬
[ ](https://chat.hyperledger.org/channel/twg-china?msg=E9M6mAAcmF4KNCZPn) @wangrangli 比如在nodesdk当中专门有个参数叫做metaDataPath来在安装chaincode的时候制定couchdb索引文件的位置：https://fabric-sdk-node.github.io/tutorial-metadata-chaincode.html
[ ](https://chat.hyperledger.org/channel/twg-china?msg=E9M6mAAcmF4KNCZPn) @wangrangli 比如在nodesdk当中专门有个参数叫做metaDataPath来在安装chaincode的时候制定couchdb索引文件的位置：https://fabric-sdk-node.github.io/tutorial-metadata-chaincode.html
[ ](https://chat.hyperledger.org/channel/twg-china?msg=tyyR8stvujjzoQzFi) @iamsteveng Hi Steve, I am david liu. It is just a greeting from rocket chat LOL.
给大家介绍一下steve Ng, 他是香港的普华永道会计事务所New Venture的资深团队主管
给大家介绍一下steve Ng @iamsteveng , 他是香港的普华永道会计事务所New Venture的资深团队主管
hi @guolidong , 有没有文档翻译的 guideline
[ ](https://chat.hyperledger.org/channel/twg-china?msg=K87KsDPfeSBhDjZD6) @lijiachuan lidong会联系你哈，欢迎参与文档工作！
[ ](https://chat.hyperledger.org/channel/twg-china?msg=GnZj6F5Ws4wDE3HM7) @lijiachuan hi, Hyperledger文档的中文化工作是我们社区一直在做的事情，
目前已经做的事情有：
1、最早的，Fabric 1.0.0版本doc翻译成中文，当时记录在wiki.hyperledger.org上，后来通过readthedocs关联GitHub仓库，形成了更易读，更易于协作翻译的一套办法，
Fabric 1.0 doc 中文版 GitHub仓库地址：https://github.com/HyperledgerCN/hyperledgerDocs
Fabric 1.0 doc 中文版 readthedocs地址：https://hyperledgercn.github.io/hyperledgerDocs/
2、后来，Fabric 1.1.0版本doc翻译成中文，就是直接使用GitHub+readthedocs的办法
Fabric 1.1.0 doc 中文版 GitHub仓库地址：https://github.com/HyperledgerCN/fabric-docs-i18n
Fabric 1.1.0 doc 中文版 readthedocs地址：https://fabric-docs-i18n.readthedocs.io/zh/fabric-1.1.0_zh-cn/
3、现在，Fabric 1.2.0版本doc翻译成中文，正在进行中，由于项目得到了社区管理者的支持，主要是境外Linux foundation的支持，使得翻译项目可以成为HyperLedger 实验室项目，然后变更了GitHub地址：https://github.com/hyperledger-labs
Fabric 1.2.0 doc 中文版 GitHub仓库地址：https://github.com/hyperledger-labs/fabric-docs-cn
Fabric 1.2.0 doc 中文版 readthedocs地址：https://hyperledger-fabric-cn.readthedocs.io/zh/latest/
4、Fabric 1.3.0版本doc翻译成中文，GitHub地址和readthedocs地址都不需要变更了。GitHub上新建了分支，readthedocs上可以直接同步
5、将来，像HyperLedger Indy 等其他文档翻译的事情也可以用GitHub+readthedocs的方式管理，但是目前Hyperledger-labs没有Indy的专有项目，可以使用其他GitHub organization账号管理。非常欢迎你能参与到这个工作中来，由于参与翻译的人员大部分是全职工作的人员，所以Fabric 1.0、1.1、1.2等三个版本都没有翻译完毕。
wiki上的介绍有：https://wiki.hyperledger.org/groups/twgc/team_ie
还有翻译贡献的指南：https://wiki.hyperledger.org/groups/twgc/team_ie/guideline
Dear all, we will have the group meeting at 10AM this Wednesday morning, pls help update the agenda at https://wiki.hyperledger.org/groups/twgc/meeting/2018-11-07 before the meeting. Welcome to attend punctually, thanks! @all
今天例会再次强调的 FAQ: https://wiki.hyperledger.org/groups/twgc/faq，欢迎大家补充完善。
:thumbsup:
fabric国密化算法补丁，可以用在fabric release版本中，支持1.1.x / 1.2.x /1.3.x
补丁地址：
https://github.com/flyinox/fabric-sm-patch
在拉取的fabric release版本源码中打上补丁，并且make编译即可以使用
配套有国密化定制的msp生成工具 cryptogensm
欢迎大家的试用和建议反馈
Has joined the channel.
Has joined the channel.
请问fabric1.1.0做数据检索的时候，那个limit = 10000可以修改吗？有没有变通之法？或者有没有什么办法来优化查询
@baohua 杨老师，您好，打扰了。我一直在听你们每次会议的录音，但是目前只更新到10/24日的，后面的还没有更新。请问后面的还会有吗？
@lcj 现在是发会议记录minutes。自动录音社区给关了，我看看有没有其他好办法。
@all Dear all, we will have the group meeting at 10AM this Wednesday morning, pls help update the agenda at https://wiki.hyperledger.org/groups/twgc/meeting/2018-11-21 before the meeting. Welcome to attend, thanks!
@baohua OK，谢谢，知道了。期待你们的录音，跟上社区的步伐。
Hi, 群里有人知道如何使用gdb或dlv来调试fabric 1.2.1的源码吗？先谢谢了，我使用dlv 1.1.0 和 golang 1.11.2在调试fabric的时候，遇到了一个问题，详见(https://manios.org/2018/10/05/metricbeat-debug-frame-section-error), 文章里的解决是将golang降级到1.9.7, 但是我又注意到编译fabric1.2.1需要go1.10.x以上的版本。那这个问题该怎么解决呢？或者是还有其他的方法？先谢谢了。
Has joined the channel.
@marryton007 用 golang 1.9.7的， 同时从 go 1.11 版本 把 x509（以目录级别） 复制到 1.9.7 对应的目录。
@ping40 let me try, thanks.
Clipboard - November 21, 2018 10:15 AM
@ping40 我的go-1.11.2版里有src/pkg，这些目录都拷贝并覆盖1.9.7里的目录吗？
我把src/pkg都覆盖过去了，还是无法编译peer
仅仅 拷贝 最小目录。
仅仅 拷贝 最小目录。 应该 是 src 目录下...
仅仅 拷贝 最小目录。 应该 是 src 目录下... 不是 pkg
我的环境是：go 1.9.2 和 go 1.10.2.
我2种都试过了
我再试试1.10.2吧
试过将1.10.2 src/crypto/x509 覆盖到1.9.7下，编译还是失败
:cry:
Has joined the channel.
@ping40 试过了，使用go源码编译最新的Master分支，可以解决这个问题。使用最新版本编译peer, dlv, 并将这2个工具拷贝到docker容器里，可以实现vscode/goland的远程调试。
@marryton007 谢谢，多了一条路
Has joined the channel.
Has joined the channel.
test msg.
@baohua 您好，我是《区块链原理、设计与应用》的新读者，以后会多多向您请教。
fabric在instantiate chaincode时，是如何将chaincode build成一个image，然后把这个image放到docker container中运行的呢？这一块的源码找了好久也也理出个头绪。
Has joined the channel.
[ ](https://chat.hyperledger.org/channel/twg-china?msg=FhF2xijR667iwSYjS) @leon.one 欢迎多交流，第一版的勘误表在 https://github.com/yeasy/blockchain_guide/wiki/%E3%80%8A%E5%8C%BA%E5%9D%97%E9%93%BE%E5%8E%9F%E7%90%86%E3%80%81%E8%AE%BE%E8%AE%A1%E4%B8%8E%E5%BA%94%E7%94%A8%E3%80%8B%E5%8B%98%E8%AF%AF%E8%A1%A8
Has joined the channel.
Has joined the channel.
fabric网络完全启动后，不停止网络的情况下，还能够像增加其他组织那样，完成排序服务的切换吗？比如卡夫卡切换为solo.望指教，谢谢:blush:。
[ ](https://chat.hyperledger.org/channel/twg-china?msg=vrN9FzMGbAJPiEwji) @wangkaixuan Not supported today.
Has joined the channel.
Does anyone know how to use the crls (certificate revocation lists) in fabric, how to config the channel msp with the crls?
@all Dear all, we will have the group meeting at 10AM this Wednesday morning, feel free to update the agenda at https://wiki.hyperledger.org/groups/twgc/meeting/2018-12-05 before the meeting. Welcome to attend, thanks!
Has joined the channel.
我在学习hyperledger composr的教程，在Developer tutorial for creating a Hyperledger Composer solution教程中，最后一个步骤Step Six: Generating a skeleton Angular application中，应用成功生成后，到应用目录下执行 npm start 报错如下，望指教原因，谢谢。
Clipboard - December 5, 2018 2:28 PM
Has joined the channel.
我们公司想开放一个联盟链平台，帮助企业快速上链，现在应该用hyperledger fabric哪个版本
做为底层好一些
[ ](https://chat.hyperledger.org/channel/twg-china?msg=E5fHkaNawRjbJypx4) @cn-ygf Fabric v1.4.0 will come out this month, and it is expected to be LTS.
:smiley:
Clipboard - 2018年12月6日下午1点51分
这个是什么原因
Clipboard - 2018年12月6日下午1点51分
Has joined the channel.
[ ](https://chat.hyperledger.org/channel/twg-china?msg=9dBbo2XCfXNAxchNk) @wangkaixuan 好像前一阵有人说composer的yoman脚本有点问题，生成的网站有bug，不知道是不是你这个。其实只要起动rest server然后直接测API就好了，自带的那个Angular模版十分简陋，随便用喜欢的前端开发然后调API比较好
@labcoinpoc 好的，谢谢。:blush:
:joy:我再试试1.1
:joy:
Clipboard - December 6, 2018 4:16 PM
我在尝试官网的code patterns，这个demo叫做--通过 Hyperledger Composer 实现去中心化能源，但是执行composer network start 命令一直报错，调试了一天了，哎，多多赐教。
Clipboard - December 6, 2018 4:21 PM
:upside_down: 终于调通了两个peer
Has joined the channel.
请问下，目前fabric的tps能达到多少？（使用node-sdk的情况下）
[ ](https://chat.hyperledger.org/channel/twg-china?msg=HbL4p8tjKPiWBgZta) @Randyshu2018 The number will depend on the configurations, however, there's some paper you may have a look at: http://arxiv.org/abs/1805.11390
Has joined the channel.
Has joined the channel.
@wangkaixuan composer network start 每次会调用gyp来编译grpc，需要翻墙。或者升级到最新版本，看看是否已经解决了这个问题。
《区块链原理设计与应用》134页勘误.png
[ ](https://chat.hyperledger.org/channel/twg-china?msg=KamMZefutWYqgK5hd) 最后一个地址少了个字母l
[ ](https://chat.hyperledger.org/channel/twg-china?msg=hNayQjspywRbKyqaf) @AlanYang can u help update at https://github.com/yeasy/blockchain_guide/wiki/%E3%80%8A%E5%8C%BA%E5%9D%97%E9%93%BE%E5%8E%9F%E7%90%86%E3%80%81%E8%AE%BE%E8%AE%A1%E4%B8%8E%E5%BA%94%E7%94%A8%E3%80%8B%E5%8B%98%E8%AF%AF%E8%A1%A8? Thanks!
@all Dear all, the meeting at 2019-01-02 will be cancelled due to the vacations. Happy new year to every one!
请教一个问题，Fabric 的链码对于调用者是完全可见的吗？就是说每个链码的调用者都能看到链码的逻辑吗？:blush:
[ ](https://chat.hyperledger.org/channel/twg-china?msg=dFkE5kcwwCmxGzhmP) @wangkaixuan 调用者属于客户端，一般情况看不到服务端的链码逻辑。如果客户端权限足够且peer开启了生命周期链码，可以通过lscc的api获取链码数据
Has joined the channel.
Has joined the channel.
Has joined the channel.
我尝试用fabric-java-sdk创建通道，遇到了这个错误：org.hyperledger.fabric.sdk.exception.TransactionException: New channel mychannel error. StatusValue 400. Status BAD_REQUEST，谢谢
[ ](https://chat.hyperledger.org/channel/twg-china?msg=mGppdLRiTTwsD68dA) @baohua My pleasure！But I found that it already exists in the table . My fault ，sorry sir.
请问区块链文件中的读写集是以明文存储吗？
@baohua 我将一些这里的一些问题整理到TWGC 的QA上了，哈哈
[ ](https://chat.hyperledger.org/channel/twg-china?msg=iYpGXFzPgmz3SsMCJ) @davidkhala :thumbsup:
大家好，请教大家一个问题，peer channel signconfigtx 可以获取peer的签名，那我想获取orderer的签名该用什么办法呢。
大家好，请问fabric分页怎么使用的？按照文档https://hyperledger-fabric.readthedocs.io/en/release-1.4/couchdb_tutorial.html#cdb-pagination，好像没法获取总记录数，以及确定是否还有下一页.
大家好，我在利用fabric-java-sdk时，自己定义的配置文件，但是报错：Filed to load any configuration from: config.properties. Using toolkit defaults
Has joined the channel.
Has joined the channel.
@baohua 勘误表怎么提交，直接edit-save嘛？
先进
yes!
参考现在表格格式
好的
你看的是github上的版本吗，也欢迎直接修改提交fix：https://github.com/yeasy/blockchain_guide
我看的pdf版本的
恩，我过会提交fix
Has joined the channel.
咨询一个创建channel的问题：是不是只有配置在configtx.yaml文件并将信息写入了genesis.block的组织可以创建channel？有没有什么方法可以让一个新组织加入网络，然后去创建自己的channel？
[ ](https://chat.hyperledger.org/channel/twg-china?msg=TDEy5FGELnyoJJTgp) @louisliu2048 创建新channel需要创建这个channel的初始区块。组织创建网络的权限在系统通道里，orderer/writer 权限。
[ ](https://chat.hyperledger.org/channel/twg-china?msg=R5Xc8QrW5SHLfb3SL) @baohua 嗯嗯，谢谢老师，问题已经解决了，修改network的sys channel的配置就可以完成这个工作了。
请问一下，Composer的Angular Web程序生成工具只能生成比较简单的应用进行测试吗？我的Composer业务网络已经完成了，现在想做前端应用，我的应用比较简单，可选择什么框架来完成前端应用的开发呢？我的开发经验不太多，期待您详细的回答，万分感谢。:blush::blush::blush:
Has joined the channel.
Has joined the channel.
@here Hyperledger wiki (wiki.hyperledger.org) has done the migration to confluence (much faster), old content can be found at https://wiki-archive.hyperledger.org.
Has joined the channel.
Has joined the channel.
冒个泡:nerd:
老师请问下 这个问题怎么解决
Clipboard - February 9, 2019 8:30 PM
Fabric 初学者，请问一个问题： 一个orderer只有一个创始区块，是否意味着在这个orderer创建的所有Channel，都起源于这个相同的创始区块？ 谢谢
[ ](https://chat.hyperledger.org/channel/twg-china?msg=NFBtbuN9sEsXci4Qp) @hexiaohu 每个channel有一个创世区块。可以把每个channel看做不同的账本。
Has joined the channel.
大家好，请教个问题： fabric-sdk-go 可不可以修改Channel配置添加新的组织，我看了sdk源码里有createOrUpdateChannel方法，貌似可以修改Channel配置，但是go sdk中pb的struct不全，也没有找到比较详细的channel配置数据结构说明，不知道大家有没有修改成功的？
@baohua 老师好， 请问每个fabric集群不就只有一个orderer的创世区块(genesis.block)吗？就是系统链吧？还有在已存在的fabric集群中新创建一个新的channel的步骤是不是：1. 在原有的configtx.yaml修改添加新组织（或者原来配置好的组织），profiles配置新channel。2. 工具configtxgen -profile 生成新的channel.tx. 3. 新的组织（或者原来已存在的组织）的peer join即可？
Has joined the channel.
[ ](https://chat.hyperledger.org/channel/twg-china?msg=EBoJ48TYsvLrtcRH4) @xDxD 步骤3之前应该还有一个 peer channel create 的过程，需要先创建 channel 之后才能 join
@tinywell 恩漏了， 多谢提醒。重点是第一步，生成config那步骤不是很清楚具体应该怎么做，请问了解具体步骤吗？
[ ](https://chat.hyperledger.org/channel/twg-china?msg=MLP4c7uRb3tqfjGZ9) @xDxD 我一般直接仿照示例配置，在 profile 项下添加自己的 channel 配置，略微修改 application 下的组织等信息。（对各配置项了解程度有限，这是偷懒省事的做法）
@tinywell 知道了，多谢。我在动手试试吧
创建一个新channel，只需要先生成相应的tx，然后peer create，会返回对应的channel_name.block，后续配置下对应的org-peer节点就可以使用该block来join channel，我的理解
@guaguawa.github.io 恩 ，是的。go-sdk 也应该可以通过API创建channel吧
@xDxD go-sdk的代码我还没看呢:sweat_smile:
@guaguawa.github.io 看完发现比node的差很多啊
:sweat_smile:还在fabric代码部分晃
@guaguawa.github.io 用了这么多中间件或者平台，感觉fabric的用户体验差的太多了。。。
哪儿有BCCSP (BlockChain Crypto Service Provider) 的学习资料吗？ 谢谢
Has joined the channel.
Has joined the channel.
https://rocket.chat/docs/administrator-guides/google-cloud/auto-translate/
Charges are approx $20/1 million characters
Hoping to meet many of you in HongKong!
See you in HK!
If we can get a bot done that translates back and forth from WeChat, it might make life easier, including having much of the english Rocket Chat content mirrored in correct WeChat groups...
definitely a good idea...but do not think there's a public API.
@here This week's meeting agenda: https://wiki.hyperledger.org/display/TWGC/2019-02-27, feel free to help update!
Has joined the channel.
@baohua 目前有一个需求，想设计一个 Org节点， 指定Org这个节点实现特殊的背书功能， 比如背书的过程中实现计费功能中的扣费，扣费信息上链。 fabric支持plugin的方式修改背书智能合约。请问可以实现这样的功能吗？
[ ](https://chat.hyperledger.org/channel/twg-china?msg=AFb4f6vnrSjZrupff) @duwenhui 应该可以
请问一下，fabric的transaction在账本中的记录是明文还是密文？比如调用了链码的invoke函数，参数是 {"Args":["invoke","a","b","10"]}，账本文件中会看到a b 10 等参数吗？
@wangkaixuan 明文
[ ](https://chat.hyperledger.org/channel/twg-china?msg=uMMJPoKG3FqLooJNa) @xDxD 好的，谢谢。
请教大家一个问题，使用java-sdk部署富查询链码，couchdb 里面查询不到对应的索引文件。直接使用命令行部署，是可以查看得到索引文件的
I am in HK bootcamp these 2 days, feel free to find me if you're here 🙂 Mostly i will round table 1&2.
Has joined the channel.
大家好，欢迎讨论caliper相关问题
Has joined the channel.
Has left the channel.
orderer 1.4 (我本地build的），老报错: `Orderer capability v1_1 is required but not supported`, 有人碰到过和解决过这样的错吗？ 谢谢
Has joined the channel.
group meeting will be hosted on Wednesday 10:00 AM, welcome to attend https://wiki.hyperledger.org/display/TWGC/2019-03-13 @baohua
@here
Zhenhua
[ ](https://chat.hyperledger.org/channel/twg-china?msg=aYpuhak6r5kPE7mcS) @hexiaohu 是不是genesis block 里面设置错了
[ ](https://chat.hyperledger.org/channel/twg-china?msg=mgGyphQdLFFjXQbos) @wangkaixuan 账本文件应该会出现 a,b但是10 应该没写到账本里
@VipinB Glad to have your strong and long term support in community!
[ ](https://chat.hyperledger.org/channel/twg-china?msg=vHdzSatPNh4odk5BQ) @davidkhala 好的，谢谢啦。
Has joined the channel.
请教一个问题，fabric-ca部署：4个orderer+4个kafka+3个zookeeper，两个组织，每个组织两个peer，针对每个组织一个ca。根据教程部署完成后，智能合约实例化报错找不到安装的智能合约，但是智能合约对应的容器已运行，说明是有的吧？
本地需要install
请问etcd的orderer配置变更是不是每次只能新增或删除一个节点？
Hey guys, if your members have any photos of my session "Forest & the Trees" please forward to either me or silona. I can post them in wiki under the page for the session
Has left the channel.
请教一个问题，chaincode query报错，但其实chaincode已安装， dev-peer0.org2.example.com-mycc-1.0容器运行日志已显示：
Error: endorsement failure during query. response: status:500 message:"make sure the chaincode mycc has been successfully instantiated and try again: getccdata mychannel/mycc responded with error: could not find chaincode with name 'mycc'"
请教一个问题，chaincode query报错，但其实chaincode已安装， dev-peer0.org2.example.com-mycc-1.0容器运行日志已显示：ex02 Init
Aval = 200, Bval = 400 但chaincode query报一下错误：
Error: endorsement failure during query. response: status:500 message:"make sure the chaincode mycc has been successfully instantiated and try again: chaincode mycc not found"
[ ](https://chat.hyperledger.org/channel/twg-china?msg=hPTmopL2Se8wuM85B) @davidkhala @davidkhala 谢谢回复，genesis.block是用configtxgen根据byfn的配置文件产生的，没有做任何的修改。 并且我把orderer.yaml修改后，使用provisional的方式也会产生相同的错。 不知道是否跟orderer的编译，或着依赖包有关系。 根据文档，capability跟binary的版本有关系 (能够提供什么能力集)，配置只是说要支持什么能力集。 现在的错误提示是说1.4不支持v1_1, 这是不可能的。 哪位大侠能帮帮？
@hexiaohu provisional 不推荐用的，而且配置文件其实并没有保证兼容，不间的你没修改就能在新版本用上，你要先将配置文件的 capability 先删除然后再调试。
@hexiaohu provisional 不推荐用的，而且配置文件其实并没有保证兼容，不见得你没修改就能在新版本用上，你要先将配置文件的 capability章节 先删除然后再调试。
@hexiaohu `V1_1`，V大写，试一下
[ ](https://chat.hyperledger.org/channel/twg-china?msg=fDxFgirNuiY5rYpLG) @davidkhala 如果我修改orderer的代码，在检测capabilities的时候硬返回，则没有问题。 通过代码可以看出，就是比较binary 是否有这种能力。 代码：github.com/hyperledger/fabric/common/capabilities/capabilities.go: Supported()
@hexiaohu 改成大写不好用？？
[ ](https://chat.hyperledger.org/channel/twg-china?msg=fszTPKzxXerHH8Eiw) @guoger 配置文件里本来就是大写的V1_1, 跟这个应该没有关系
@hexiaohu 你检查一下
你的配置文件应该不对
[ ](https://chat.hyperledger.org/channel/twg-china?msg=j2MxJnvjXBgGHZ6oi) @guoger 这是我的配置文件
[ ](https://chat.hyperledger.org/channel/twg-china?msg=j2MxJnvjXBgGHZ6oi) @guoger 这是我的配置文件的一部分：
\[ Capabilities:
# Channel capabilities apply to both the orderers and the peers and must be
# supported by both.
# Set the value of the capability to true to require it.
Channel: &ChannelCapabilities
# V1.3 for Channel is a catchall flag for behavior which has been
# determined to be desired for all orderers and peers running at the v1.3.x
# level, but which would be incompatible with orderers and peers from
# prior releases.
# Prior to enabling V1.3 channel capabilities, ensure that all
# orderers and peers on a channel are at v1.3.0 or later.
V1_3: true
# Orderer capabilities apply only to the orderers, and may be safely
# used with prior release peers.
# Set the value of the capability to true to require it.
Orderer: &OrdererCapabilities
# V1.1 for Orderer is a catchall flag for behavior which has been
# determined to be desired for all orderers running at the v1.1.x
# level, but which would be incompatible with orderers from prior releases.
# Prior to enabling V1.1 orderer capabilities, ensure that all
# orderers on a channel are at v1.1.0 or later.
V1_1: true
# Application capabilities apply only to the peer network, and may be safely
# used with prior release orderers.
# Set the value of the capability to true to require it.
Application: &ApplicationCapabilities
# V1.3 for Application enables the new non-backwards compatible
# features and fixes of fabric v1.3.
V1_3: true
# V1.2 for Application enables the new non-backwards compatible
# features and fixes of fabric v1.2 (note, this need not be set if
# later version capabilities are set)
V1_2: false
# V1.1 for Application enables the new non-backwards compatible
# features and fixes of fabric v1.1 (note, this need not be set if
# later version capabilities are set).
V1_1: false
\]
[ ](https://chat.hyperledger.org/channel/twg-china?msg=j2MxJnvjXBgGHZ6oi) @guoger 这是我使用工具configtxgen的配置文件，来产生genesis block. Capabilities的部分如下：
Capabilities:
# Channel capabilities apply to both the orderers and the peers and must be
# supported by both.
# Set the value of the capability to true to require it.
Channel: &ChannelCapabilities
# V1.3 for Channel is a catchall flag for behavior which has been
# determined to be desired for all orderers and peers running at the v1.3.x
# level, but which would be incompatible with orderers and peers from
# prior releases.
# Prior to enabling V1.3 channel capabilities, ensure that all
# orderers and peers on a channel are at v1.3.0 or later.
V1_3: true
# Orderer capabilities apply only to the orderers, and may be safely
# used with prior release peers.
# Set the value of the capability to true to require it.
Orderer: &OrdererCapabilities
# V1.1 for Orderer is a catchall flag for behavior which has been
# determined to be desired for all orderers running at the v1.1.x
# level, but which would be incompatible with orderers from prior releases.
# Prior to enabling V1.1 orderer capabilities, ensure that all
# orderers on a channel are at v1.1.0 or later.
V1_1: true
# Application capabilities apply only to the peer network, and may be safely
# used with prior release orderers.
# Set the value of the capability to true to require it.
Application: &ApplicationCapabilities
# V1.3 for Application enables the new non-backwards compatible
# features and fixes of fabric v1.3.
V1_3: true
# V1.2 for Application enables the new non-backwards compatible
# features and fixes of fabric v1.2 (note, this need not be set if
# later version capabilities are set)
V1_2: false
# V1.1 for Application enables the new non-backwards compatible
# features and fixes of fabric v1.1 (note, this need not be set if
# later version capabilities are set).
V1_1: false
[ ](https://chat.hyperledger.org/channel/twg-china?msg=j2MxJnvjXBgGHZ6oi) @guoger 顺便确认一下，是认为产生的genesis block中的值不对吗？还是yaml文件不对？
yaml是用来生成genesisblock的，如果yaml不对，genesis block自然也不对。你的Log里边的v1_1是小写的。我把configtx.yaml的key改成小写也能复现你的问题 @hexiaohu
把你的configtx.yaml文件给我发一下
这种大小写的就是天坑了
[ ](https://chat.hyperledger.org/channel/twg-china?msg=rjwCa5rmAZcbpcQ8s) @guoger 我已经发给你yaml文件了，我也注意到了log里写的是小写的v了，谢谢
Guys, we have added a call at 12 pm UTC for the Identity WG specifically for APAC. Please join to talk about and contribute to Identity issues which is a fundamental concern in any permissioned blockchain.
12 noon EDT and 8 pm EDT March 20, 2019
That would be 4 pm UTC and 12 midnight UTC (March 20, 2019)
Trying an experiment tomorrow by running multiple calls at different times with the same Agenda. This is an attempt to escape the time zone limitations of our calls.
4 pm UTC is good for The whole of North and South America as well as Europe and possibly parts of the near East.
12 midnight UTC the whole of East Asia, Australia etc.
We might fiddle with these dates and times. What is unknown at this point is the level of interest we might get
Two calls tomorrow:
4 pm UTC and 12 midnight UTC
Join from PC, Mac, Linux, iOS or Android: https://zoom.us/my/hyperledger.community
All are welcome.-
The paper is: https://docs.google.com/document/d/1ExFNRx-yYoS8FnDIUX1_0UBMha9TvQkfts2kVnDc4KE/edit#
Meeting minutes:
We are taking the minutes on the wiki now. Please edit collaboratively or send updates by email. This is the location (https://wiki.hyperledger.org/display/IWG/2019-03-20+Notes)
You need a LF ID to login to edit.
To read passively you do not need a LFID
Agenda: https://wiki.hyperledger.org/display/IWG/2019-03-20
All are welcome. You do not have to be a member of Hyperledger to be on the call!
zoom details
iPhone one-tap :
US: +16465588656,,4034983298# or +16699006833,,4034983298#
Or Telephone:
Dial(for higher quality, dial a number based on your current location):
US: +1 646 558 8656 or +1 669 900 6833 or +1 855 880 1246 (Toll Free) or +1 877 369 0926 (Toll Free)
Meeting ID: 403 498 3298
International numbers available: https://zoom.us/u/bAaJoyznpThis is an open call.
Has joined the channel.
有人吗？ go-sdk
go-sdk channel: https://chat.hyperledger.org/channel/fabric-sdk-go
Hi all
group meeting will be hosted on Wednesday 10:00 AM, welcome to attend https://wiki.hyperledger.org/display/TWGC/2019-03-27 . @here
请教一个问题，默认策略
/Channel/Readers: ImplicitMetaPolicy-ANY Readers ，“ANY Readers” 中的“Readers”指的是什么?
是指所有的 /Channel/*/Readers 吗？
Has joined the channel.
yes
Next Identity WG call targeted for APAC April 4 00:00 UTC. Please join- Agenda is here: https://wiki.hyperledger.org/display/IWG/2019-04-03
Has joined the channel.
@baohua @guoger 想咨询一个问题，把一个Peer的LocalMsp的Certificates (公钥，私钥也换了)换了会导致什么后果呢？比如1：对将来的Transation会有什么影响？ 2: 对历史的Transation （已经存入Ledger的）会有什么影响? 谢谢。
将来的endorsement会用新的签名
Hi guys, as we made the second call of the ID WG at 00:00 UTC for the benefit of APAC members, we did not see attendance from China there. We have participation from Japan and Australia. Please let us know what else the Chinese community would like to discuss and contribute in Identity Working Group. What would be fantastic would be any work that you could share on Identity in the APAC region which has a direct influence on the solutions that we develop in Hyperledger DLT for Identity and Access Management. Any open documentation or data or code on these regulations also could help. No matter if these are in Chinese, we could attempt to translate them. I had posted about the JD.com open sourcing of JD Blockchain in linked in. Id anyone is aware of the details of their Identity solution, please contribute. I have the translation from JD.com here...https://docs.google.com/document/d/1HuvidddNlxZaLIJEgc9X1qVZzC1ZhGzXeQk20Sfky4M/edit?usp=sharing; however it is bare bones google translate and may not express ideas from Chinese properly. In particular there is a challenge to translate images...If anyone is aware of tools to deal with this, we need to be made aware. Thanks
Hi guys, as we made the second call of the ID WG at 00:00 UTC for the benefit of APAC members, we did not see attendance from China there. We have participation from Japan and Australia. Please let us know what else the Chinese community would like to discuss and contribute in Identity Working Group. What would be fantastic would be any work that you could share on Identity in the APAC region which has a direct influence on the solutions that we develop in Hyperledger DLT for Identity and Access Management. Any open documentation or data or code on these regulations also could help. No matter if these are in Chinese, we could attempt to translate them. I had posted about the JD.com open sourcing of JD Blockchain in linked in. Is anyone is aware of the details of their Identity solution, please contribute. I have the translation from JD.com here...https://docs.google.com/document/d/1HuvidddNlxZaLIJEgc9X1qVZzC1ZhGzXeQk20Sfky4M/edit?usp=sharing; however it is bare bones google translate and may not express ideas from Chinese properly. In particular there is a challenge to translate images...If anyone is aware of tools to deal with this, we need to be made aware. Thanks
Has joined the channel.
group meeting will be hosted on this Wednesday 10:00 AM, welcome to attend https://wiki.hyperledger.org/display/TWGC/2019-04-10 @baohua
请问private collection能做到数据只能被组织下某些成员访问到吗？
请问一下channel configuration 和 network configuration的改动transaction都被记录到一个链里吗，"system-channel"?
@Randyshu2018 private data的粒度应该是在org，所以我觉得应该是不行。
@hexiaohu 你指的network configuration是什么？
[ ](https://chat.hyperledger.org/channel/twg-china?msg=dwZLmnH6suM9RHEc2) @guoger 好的，谢谢您，那么如果我有更细颗粒度的需求的话，是不是考虑用智能合约的cid进行控制，或者有没有更好的方案？
[ ](https://chat.hyperledger.org/channel/twg-china?msg=9BWT5S8qYRhcnQCPy) @guoger Network configuration 就是定义了consortium 和 orderer organization的configuration
[ ](https://chat.hyperledger.org/channel/twg-china?msg=uHb3Aa5ceaQojxha3) @Randyshu2018 我觉得应该就是用cid了
[ ](https://chat.hyperledger.org/channel/twg-china?msg=QtNyHNuCBzAxvESm5) @hexiaohu channel config会被记录在相应的channel内。consortium和orderer org的改动会被记录在system channel里
https://wiki.hyperledger.org/display/TWGC
[ ](https://chat.hyperledger.org/channel/twg-china?msg=679wLFkkSfwSHbGHB) @guoger 谢谢郭！ 我再更新一下我的问题：channel 级别的 configuration transaction 会被存储在哪个Ledger里呢？ 是和 Network 级别的 configuration transaction 存储在相同的ledger （属于system channel）里？还是存储在相应channel的Ledger里? 还是有自己独立的存储Ledger?
https://www.hyperledger.org/community/technical-ambassador
[ ](https://chat.hyperledger.org/channel/twg-china?msg=ZioaqiPN5kP2MDM5e) @hexiaohu 存储在相应channel的Ledger里
@guoger 郭哥，我今天从开发者角度试用1.4.1-rc1有一些疑问：https://github.com/hyperledger/fabric/blob/release-1.4/sampleconfig/configtx.yaml
1. 这里面的Address 配置部分还需不需要？
2. 这里面的ClientTLSCert: path/to/ClientTLSCert0， ServerTLSCert: path/to/ServerTLSCert0，分别应该用哪个证书？
我刚看了后面的部分文档 问题1解决了
> 2. 这里面的ClientTLSCert: path/to/ClientTLSCert0， ServerTLSCert: path/to/ServerTLSCert0，分别应该用哪个证书？
可以看一下byfn里边configtx.yaml的例子。暂时用的都是tls server cert
嗯，看来sampleConfig这边需要一些注释更新
我意思是例子里使用的是server cert，但在实际中是完全可以配置的
理论上应该使用不同的cert，一个用于client auth，一个用于server auth
不过例子里为了简单，就用一样的了
就是可以完全不同的一套TLS？甚至这个TLS都不需要跟Orderer自己的TLS相关？
对
酷炫
self sign也可以
那么有个疑问就是，这套独立的TLS私钥放哪了？
```
# Cluster settings for ordering service nodes that communicate with other ordering service nodes
# such as Raft based ordering service.
Cluster:
# SendBufferSize is the maximum number of messages in the egress buffer.
# Consensus messages are dropped if the buffer is full, and transaction
# messages are waiting for space to be freed.
SendBufferSize: 10
# ClientCertificate governs the file location of the client TLS certificate
# used to establish mutual TLS connections with other ordering service nodes.
ClientCertificate:
# ClientPrivateKey governs the file location of the private key of the client TLS certificate.
ClientPrivateKey:
# The below 4 properties should be either set together, or be unset together.
# If they are set, then the orderer node uses a separate listener for intra-cluster
# communication. If they are unset, then the general orderer listener is used.
# This is useful if you want to use a different TLS server certificates on the
# client-facing and the intra-cluster listeners.
# ListenPort defines the port on which the cluster listens to connections.
ListenPort:
# ListenAddress defines the IP on which to listen to intra-cluster communication.
ListenAddress:
# ServerCertificate defines the file location of the server TLS certificate used for intra-cluster
# communication.
ServerCertificate:
# ServerPrivateKey defines the file location of the private key of the TLS certificate.
ServerPrivateKey:
```
ClientPrivateKey:这个如果unset时候，就是重用回原来orderer的私钥么？
就用orderer与client之间使用的cert&key了
就用orderer与~client~sdk/cli之间使用的cert&key了
就用orderer与 ~client~sdk/cli之间使用的cert&key了
这里的Client指的是类似sdk应用那种么？我以为是指的另一个raft node
我更新了我的回复
嗯，这样看起来，以前传统上client连orderer一般都是用的orderer组织的TLScert, 现在在双方都用另一套TLS的情况下甚至可以换另一个TLS来接orderer了
orderer之间的tls连接，与其他的tls连接是相互独立的
可以配置成使用相同的cert&key，也可以不同
那是不是就是上面cluster.ClientPriv-cert这套用于client连orderer，clusterServerPriv-cert这套用于orderer之间互联？
cluster里的client，指的是tls中server-client的client
与sdk/cli那种client不一样
从一个orderer node的角度来讲，其他尝试与之进行连接的，都是TLS client。这个client可以是sdk/cli，也可以是另一个orderer
那么你可以给这两种TLS连接，都使用相同的cert
也可以使用不同的
```
# This is useful if you want to use a different TLS server certificates on the
# client-facing and the intra-cluster listeners.
```
这句话里的 `client-facing` 指的是cli/sdk
```
# This is useful if you want to use a different TLS server certificates on the
# client-facing and the intra-cluster listeners.
```
这句话里的 `client-facing` 指的是cli/sdk/peer
所以Cluster.ClientPrivateKey适用于服务其他尝试与之连接的，Cluster.ServerPrivateKey适用于自己向其他服务尝试TLS连接的，这样对么？
还是反过来？
反过来
server private key用于签名发出去的消息，向client证明自己的身份。
orderer之间的链接是双向认证的，所以两边都需要server/client cert&key
对嘛，那就是不用反过来
（你对）
反过来的
server接到别人发来的请求，回复的时候用server private key签名
：）
我将加密解密和签名校验的表述跟你相反了哈哈
哦哦 你本想说的是server cert用于向其他服务尝试tls连接是吧
tls连接本身就是两次握手，所以光说一个方向是不对的
用于验证server端返回的消息
没事，我理解了
说一个方向是可以的，因为这个和握手还不是同一个事情
一般web服务都是用server auth
不用client auth
@davidkhala 最好能再帮忙试一下eyfn.sh
一般web服务都是用server auth
>>是的，不然一般软件用户带证书私钥不方便
我刚才看漏了一行，现在懂了
我刚才看漏了一行，现在懂了， ServerCertificate这边类似于TLS里面的client Auth
我刚才看漏了一行，现在懂了， ServerCertificate这块类似于TLS里面的client Auth
@davidkhala 最好能再帮忙试一下eyfn.sh
@davidkhala 最好能再帮忙试一下 eyfn.sh
@davidkhala 最好能再帮忙试一下 `eyfn.sh`
@guoger kafka是不是现在希望逐渐deprecate了？
是的
@guoger 请教一个问题， cacerts目录下是否可以放多个ca证书，并且多个ca证书的subject是一样的，但是publickey是不一样的？
@guoger 请教一个问题， MSP cacerts目录下是否可以放多个ca证书，并且多个ca证书的subject是一样的，但是publickey是不一样的？
@guoger
[orderer.commmon.multichannel] newChainSupport -> PANI 15d Error retrieving consenter of type: etcdraft
这一般是为什么？
@davidkhala 是不是用了旧版本的orderer binary
请教一个问题，在Composer的query里面如何对字符串字段进行模糊查询，query的where的条件的比较语法关键词里面没有like，有一个看着有点像操作符 %= , 但写出来语法检查都通过不了，有点郁闷
[ ](https://chat.hyperledger.org/channel/twg-china?msg=XTK78gdzQab7jQwou) @guoger 应该是新的了，不过我这边orderer环境里面Cluster这个section整个都没设置，是不是这样就没法识别？
特别是没有手动制定listen port的话
特别是没有手动指定listen port的话
应该没关系。。。有没有完整的log？
typo 了哈哈 "fabricTag": "1.4.0-rc1",
现在createChannel还会出这种错误？ @guoger status=SERVICE_UNAVAILABLE, info=no Raft leader
如果raft没选出leader，会报这种错。
郭哥我发现一个文档bug了
https://github.com/hyperledger/fabric-samples/blob/release-1.4/first-network/base/peer-base.yaml first network 里面有cluster....rootCA这一项
https://github.com/hyperledger/fabric-samples/blob/release-1.4/first-network/base/peer-base.yaml这里面Cluster里面缺了RootCA这一项
https://github.com/hyperledger/fabric-samples/blob/release-1.4/first-network/base/peer-base.yaml first network 里面有cluster....rootCA这一项
https://github.com/hyperledger/fabric-samples/blob/release-1.4/first-network/base/peer-base.yaml 这里面Cluster里面缺了RootCA这一项
https://github.com/hyperledger/fabric-samples/blob/release-1.4/first-network/base/peer-base.yaml first network 里面有cluster....rootCA这一项
https://github.com/hyperledger/fabric/blob/release-1.4/sampleconfig/orderer.yaml 这里面Cluster里面缺了RootCA这一项
难怪TLS互联失败。。
@davidkhala 第二个链接和第一个一样
typo?
改了
另外好像不支持非TLS模式？consenter info in etcdraft configuration did not specify client TLS cert
恩，要开启TLS
我这边测试基本没问题了，唯一就是刚启动orderer的时候 client通过grpc sendDeliver的时候会返回NOT_FOUND，要过几秒重试才行。以前我在kafka的时候也有重试机制，只不过对应的关键字是`Stream removed`
我这边测试基本没问题了，唯一就是刚启动orderer的时候 client通过grpc sendDeliver的时候会返回NOT_FOUND，要过几秒重试才行。以前我在kafka的时候也有重试机制，只不过对应的关键字是`SERVICE_UNAVAILABLE`
@davidkhala @guoger 请教一下，有怎样修改network configuration的文档吗？ 我想修改consortium （一共两个org） 里的其中一个org的MSP配置，使用这个org的admin去修改，但是说 permission denied： Error: got unexpected status: FORBIDDEN -- Failed to reach implicit threshold of 1 sub-policies, required 1 remaining: permission denied
你需要用orderer组织的admin去改
[ ](https://chat.hyperledger.org/channel/twg-china?msg=7LL4AqBQH8ZF3gbNw) @davidkhala NOT_FOUND?? 完整的error是什么？
[ ](https://chat.hyperledger.org/channel/twg-china?msg=eKe4skHWk5euiPqWj) @guoger 这个error不知道是不是grpc-node封装过了，我这边没看到特别多的信息
因为我是通过grpc的nodejs库去连的
有哪位知道怎么动态修改orderer的logging级别吗？ peer logging 好像只能修改动态修改peer的logging级别？
@hexiaohu orderer实现了，但是cli貌似没有做
[ ](https://chat.hyperledger.org/channel/twg-china?msg=bpdoE8HPXL4fg7jEk) @guoger 谢谢:thumbsup:
请问 raft共识中，所有orderer节点加到系统通道，应用通道可以从中挑一些组成自己的共识集群，这个是跟什么地方的配置相关？一个应用通道如何配置自己的共识集群？byfn的例子中没有看到相关配置，尝试配置应用通道的 /Channel/Orderer 的配置信息似乎无效
[ ](https://chat.hyperledger.org/channel/twg-china?msg=zwBBmv933eoKpemQq) @tinywell ```
Consenters:
- Host: raft0.example.com
Port: 7050
ClientTLSCert: path/to/ClientTLSCert0
ServerTLSCert: path/to/ServerTLSCert0
- Host: raft1.example.com
Port: 7050
ClientTLSCert: path/to/ClientTLSCert1
ServerTLSCert: path/to/ServerTLSCert1
- Host: raft2.example.com
Port: 7050
ClientTLSCert: path/to/ClientTLSCert2
ServerTLSCert: path/to/ServerTLSCert2
```
主要是这一段的配置
你可以在创建channel的时候指定一个subset，不过在使用 `configtxgen` 创建channel creation tx的时候，要记得使用 `channelCreateTxBaseProfile` 指向genesis profile。
或者可以创建了channel之后，再从channel里删除一个orderer。
谢谢
加上channelCreateTxBaseProfile参数后，生成的channel.tx附加上了对Orderer的ConsensusType、OrdererAddresses等值的更新，满足相关策略后即可创建指定raft集群的channel。但是有一点很奇怪的是，生成的channel.tx中，对 Applicaiton 下的所有子group以及自身version 变成 1，而正常创建的channel.tx 只会对Applicaiton本身的version变为1，这导致需满足的策略有些差异，不知道是我使用的不对还是理解有误
[ ](https://chat.hyperledger.org/channel/twg-china?msg=bEHpi4j67hdKYPrh2) @hexiaohu 拿healtthz的restful 服务改就可以了，非常方便的 这个特性在1.4版本加入的
说起来，Xing Zhou（TOM）在群里么？
[ ](https://chat.hyperledger.org/channel/twg-china?msg=yAh7buBPZ9GkinpQd) @davidkhala 谢谢
@davidkhala @guoger 想确认一下Fabric MSP支持配置在线的第三方CA吗？
Identity WG will continue its two calls schedule for April 17th/18th that would be 4 pm UTC and *01:00* midnight UTC (April 18th for UTC and points East)
PLEASE NOTE THE CHANGED TIME FOR SECOND CALL
Hello all,
Multiple calls at different times with the same Agenda. This is an attempt to escape the time zone limitations of our calls.
4 pm UTC is good for The whole of North and South America as well as Europe and possibly parts of the near East.
01:00 midnight UTC the whole of East Asia, Australia etc. (this would be the next day for all points UTC and East)
We are still fiddling with these dates and times.
Join from PC, Mac, Linux, iOS or Android: https://zoom.us/my/hyperledger.community
All are welcome.-
The paper is: https://docs.google.com/document/d/1ExFNRx-yYoS8FnDIUX1_0UBMha9TvQkfts2kVnDc4KE/edit#
Meeting minutes:
We are taking the minutes on the wiki now. ( https://wiki.hyperledger.org/display/IWG/2019-04-17+Notes ) Please edit collaboratively or send updates by email.
You need a LF ID to login to edit.
To read passively you do not need a LFID
Agenda: https://wiki.hyperledger.org/display/IWG/2019-04-17
Select items from the Agenda (go to the link for details):
-Work on the paper
-Report to TSC
-Agent 2 Agent discussion
-DiD schemas presentation by Jim Wowchuk
All are welcome. You do not have to be a member of Hyperledger to be on the call!
zoom details
iPhone one-tap :
US: +16465588656,,4034983298# or +16699006833,,4034983298#
Or Telephone:
Dial(for higher quality, dial a number based on your current location):
US: +1 646 558 8656 or +1 669 900 6833 or +1 855 880 1246 (Toll Free) or +1 877 369 0926 (Toll Free)
Meeting ID: 403 498 3298
International numbers available: https://zoom.us/u/bAaJoyznpThis is an open call.
Please reach out if you have questions, attend the call, participate to collaborate!
Identity WG will continue its two calls schedule for April 17th/18th that would be 4 pm UTC and *01:00* AM UTC (April 18th for UTC and points East)
PLEASE NOTE THE CHANGED TIME FOR SECOND CALL
Hello all,
Multiple calls at different times with the same Agenda. This is an attempt to escape the time zone limitations of our calls.
4 pm UTC is good for The whole of North and South America as well as Europe and possibly parts of the near East.
01:00 AM UTC the whole of East Asia, Australia etc. (this would be the next day for all points UTC and East)
We are still fiddling with these dates and times.
Join from PC, Mac, Linux, iOS or Android: https://zoom.us/my/hyperledger.community
All are welcome.-
The paper is: https://docs.google.com/document/d/1ExFNRx-yYoS8FnDIUX1_0UBMha9TvQkfts2kVnDc4KE/edit#
Meeting minutes:
We are taking the minutes on the wiki now. ( https://wiki.hyperledger.org/display/IWG/2019-04-17+Notes ) Please edit collaboratively or send updates by email.
You need a LF ID to login to edit.
To read passively you do not need a LFID
Agenda: https://wiki.hyperledger.org/display/IWG/2019-04-17
Select items from the Agenda (go to the link for details):
-Work on the paper
-Report to TSC
-Agent 2 Agent discussion
-DiD schemas presentation by Jim Wowchuk
All are welcome. You do not have to be a member of Hyperledger to be on the call!
zoom details
iPhone one-tap :
US: +16465588656,,4034983298# or +16699006833,,4034983298#
Or Telephone:
Dial(for higher quality, dial a number based on your current location):
US: +1 646 558 8656 or +1 669 900 6833 or +1 855 880 1246 (Toll Free) or +1 877 369 0926 (Toll Free)
Meeting ID: 403 498 3298
International numbers available: https://zoom.us/u/bAaJoyznpThis is an open call.
Please reach out if you have questions, attend the call, participate to collaborate!
[ ](https://chat.hyperledger.org/channel/twg-china?msg=yBNhMD83hwtMxEtoj) @hexiaohu 其实不一定需要在线的，离线也可以，通道里面的msp配置写在了链上，跟CA服务本身是没有耦合性的
[ ](https://chat.hyperledger.org/channel/twg-china?msg=6L9wSA7Fp6wLviKD8) @davidkhala 就是想确认一下，是否支持在线3方的CA.
[ ](https://chat.hyperledger.org/channel/twg-china?msg=FoZSMCEkCeSqAXtcC) @hexiaohu 支持的，只要PKI兼容
[ ](https://chat.hyperledger.org/channel/twg-china?msg=7njxBhX67fezPWiM7) @davidkhala 可能我的问题会有歧义： 我的意思是Fabric在运行时，是否支持动态在线的CA验证，CRL验证，而不是离线的用一个第三方CA，先把一堆证书创建好以后，放到MSP再用（其实这种方式就是我说的离线）？
[ ](https://chat.hyperledger.org/channel/twg-china?msg=8pAbbiRALqfnnjf62) @hexiaohu CA以及CRL这些部分是Fabric-ca做支持的，我记得fabric通道里面并不会存储这些信息，通道里面只存了证书根，以及TLS证书根，以及一个管理员证书列表。因此fabric节点运行时本身并不会访问外部的在线CA， 要做只能在应用层做，现在的很多sample也确实是这么做的。 当然，对于普通的非admin的User，完全可以在网络运行起来之后去CA申请验证，但是fabric网络只会对他做最基本的根证书校验
[ ](https://chat.hyperledger.org/channel/twg-china?msg=9cmKq7DZcAwBpnta4) @davidkhala 谢谢， 你提了很重要的点，可以帮助理解。通道的MSP配置信息目前应该不会实时连接在线的CA做实时更新的，这也从侧面证明目前Fabric MSP不支持连接在线CA的。另：通道MSP会存储CRL，这个我已经做实验确认过了。
[ ](https://chat.hyperledger.org/channel/twg-china?msg=62BoxTsXGwXErr63k) @hexiaohu 这个CRL放在通道的那个属性下面了？
或者我这个表述也有可能不对，毕竟代码在发展，不知道改成什么样了
@hexiaohu 看到了，在某个版本里面加进去了
https://hyperledger-fabric.readthedocs.io/en/release-1.4/msp.html?highlight=CRL#msp-setup-on-the-peer-orderer-side
@hexiaohu 看到了，在某个版本里面加进去了，多谢提醒
https://hyperledger-fabric.readthedocs.io/en/release-1.4/msp.html?highlight=CRL#msp-setup-on-the-peer-orderer-side
第5条，optional
@luckforzhang hi
Has joined the channel.
原来你们都在这里讨论。。。我用蹩脚的英文在别的频道交流了好几天
@All
Dear all, we will have the group meeting at 10AM this Wednesday morning, feel free to update the agenda at https://wiki.hyperledger.org/display/TWGC/2019-04-24 before the meeting. Welcome to attend, thanks!
@All
Dear all, we will have the group meeting at 10AM this Wednesday morning, feel free to update the agenda at https://wiki.hyperledger.org/display/TWGC/2019-04-24 before the meeting. Welcome to attend, thanks!
各位，请教一下有么有遇到过截图中的错误？
请教下大家有没有遇到一下截图中的错误？
环境：v1.4.1
部署环境：华为云 1个orderer 一个 peer.org1 ， 阿里云 一个 peer.org2 一个 cli
环境网络都是通的，可以初始化以及加入通道，更新组织锚节点。在各个 peer 节点安装链码以后，初始化链码的时候报错。
1.png
2.png
我猜是用docker daemon启动容器报错。。不过没试过
链码镜像生成了 但是启动链码容器的时候出错
两个环境单独运行 first-network 都没有问题
container exit with 0
是不是cc退出了。。。
https://jira.hyperledger.org/browse/FAB-14741 这个跟我的错误一样 但是他是 node 链码 v2.0.0 我是 go 链码v1.4.1
单机环境都没有问题 网络也是通的
看一下cc container的log?
peer 节点可以这样配置参数吗？CORE_PEER_ID=peer1.org1.example.com
CORE_PEER_ADDRESS=ip2:7051
CORE_PEER_LISTENADDRESS=0.0.0.0:7051
CORE_PEER_CHAINCODEADDRESS=ip2:7052
CORE_PEER_CHAINCODELISTENADDRESS=0.0.0.0:7052
CORE_PEER_GOSSIP_BOOTSTRAP=ip1:7051
CORE_PEER_GOSSIP_EXTERNALENDPOINT=ip2:7051
ccenv 的日志？
应该有一个chaincode container
链码容器是会运行一下 然后报错就把容器删除掉了
链码容器报的什么错？
我看看 链码容器运行一下就被删除了
2019-04-25 10:38:41.699 UTC [shim] userChaincodeStreamGetter -> ERRO 001 context deadline exceeded
error trying to connect to local peer
github.com/hyperledger/fabric/core/chaincode/shim.userChaincodeStreamGetter
/opt/gopath/src/github.com/hyperledger/fabric/core/chaincode/shim/chaincode.go:112
github.com/hyperledger/fabric/core/chaincode/shim.Start
/opt/gopath/src/github.com/hyperledger/fabric/core/chaincode/shim/chaincode.go:151
main.main
/chaincode/input/src/github.com/hyperledger/fabric-samples/chaincode/chaincode_example02/go/chaincode_example02.go:195
runtime.main
/opt/go/src/runtime/proc.go:201
runtime.goexit
/opt/go/src/runtime/asm_amd64.s:1333
这个代码日志
ip2是什么？
ip1 ip2 是两台服务器的地址
fabric-sdk-go tls怎么关闭，能传授下经验不
[ ](https://chat.hyperledger.org/channel/twg-china?msg=Gaf2ij2ebY9A43Jhy) @james3443112 你把peer容器的7052端口映射出来试一下。之前遇到过链码实例化的时候，链码容器生成成功了，但是启动一下就停止了。
感谢！还真是这样！
:ok_hand:
Has joined the channel.
Has joined the channel.
fabric-sdk-java 有没有动态增加节点、组织、通道的样例的？ 网上没找到，只有nodejs的:persevere:
大家好，请问有没有msp 最佳实践的实例（https://hyperledger-fabric.readthedocs.io/en/latest/msp.html#best-practices）
Has joined the channel.
这里是否可以探讨一些抽象的问题？ 区块链技术离爆发式发展，只缺少一个杀手级应用了。我认为主要原因是网络还不够分散，节点、子网络离得还不够远。所以，对去中心化不甚急迫。
[ ](https://chat.hyperledger.org/channel/twg-china?msg=sm8W5zESonFPafvuD) @Tom-Xu-CNXA 可以讨论。不过没懂你的描述，一方面说网络不够分散，另一方面说对去中心化的需求不急迫？
Has joined the channel.
@guoger 太好了，很高兴讨论一些技术之外的话题。 其实，我的意思是说，目前现有的IT框架所要处理的问题还是太简单，不够复杂； 网络所承载的内容还是太少，以至于人们认为：现在的网络足够了，为什么要用BLOCKCHAIN呢？现有的数据库已经很好了，为什么要分布式呢？中心授权不是很好吗，为什么要使用共识机制呢？ 如果不让人们觉得：下一个应用必须用BLOCKCHAIN， 否则，这个业务就不会实现。那么，人们就会等待。。。。。。而不是主动去应用这个技术。 就我个人而言，我很喜欢BLOCKCHAIN中体现的对等、共享等特性。 希望我们会有越来越多的KILLER APP。。。 但会有哪些呢？ 我们是不是可以主动设计一些区块链应用项目？以推动它发展。 是的，银行、保险、食品、物流等行业都说在推动，但，还远远不够。（个人浅见，欢迎批评指正）
@Tom-Xu-CNXA 我觉得，现在应用是拿着锤子找钉子，“主动设计一些区块链应用”在没有需求的情况下，是很难的。
@guoger 是的。技术与需求之间，有些时候正是相互促进的。
@guoger 是的。技术与需求之间，有些时候正是需要相互促进的。
可以比照下当初为啥会出现股票制企业（100年）和互联网（30年）这样的创新。
原来前辈在着:joy:早知道直接来着问好了:sweat_smile:
原来前辈在这:joy:早知道直接来这问好了:sweat_smile:
btw，如果有人想熟悉一下fabric代码贡献流程，这里有一个非常简单的task：https://jira.hyperledger.org/browse/FAB-15302
@baohua 互联网迅速发展的原因就是电脑越来越多了，它们产生了互相连接的需求。哈哈。
大佬们，问个问题，后续会用Raft替换掉现有的kafka共识。那么Raft针对kafka来说，除了在资源以及维护成本方面，还有哪些优势呢？
纯从共识算法角度，raft算法在大规模情况下应该会更快一些
raft这个patch除了本身的实现之外，也重新将orderer分组织这个事情提上了议程
我是觉得大家误会了很多，区块链本身的性质产生了不会产生爆炸应用，大家会说安卓带来了爆炸应用，iphone带来了爆炸应用，但是你听过说apacher http server，DB2, sqlite产生了爆炸应用么？没有，而这些正是区块链的常见场景，即使它被广泛应用，也很少会变成大家所说的爆炸。大家经常说java老了，C++已死，但是大家会说之前整个中间件拿java写的淘宝是爆炸应用， 股市高频交易是爆炸应用。
所以我觉得总是提爆炸应用的人们，应该是很缺钱了哈哈
不得不说，Rocket.Chat的thread UI跟slack没法儿比啊。太乱了
嗯。@davidkhala 说得有道理。HTTP & HTTP Server很快就成为基础设施了。但以HTTP为基础的电子商务、在线视频等应用是爆炸性的。
我试了下FABRIC 2.0 ALPHA里面的TOKEN。不知2.0正式版会不会支持chaincode interoperability，就是文档说的那样，允许 在CHAINCODE里直接使用TOKEN .
Has joined the channel.
请问，修改了fabric源码，改怎样调试我的代码
有谁尝试过chaincode容器内部plugin.Open("xxx.so")，导致chaincode程序崩溃
在容器内部写测试程序都是OK的，但是一集成到chaincode当中就挂了
各位大佬，我有一个问题fabric的共识算法中kafka比着solo模式性能有提升吗？新出现的raft比着kafka有什么性能上的提升吗？
What's the log msg?
The performance improvement is not the major purpose, however, it does.
找到问题了，应该把peer节点环境变量设置CORE_CHAINCODE_GOLANG_DYNAMICLINK=true
但是我现在遇到另外一个情况，chaincode容器运行过程中我停止了，然后再去invoke chaincode，这时peer节点会去重新创建一个chaincode容器，而不是启动已经存在的chaincode容器，我看到DockerVM代码中的确没有判断容器是否存在的操作，Start函数内部先是stopInternal，再直接createContainer，而后startContainer，这里是否需要判断下，如果容器已经存在，直接启动，无需重新创建
各位大佬，fabric peer和order节点非docker部署，能不能实现远程资源监控呢？
@houqinghui 不知您所说的要监控的资源有哪些？METRICS或许能提供一些这方面的实时数据 。请参考：https://hyperledger-fabric.readthedocs.io/en/latest/operations_service.html?highlight=metrics
Fabric 本身提供了 metrics 功能，跟部署方式无关。
@Tom-Xu-CNXA @baohua 想要监控peer和orderer节点的资源消耗情况，如果是docker部署的话docker提供了远程或者资源占用情况的api，这样就可以获得cpu、内存等的占用情况了，但是如果不是docker部署的，怎么获得资源占用信息呢？
你如果是直接运行在虚拟机里面，传统的怎么获取现在仍然可以怎么获取。另外，可以使用fabric直接提供的metric 接口。
请问 fabric-ca-sdk-java 有望像fabric-ca-client一样 支持生成标准MSP目录的用户证书吗？
Has joined the channel.
目前 北京公司基于fabric做联盟链的多么 前景怎么样
@baohua
我想在这方面提高技术的话 深入fabric源码是一方面 还有其他的么
您的书我也看了
目前我会的是 搭建fabric网络 可以自定义orderer，peer org，peer
相关poc使用的java sdk
最近有点迷茫 还请您杨先生 指点迷津 @baohua
闲了也会阅读fabric 文档
自己编译你镜像
Has joined the channel.
Howdy!
someone deleted the Description from your page https://wiki.hyperledger.org/display/TWGC/Technical+Working+Group+China
please add that back as it is required to be listed properly in the wiki.
Silona, i checked recent changes, not found the deletion? Which part are you referring to? Thanks!
It was deleted in February but Just noticed. All need to have a description for the scripts to work
I saw the change. @richzhao . The description disappeared at your v15 change, would you like to add the description part again?
https://wiki.hyperledger.org/pages/viewpreviousversions.action?pageId=2392722
@Henretter 指点谈不上，有兴趣的话读读代码可以理解更深入一些。https://github.com/yeasy/hyperledger_code_fabric。另外推荐读一些论文，会有最新的技术突破。
restored @Silona @baohua
Thanks zhenhua:thumbsup:
谢谢 @baohua
未来几年区块链关于hyperledger技术人员会持续有需求么 怎么感觉最近关于hyperledger的新闻都很少了
目前我在北京一家创业公司做区块链技术 但不知道之后的前景会是什么样子 很忧虑 @baohua
这个话题有点大。市场和科技进步很多时候不同步的，有句话叫做，人们容易高估创新的短期影响力，低估其长期影响力。我个人认为，衡量先进科技的指标是推动生产力进步。长期来看，终归是要进步的。
这个话题有点大。市场和科技进步很多时候不同步的。有句话叫做，人们容易高估创新的短期影响力，低估其长期影响力。我个人认为，衡量先进科技的指标是推动生产力进步。长期来看，终归是要进步的。
恩 谢谢
@all
Dear all, we will have the group meeting at 8PM this Wednesday evening, feel free to update the agenda at https://wiki.hyperledger.org/display/TWGC/2019-06-05 before the meeting. Welcome to attend, thanks!
@all Dear all, we will have the group meeting at 8PM this Wednesday evening, feel free to update the agenda at https://wiki.hyperledger.org/display/TWGC/2019-06-19 before the meeting. Welcome to attend, thanks!
:thumbsup:
Has joined the channel.
大家好，请教大家一个问题，在使用 couchdb 作为状态数据时，如果查询条件比较复杂，需要建立大量的索引文件，造成索引文件占用大量的磁盘空间（一个分片差不多 1.5G，默认 8 分片就是 1.5*8）
@all Dear all, we will have the group meeting at 8PM this Wednesday evening, feel free to update the agenda at https://wiki.hyperledger.org/display/TWGC/2019-07-03 before the meeting. Welcome to attend, thanks!
大家好，请教个问题，使用 java-sdk，有时候会出现 orderer 节点假死无法通讯，但是重新初始化 HFClient 以后，服务又能正常使用。请问有朋友遇到过类似的问题吗？
Has joined the channel.
请问现在1.4版本的fabric，性能数据大概是怎样的啊？
i think it's not amazing, but good enough for most scenarios.
Has joined the channel.
请问有没有基于fabric的联盟治理方案？最近在查找资料的时候偶然发现一个github项目：https://github.com/hyperledger-labs/hyperledger-fabric-based-access-control，但是没有后续了
Hello Everyone!
First call of the Capital Markets SIG at 9:00 am EDT on July 17. This is 13:00 UTC and 21:00 Chinese standard time
All are welcome!
The Capital Markets Special Interest Group (CMSIG) represents industry professionals working together to study how Hyperledger DLTs interact with Capital Markets use cases. This covers issuance and trading of instruments to continued market-making, management of risk, program-trading, regulations, capital requirements, traceability, post trade settlement, custody including corporate actions and more. This group also explores architecture, identity and performance related considerations specific to Capital Markets and DLTs.
Most of our resources can be reached through the wiki page.
The first call will be on the hyperledger community zoom
Join from PC, Mac, Linux, iOS or Android: https://zoom.us/my/hyperledger.community
Please register for the mailing list and rocket channel if you have not done so.
Please think about volunteering for the vice-chair and scribing and recording the meeting.
The tentative Agenda: https://wiki.hyperledger.org/display/CMSIG/2019-07-17
SIG and Linux foundation introduction - KO 5 minutes
Anti Trust Policy & Code of Conduct - 3 minutes
Volunteer to scribe and record - 1 min
Introductions - 10-15 minutes
Meeting time - Poll - 1 minute
Volunteer for Vice Chair - 1 min
Topics for the SIG and AOB- Rest of the time
Work products
You need a LF ID to login to edit.
You do not need a LFID to read passively.
All are welcome. You do not have to be a member of Hyperledger to be on the call!
zoom details
iPhone one-tap :
US: +16465588656,,4034983298# or +16699006833,,4034983298#
Or Telephone:
Dial(for higher quality, dial a number based on your current location):
US: +1 646 558 8656 or +1 669 900 6833 or +1 855 880 1246 (Toll Free) or +1 877 369 0926 (Toll Free)
Meeting ID: 403 498 3298
International numbers available: https://zoom.us/u/bAaJoyznpThis is an open call.
Please reach out if you have questions, attend the call, participate to collaborate!
Has joined the channel.
为了方便更多社区成员参与，社区倒会改回周三上午10点了。欢迎大家参加 https://wiki.hyperledger.org/display/TWGC/2019-07-17。 feel free to add topics you want to discuss.
@all
@all
为了方便更多社区成员参与，经过上次会议讨论，社区例会改回周三上午10点了。欢迎大家参加 https://wiki.hyperledger.org/display/TWGC/2019-07-17。 feel free to add topics you want to discuss.
新增组织成员的功能有谁用fabric-sdk-java实现的么
You may ask in the fabric-sdk-java channel.
ok
Has joined the channel.
Has joined the channel.
@all we will host our group meeting at 10:00 am Wed, feel free to add topics you want to share 欢迎大家参加 https://wiki.hyperledger.org/display/TWGC/2019-07-31
Clipboard - July 31, 2019 3:26 PM
Please , @baohua
请教个问题，WORLDSTATE 的存储，目前是LEVELDB， COUCHDB。但对于一些场景，如果客户要求WORLDSTATE放在RBDM里，虽然说是PLUGABLE， 但必须 要写代码并重新编译FABRIC。 不知FABRIC 是否有计划支持ODBC/JDBC一类的（作为world state storage）？ 否则 的话只能通过CLIENT APPLICATION 实现。。。
我了解的是有计划，没行动 :joy:
我觉得这个挺有意义的。有性能、可靠性问题？那是不是可以放一个POOL，把EXTERNAL RDBM 作为 CLONED / VIEW .
我觉得这个挺有意义的。有性能、可靠性问题？
RBDM是什么的缩写呢？
我记得上次看到这个的时候是配置proto格式出错了，要非常仔细地检查才能知道
Has joined the channel.
说的是关系型数据库(RMDB)吧.
哈，是的。我是指RDBMS。关系型数据库。。。输入法拼写错了。
我发现 peer chaincode package，生成的SignedCDS ， 其实不管是否有签名，都不会影响后面的chaincode install. 看install.go 好象也没有validate sign of the package,。也就是说 peer chaincode signpackage 并没有对应的场景。请问大家对这个问题有更多了解吗？ 请指正。谢谢！
也就是说，peer chaincode package 不管是否有 -s -S参数，都可以work..
生成的PACKAGE都可以INSTALL。
Has joined the channel.
这个是个老问题
后来这些问题打算一并在2.0的新 lifeCycle里面跟着新特性一起修掉
@davidkhala 谢谢了。期待2.0...
@davidkhala 不知是是否有对应的FAB？ 具体是什么方案呢？ To validate when install/instantiate? Or just query the sign information?
@davidkhala 不知是是否有对应的FAB in JIRA？ 具体是什么方案呢？ To validate when install/instantiate? Or just query the sign information?
但是，如果这个SIGN POLICY 也是在PACKAGE里，那么，，，不是要求自己证明自己？这可能是个问题啊。
所以，我想对于FABRIC来说，query chaincode 时，是不是，能提供signature history 应该就可以了。
其实， package sign/install/instantiate 都有类似policy 问题。
我以前的理解就是 package sign就是为了解决 谁可以instantiate的问题， 安装时候倒是没什么问题，只有同组织的admin可以装
Package sign 与 instantiate policy 应该是两个事情 吧。（看来这个FEATURE确实不清晰）。 而且 peer chaincode signpackage 时指定的参数 instantiate policy 目前只能用 OR (...) ,不能用 AND (...)。https://jira.hyperledger.org/browse/FAB-6046 也说了这个问题，但没有MERGE。
Package sign 与 instantiate policy 应该是两个事情 吧。（看来这个FEATURE确实不清晰）。 而且 peer chaincode package 时指定的参数 instantiate policy 目前只能用 OR (...) ,不能用 AND (...)。https://jira.hyperledger.org/browse/FAB-6046 也说了这个问题，但没有MERGE。
Has joined the channel.
Has joined the channel.
想请问各位前辈有没有遇到这种状况，orderer使用kafka时，会有一定的机率processMessagesToBlocks不运作，导致channel create有问题，附上issue网址 https://jira.hyperledger.org/browse/FAB-16484
謝謝!!
@all TWGC Chair Board Annual Election is Starting!
https://lists.hyperledger.org/g/twg-china/message/719, welcome to nominate!
看来是历史残留问题了
instantiate policy 本来设计上是用来校验 package sign的（注意我不是说 endorsement policy） 只能OR不能AND，就是这个东西没昨晚的表征了
没做完
evidently zoom is having problems in china
Below is a temporary workaround from Zoom. Otherwise, the issue should be monitored at status.zoom.us and attendees in China can contact Zoom customer support for more assistance at cnsupport@zoomus.zendesk.com.
How users can join a meeting from China :
Zoom Client：
Please access https://zoomcloud.cn/download.html and download the China Zoom client. After installing, users can enter the meeting ID to join a Zoom meeting.
Zoom Web Client:
Users in China can access the Zoom web client at https://www.zoomus.cn/webclient/join. Please enter the meeting ID to join the meeting.
Example URL: http://zoomus.cn/webclient/123456789/join
iOS client:
The steps below work with Chinese as the system language.
1. Switch the system language to Chinese. If it is Chinese already, please ignore this step.
2. Logout of the current Zoom account. If user has not logged in, please ignore this step.
2. Tap the "Sign In" button in the bottom righthand corner, enter an invalid Name and Password (for example "u" and "p"), tap "Sign in".
3. Ignore the error message by tapping "OK" and tap "Cancel" on the left top to return to the home page.
4. Tab "Not now" if a prompt appears asking to save the password.
5. Users can then switch to their preferred system language if this is not Chinese.
6. Tap "Join a Meeting" to enter meeting ID and Display name, and join a Zoom meeting.
Please be noted not to enter invalid credential under other system language.
Below is the Chinese version for Chinese users.
关于中国区用户加会的两个方法
1.通过https://zoomcloud.cn/download.html 下载Zoom客户端,安装后可以输入meeting number 加会。
2. 国内用户可以访问Zoom网页客户端: https://www.zoomus.cn/webclient/join, 并在页面中输入会议号加会。
或者访问： http://zoomus.cn/webclient/123456789/join ，以同样方式加会。
iOS客户端加会方法：
1. 将系统语言切换到中文。如果已经是中文，可以忽略此步骤。
2. 注销已登录的帐号，若没有登录可以省略此步骤。
3. 点击 右下角的 "登录" 按钮，输入任意错误的用户名和密码，然后点击“返回”，回到开始页
4. 此时可以切换到其它系统语言。
5. 点击"加入会议” 按钮，输入会议号和显示的用户名，即可加入Zoom会议
请注意，不要在其它系统语言下尝试输入错误的用户名和密码。
@Silona thank you!
:thumbsup:
Thank you @davidkhala
@here the hyperledger community will migrate from the gerrit CI to the github one. Please pay attention to the latest progress at #cicd channel.
Has joined the channel.
fabric 1.0为什么要将共识和验证分开？
哈哈，虽然这个问题过去了很久，还是要回答一下。不然看着不整齐。
将共识与验证分开，我想这也是Fabric的特殊之处，现在也是的。
一是解耦，方便实现、应用不同的共识算法；
二是使共识成为permissioned；
三是使ordering 与 validating 成为异步过程，这样总体效率更高。
@chenchongswjtu ，不知这样理解对不对？
哈哈，虽然这个问题过去了很久，还是要回答一下。不然看着不整齐。
将共识与验证分开，我想这也是Fabric的特殊之处，现在也是的。
一是解耦，方便实现、应用不同的共识算法；
二是使共识成为permissioned；
三是使ordering 与 validating 成为异步过程，这样总体效率更高。
（其实其他DLT对这两个，在逻辑上也是分开的）
@chenchongswjtu ，不知这样理解对不对？
@guoger 请问下，有了解fabric最新的共识算法和未来预计的共识优化吗？现在目前使用的是v1.4.1开始推出的RAFT共识，感觉比以前快了很多。
看了jira的roadmap好像并没有提及，看样子打算一直以raft为默认的共识策略了
当前以raft为主，会逐渐淡化kafka直到在以后的某个版本中移除。pbft工作正在进行
噢噢。好的。
生产推荐 Raft
Has joined the channel.
TWGC bi-week meeting now started
Has joined the channel.
请问现在fabric支持RSA算法生成的证书么？
@guoger If we were to go straight to a BFT solution, we would have to juggle two
moving parts at the same time: (i) writing the BFT library, and (ii) fixing
the Fabric interfaces that wrap around it. This seemed like an unwise
endeavor.
我在Fabric Proposal_ A Raft-Based Ordering Service.pdf看到这个，也是回答了我之前提出的问题。
Has joined the channel.
源码支持。
我在浙大内网上看到有个据说是国家队的[bns的“区块链服务网络”](https://www.bsnbase.com/)，发现底层好像也只是魔改fabric的 :joy_cat:
然后他们python开发手册上直接使用我们 fabric-sdk-py :joy:
Has joined the channel.
TWGC 双周会议即将开始， https://zoom.us/my/hyperledger.community 或者http://zoomus.cn/webclient/4034983298/join
今天我们邀请到来自consensys的朋友来分享Hyperledger Besu
Howdy! y'alls quarterly report is due https://wiki.hyperledger.org/display/TSC/2019+12+12+TSC+Agenda
Hello everyone -
Do you know of a developer event that we would like to get some Hyperledger representation at?
Please submit it here. The marketing committee will review them all as we go thru our budget for 2020
Thank you! - Silona
https://wiki.hyperledger.org/display/Marketing/Developer+Events
Great post for this year’s Mentorship Program. Thanks Hyperledger community! https://www.hyperledger.org/blog/2019/12/12/2019-summer-mentee-project-update-hyperledger-fabric-sdk-for-node-js-security-extension
请问fabric支持部署在arm64v8上吗？自己make docker总是各种问题
nodejs ec公钥加密，私钥解密有没有大佬知道怎么弄？
Has joined the channel.
Has joined the channel.
Help Us Help you! Attend the Developer Relationship Meeting with Myself and our Marketing Dept. tomorrow at 9:00am Pacific Time.
For the agenda and Dial in info
https://wiki.hyperledger.org/display/Marketing/2020-01-15+Meeting+notes
Calling all Projects, SIG, and WG!!! We will have a Video recording Studio setup at HGF (Hyperledger Global Forum). We are asking that all projects and groups help us create a 5 minute video about your group so that we can promote it afterward. Sign up Here! https://wiki.hyperledger.org/display/HGF/Video+Recording+Schedule
Has joined the channel.
The Linux Foundation’s CommunityBridge engineers are working on a tool to measure the health of critical open source projects and one of the key areas identified is QA Testing. They request that our communities provide honest and detailed information on testing tools and methodologies you use in your projects for us to come up with a detailed analysis, which they will share with all respondents and projects. https://www.surveymonkey.com/r/9H5G2GV. It’s only 5 questions long.
看到印度区有开展黑客松的比赛（ https://wiki.hyperledger.org/display/CP/Hackathon+Feb+2020 ），咱这边是不是也可以举办类似的比赛？
Howdy Contributors and Maintainers! Are you wondering about tapping into Developer marketing for your group or project? Do you have a blog post idea? An awesome announcement? Please attend our Contributor/marketing meeting! https://wiki.hyperledger.org/display/Marketing/2020-02-19+Meeting+notes
Are you wondering about tapping into Developer marketing for your group or project? Do you have a blog post idea? An awesome announcement? Please attend TOMORROW! https://wiki.hyperledger.org/display/Marketing/2020-02-19+Meeting+notes
Has joined the channel.
前两年有过，我们也可以搞的，欢迎参与组织策划
有企业愿意赞助场地就可以。
场地也不用吧，不可以online吗？不过之前我联系过，我学校可以提供场地，但是超级账本也不提供奖金，所以最后没办成
过往的超级账本实习经验分享： https://github.com/gsoc-cn/hyperledger-mentor-program
https://hyperledger-cn.github.io/
cool, and there are lots of interns to present their work today.
Hi all, I'd share you an open source project, Fablet, what is a browser-based dashboard and tools set for Hyperledger Fabric blockchain platform. It's based on Go SDK, for learning purpose, maybe we can get more in this project. Thanks.
The site is: https://github.com/IBM/fablet
我做了一个基于浏览器的Fabric 客户端，基于Go SDK。现在作为开源项目分享给大家。谢谢！
基本出于学习目的，也希望能有更多收获。请多批评指正。
:grinning:
Has joined the channel.
hello?
大陆用户有吗？
我做了一个，可以发出链接吗？我仅仅是寻找技术交流，帮助我改进我做的社区
打开这个网站很慢，用梯子也很慢，我也没时间等了，发一个我使用rocketchat做的（https://0514.chat），我不是来宣传我的网站，我仅仅在寻找认同rocketchat这种在线沟通的用户，帮我提点意见，我好改进我做的社区，如果你们打开也很慢，欢迎你们来我做的讨论，我也不懂你们这个社区讨论的是啥，如有冒犯，深表抱歉
fabric 2.0 orderer 能启动 solo 调试模式吗？
好像1.4.2之后就不支持了，用raft单节点替代
Hi all, I am trying to applying External Chaincode with Fabric 2.0.1, but it seems that the chaincode building flow at all didn't fallback to the external chaincode builder.
1. Fabric is 2.0.1.
2. In core.yaml:
```
chaincode:
externalBuilders:
- name: extGolangBuilder
path: /builders/golang
environmentWhitelist:
- GOPROXY
- GOSUMDB
- GONOSUMDB
- name: noopBuilder
path: /builders/golang
```
3. Tar gz a package with metadata.json, and connection.json.
4. Mount the builder scripts.
```
$ docker exec -it peer0.org1.example.com ls /builders/golang/bin/
build.sh detect.sh release.sh
```
5. Install chaincode always got failed.
```
$ peer lifecycle chaincode install "${PKG}"
Error: chaincode install failed with status: 500 - failed to invoke backing implementation of 'InstallChaincode': could not build chaincode: docker build failed: platform builder failed: Failed to generate a Dockerfile: Unknown chaincodeType: EXTERNAL
```
No error in peer, its output:
```
2020-03-23 09:32:36.398 UTC [endorser] callChaincode -> INFO 04c finished chaincode: _lifecycle duration: 0ms channel= txID=d0bcf453
2020-03-23 09:32:36.398 UTC [comm.grpc.server] 1 -> INFO 04d unary call completed grpc.service=protos.Endorser grpc.method=ProcessProposal grpc.peer_address=172.23.0.1:38656 grpc.code=OK grpc.call_duration=1.389276ms
```
It seems that the flow was not changed to external builder.
Have you experienced this?
Thanks!
Hi all, I am trying to apply External Chaincode with Fabric 2.0.1, but it seems that the chaincode building flow at all didn't fallback to the external chaincode builder.
1. Fabric is 2.0.1.
2. In core.yaml:
```
chaincode:
externalBuilders:
- name: extGolangBuilder
path: /builders/golang
environmentWhitelist:
- GOPROXY
- GOSUMDB
- GONOSUMDB
- name: noopBuilder
path: /builders/golang
```
3. Tar gz a package with metadata.json, and connection.json.
4. Mount the builder scripts.
```
$ docker exec -it peer0.org1.example.com ls /builders/golang/bin/
build.sh detect.sh release.sh
```
5. Install chaincode always got failed.
```
$ peer lifecycle chaincode install "${PKG}"
Error: chaincode install failed with status: 500 - failed to invoke backing implementation of 'InstallChaincode': could not build chaincode: docker build failed: platform builder failed: Failed to generate a Dockerfile: Unknown chaincodeType: EXTERNAL
```
No error in peer, its output:
```
2020-03-23 09:32:36.398 UTC [endorser] callChaincode -> INFO 04c finished chaincode: _lifecycle duration: 0ms channel= txID=d0bcf453
2020-03-23 09:32:36.398 UTC [comm.grpc.server] 1 -> INFO 04d unary call completed grpc.service=protos.Endorser grpc.method=ProcessProposal grpc.peer_address=172.23.0.1:38656 grpc.code=OK grpc.call_duration=1.389276ms
```
It seems that the flow was not changed to external builder.
Have you experienced this?
Thanks!
可能 detect.sh 脚本执行失败，跳过了external builder
我在detect里加了log， 但没有输出。应该是还没有走到detect。
我在detect里加了log， 但没有输出。应该是还没有走到detect。
@guoger could you please help on this? Thanks.
Has joined the channel.
Has joined the channel.
fabric 2.0 执行 peer lifecycle chaincode commit 执行是成功的 可是智能合约却退出了，
查看 peer的日志为：2020-04-10 08:21:12.235 UTC [lifecycle] Work -> WARN 124 could not launch chaincode 'mycc_11:68ab5600bac5c2d3ddbe4269efc37e885ea6f3f3661e4455e6f355b134ed0282': chaincode registration failed: container exited with 0
查看智能合约的日志为：Error starting ABstore chaincode: context deadline exceeded
请问这个什么问题
请问什么时候才能出v.1.4.2到v2.1的升级中文文档呢？https://hyperledger-fabric.readthedocs.io/en/release-1.4/upgrading_your_network_tutorial.html?highlight=upgrade
有尝试升级过的朋友吗？之前v1.3升级v1.4可以直接跑fabric-samples升级，不知道后续fabric-samples有没有继续支持脚本升级到v2.x
https://hyperledger-fabric.readthedocs.io/en/latest/upgrade.html 按照这个做尝试中。。
[ ](https://chat.hyperledger.org/channel/twg-china?msg=dCKKuwgt7AZ665dxS) 目前文档翻译在持续更新中，但是具体时间不好说，因为文档翻译都是社区成员业余时间贡献的。有兴趣的话也欢迎你来贡献这篇文章的翻译。
Has joined the channel.
Has joined the channel.
Has joined the channel.
Howdy - since the Cactus whitepaper has been translated, we (Hyperledger) would like to send a tweet in Chinese. Could someone provide us with the text? @stone-ch ?
Hyperledger Cactus 旨在提供去中心化、安全和通用的区块链网络集成功能。目前中文版白皮书已完成中文翻译，更多内容请查看 https://github.com/hyperledger/cactus/blob/master/whitepaper/whitepaper_zh-CN.md
Hyperledger Cactus aims to provide Decentralized, Secure and Adaptable Integration between Blockchain Networks. Currently the Chinese whitepaper has been translated, more details see https://github.com/hyperledger/cactus/blob/master/whitepaper/whitepaper_zh-CN.md
@rjones This is the Chinese and English text for tweet, is it ok?
Has joined the channel.
Looks good to me
@DavidBoswell ^^^
Has joined the channel.
Hi - I'm working on helping move the zh_CN docs from labs - over in #i18n
Hi @all - I moved over the files. https://github.com/hyperledger/fabric-docs-i18n/tree/master/docs/source/locale/zh_CN there will need to be a PR to straighten up probably
@rjones Hi Ry, does the community have already consent on make the lab project deprecated or archived? In recent TWGC bi-week meeting we are still discussing whether it is easier for volunteers.
@stone-ch 程阳你的意见是？
征求了其他语言翻译者的意见，他们都认为我们目前的这种翻译方式比较合适，就是在原文档上直接翻译，不用Transifex，所以我们的翻译方式没有变化。Ry 新建了一个仓库 https://github.com/hyperledger/fabric-docs-i18n ，所有语言的翻译都在这里。
使用PO/POT文件进行翻译的话，目前没有比较好用的工具进行管理，我给他们提了意见，但是目前所有翻译者都是在原文档进行翻译的，而且这种方式也比较顺手，所以就还按原来的翻译方式
hi，有人遇到过CA证书过期的情况吗？ 2个组织的channel中有一个组织的ca和tlsca过期了怎么办？
可以先将更新后的证书加入到peer的识别目录中，然后对通道配置进行更改
Has joined the channel.
1.4.7 与 2.1.1 之间有什么区别吗，新项目用2.1.1还是1.4.7呢？
Has left the channel.
区别挺大的
个人认为可以上新版本
谢了！
大家好，我问个问题
Clipboard - 2020年7月2日上午11点20分
基于fabric1.4.7的raft共识算法部署的网络，账本数据可以同步，但是peer节点报错，tls握手失败
Clipboard - 2020年7月2日上午11点22分
没弄明白啥原因造成的。
@baohua :pray:
Has joined the channel.
大概率证书问题，其中包括CA版本问题
Hyperledger Fabric v2.2 LTS RELEASE ANNOUNCEMENT:
https://lists.hyperledger.org/g/fabric/message/8643
Has joined the channel.
想知道fabric支持从channel中动态退出一个节点的功能吗
直接停掉就好了
得从创世块里去掉相关的信息吧
如果是系统通道里面写了的Consortium组织那还比较麻烦
Has joined the channel.
fabric-go-sdk 调用 fabric 2.2 出现
```
{"code":500,"msg":"fail","data":"Event Server Status Code: (10) ENDORSEMENT_POLICY_FAILURE. Description: received invalid transaction"}
```
是哪里的背书策略出问题了，cli调用完全正确阿。
你研究下 错误代码？
如果cli是只管发不管监听也检测不到这里
Has joined the channel.
Welcome
Clipboard - 2020年8月21日上午10点59分
请问上面的库 fabric@2.0版本在哪里可以找到？
https://pkg.go.dev/github.com/hyperledger/fabric-chaincode-go/pkg/statebased?tab=doc
https://pkg.go.dev/github.com/hyperledger/fabric-chaincode-go/pkg/statebased?tab=doc
fabric-chaincode-go里面了
Has joined the channel.
https://lfanalytics.io/projects/hyperledger%2Fhyperledger-twgc/dashboard
If you could log in and check if your email address is up-to-date, that would be awesome: https://myprofile.linuxfoundation.org/
My email on Profile page is correct.
@rjones Hi Ry, the rocketchat bot tell me I am not allowed to "AT all" in this TWGC channel. Could you help?
I found Matthew Sykes is also counted as TWGC contributor. Em, is there a mistake？
Everyone with commits in Fabric is
davidkhala
Everyone with commits in Fabric is
Has joined the channel.
前段时间看到一条消息关于hyperledger fabric国密化改造的，请问大家知道最新的进展吗？
@Flyyellow 在缓慢地推进当中，可以关注这里 https://github.com/Hyperledger-TWGC/fabric-gm-wiki/wiki
有人知道怎样通过环境变量传递一个人数组到Peer吗？ 比如值： CORE_CHAINCODE_EXTERNALBUILDERS
TSC 选举正在进行中，请大家关注 https://wiki.hyperledger.org/display/TSC/TSC+Election+2020-2021。
Has joined the channel.
一个人数组是什么？数组的话一般就是```[a,b]```的形式
fabric考虑支持unjoin channel这个功能吗
我看下了代码，现在的实现方式，底层leveldb数据存储的key值是channelname+chaincodeKey组合而成的，很难剥离删除
这块fabric有什么考虑不
有在做的，具体可以看 https://github.com/hyperledger/fabric-rfcs/pull/24
hello?
恭喜保华当选新一届TSC委员！
Has joined the channel.
大家好，我是个执业律师，编程爱好者，希望能将自然语言合约通过智能合约转移到Fabric平台上。目前在研究国密改造，申请加入组织！:blush: :pray:
@paul-lee-attorney Paul你好，欢迎来到TWGC
你可以将你的github id发到我邮箱david-khala@hotmail.com么？我可以邀请你进Hyperledger-TWGC这个Github org
Has joined the channel.
老大哥们，大家好，我是一名fabric初学者，买了区块链原理、设计与应用第2版，有些问题想来求助一下
大佬们，请问一下，利用docker-compose-files里面的HLF_MOD=raft make start，随后的生成创世区块，通道，锚节点一类的都是需要make cil进入docker操作吗
我创建通道的时候为什么提示这个不存在呢，分明路径没错啊Cannot run peer because cannot init crypto, folder "/src/github.com/hyperledger/my-syxt/v2.0.0/crypto-config/peerOrganizations/org1.example.com/users/Admin@org1.example.com/msp" does not exist
大佬们还有个问题
Clipboard - 2020年11月15日晚上9点49分
ca配置里面这个文件名称在哪找到的
我这边自动生成的就叫priv_sk
这个可以在启动了的docker container里边找到
你的这个路径是绝对路径，从根目录开始的，再确认一下路径吧
@Steiner 1 国内的开发者主要在微信群里边讨论的比较多，加我微信 15600298825 我拉你进群。
@Steiner 1 国内的开发者主要在微信群里边讨论的比较多，加我微信我拉你进群。
微信号 yycheng418
wechat.jpg
Has joined the channel.
大家好，有个问题想请教一下，就是ca颁发的证书有效期是一年。如果到期了怎么办？
可以reenroll，有效期在生成的时候也可以设置
那reenroll之后的证书 要怎么在集群中使用呢
替换掉旧证书就可以用了啊
不用更改配置区块什么的吗
好的 那我试一下
我这个替换证书了 不行啊
@stone-ch
报错Error: transaction invalidated with status (ENDORSEMENT_POLICY_FAILURE)
Has joined the channel.
[ ](https://chat.hyperledger.org/channel/twg-china?msg=BCc8C3qjLsFn2kF4s) 加我微信，拉你进微信群
[ ](https://chat.hyperledger.org/channel/twg-china?msg=f3hpHReAA34npueES) @zhangshuai
Has joined the channel.
Hi! Every week, we publish a newsletter about Hyperledger for developers. If you have items to add: https://wiki.hyperledger.org/pages/viewpage.action?pageId=39618905 adding them in Chinese is totally fine, just add a comment to the next newsletter.
@rjones Thanks Ry, I missed it for a while. I just comment on the Feb 5 page
Has joined the channel.
:woo:
hi,bro.i have a question.how changing ubuntu profile path ,vi ~/.profile is no use
it might be in `.bashrc` if `bash` is your shell
thank u sir
Has joined the channel.
hello. I am facing difficulty when I try set up hyper ledger in VS code.
Has joined the channel.
Has joined the channel.
Has joined the channel.
Has joined the channel.
Has joined the channel.
this chat has moved to discord https://discord.gg/hyperledger
![AY{E%A%GJS]][NI@6)3M{_9.png](./assets/eiqhJ5DA2q9tSh8Wm-AY{E%A%GJS]][NI@6)3M{_9.png){kind=link}
