Ok impressive paper, but could someone ELI5 on how DragonFly/Infoteria partnership utilizes NEM?
afaik mijin is private NEM chain what DF uses. API is 100% same and there can be cross chains
directly to NEM or you can use NEM directly.
Topic: NEM (XEM) Official Thread - 100% New Code - Easy To Use APIs - page 838. (Read 2985369 times)
Ok impressive paper, but could someone ELI5 on how DragonFly/Infoteria partnership utilizes NEM?
afaik mijin is private NEM chain what DF uses. API is 100% same and there can be cross chains
directly to NEM or you can use NEM directly.
Ok impressive paper, but could someone ELI5 on how DragonFly/Infoteria partnership utilizes NEM?
Okay……. Looks like something is happening. Can anybody read Japanese? https://www.infoteria.com/jp/news/press/2016/04/18_01.php 
http://www.dfintech.com/static/teps.pdf
http://japan.cnet.com/release/30140934/
https://translate.google.com.au/translate?sl=auto&tl=en&js=y&prev=_t&hl=en&ie=UTF-8&u=http%3A%2F%2Fjapan.cnet.com%2Frelease%2F30140934%2F&edit-text=
Infoteria Co., Ltd. (Headquarters: Shinagawa-ku, Tokyo, President: Yoichiro Hirano, Securities Code: 3853, below, Infoteria) is, FinTech headquartered in Singapore company Dragonfly Fintech Pte Ltd (read: Dragon Fly FinTech, headquarters : Singapore, CEO: Lon Wong, below, and Dragonfly), and announced that it has agreed to a business tie-up to strengthen the payment solutions in the financial services industry.
Infoteria Co., Ltd. (Headquarters: Shinagawa-ku, Tokyo, President: Yoichiro Hirano, Securities Code: 3853, below, Infoteria) is, FinTech headquartered in Singapore company Dragonfly Fintech Pte Ltd (read: Dragon Fly FinTech, headquarters : Singapore, CEO: Lon Wong, below, and Dragonfly), and announced that it has agreed to a business tie-up to strengthen the payment solutions in the financial services industry.
Okay……. Looks like something is happening. Can anybody read Japanese? https://www.infoteria.com/jp/news/press/2016/04/18_01.php
http://www.dfintech.com/static/teps.pdf
Okay……. Looks like something is happening. Can anybody read Japanese?
Edit: http://japan.cnet.com/release/30140934/
Edit: http://japan.cnet.com/release/30140934/
not released yet....
I'm speculating here ok:
1) Zaif adding XEM as the 3rd coin into their exchange( BTC / Mona and now XEM ?)
2) DF announcing a joint venture with? Mijin / TB ?
3) DF secured funding from an Angel Investor?
4) XEM secured a funding from an Angel Investor?
5) XEM will finally release the mobile wallets? or announce a date for it to be released? which supports multiple languages etc?
I don't know...so hard to guess..it could be anything.... all I know this coin is under the radar... accumulate moarrrrrrrrrr!!!!
I'm speculating here ok:
1) Zaif adding XEM as the 3rd coin into their exchange( BTC / Mona and now XEM ?)
2) DF announcing a joint venture with? Mijin / TB ?
3) DF secured funding from an Angel Investor?
4) XEM secured a funding from an Angel Investor?
5) XEM will finally release the mobile wallets? or announce a date for it to be released? which supports multiple languages etc?
I don't know...so hard to guess..it could be anything....
all I know this coin is under the radar... accumulate moarrrrrrrrrr!!!!
What's the announcement?
if you go to your account dash board, click the settings cog next to your account address on the left. then go view account details > show remote accounts private key.
to find the config file you need to edit go to c:\
edit the following:
#nis.bootKey = #0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef
#nis.bootName = foobar
remove the #'s, all 3.
change the bootkey shown to the private key for your delegated account and change the bootname to anything you want(bootname shows public just so you know)
then:
set "nis.shouldAutoHarvestOnBoot = false" to true.
Hello.
I have a question regarding last auto harvest option.
I use a bash script that was written by Rigel on my vps to start stop the nis and run it as a service.
In that script there is a curl call to "harvest.sh" script to start the harvesting on boot.
Is this call to harvest.sh still needed when there is an
nis.shouldAutoHarvestOnBoot option in the nis config file
or this bash script should be modified to avoid the call to
"harvest.sh" ?
Also is there an updated version of that bash script somwehre in our forum?
Can somebody point me to it bacuse it seems I can't find that bash script on the forum any more! :-/
Thanks.
Japan overtake China in Crypto? Then like Nintendo go international? Time to buy and HODl XEM. 
we really need to get on there!
When NEM gets on zaif we'll see a big bump in price like we did when people could buy NEM with CNY. I bet my money on it.
Zaif=bump is practically a sure thing, but I am holding out for the big time. The traders will only take your XEM if you sell.
With our steady growth, it continuously gets more costly to accumulate. Hodl, the real boom is coming.
ZAIF SEES SIGNIFICANT BITCOIN VOLUME BOOST. Article from Merkle http://themerkle.com/japanese-bitcoin-exchange-zaif-noted-record-trading-volume-last-week/
we really need to get on there!
When NEM gets on zaif we'll see a big bump in price like we did when people could buy NEM with CNY. I bet my money on it.
Zaif=bump is practically a sure thing, but I am holding out for the big time. The traders will only take your XEM if you sell.
With our steady growth, it continuously gets more costly to accumulate. Hodl, the real boom is coming.
an important milestone has been reached by Dragonfly......announcement impending...should be tomorrow Rock on NEM... !!!!!!! an important milestone has been reached by Dragonfly......announcement impending...should be tomorrow Rock on NEM... !!!!!!! we really need to get on there!
When NEM gets on zaif we'll see a big bump in price like we did when people could buy NEM with CNY. I bet my money on it.
I am wondering if there is a faucet available? In the opening post is a link to faucet.nem.io but the site does not open and it seems the url is outdated. Is there a other XEM faucet available somewhere?
Ah I understand. The Delegated transaction I made from the account is not known yet to my NIS, because it's not fully synced indeed.
Yes, your chain can't see that transaction yet because it hasn't been synced to that block.
After I changed that NIS doesn't start well; end of logs;
2016-04-17 08:20:26.931 INFO loadBlocks (from height 516902 to height 517001) needed 0ms (org.nem.nis.dao.BlockDaoImpl d)
2016-04-17 08:20:26.946 INFO loadBlocks (from height 516968 to height 517067) needed 0ms (org.nem.nis.dao.BlockDaoImpl d)
2016-04-17 08:20:27.181 INFO clustering completed: { clusters: 3 (average size: 14.33), hubs: 1, outliers: 1433 } (org.nem.nis.pox.poi.PoiContext$AccountProcessor dd)
2016-04-17 08:20:27.321 INFO Iterations required: 21; converged?: true (org.nem.nis.cx.na.xgf run)
2016-04-17 08:20:27.321 INFO POI iterator needed 62ms. (org.nem.nis.pox.poi.PoiImportanceCalculator c)
2016-04-17 08:20:27.337 INFO block loading completed; height 516967 (org.nem.nis.service.BlockChainLastBlockLayer dX)
2016-04-17 08:20:27.400 WARNING auto-booting
2016-04-17 08:20:27.446 INFO calculating trust values (org.nem.peer.trust.CachedTrustProvider a)
2016-04-17 08:20:27.462 INFO trust calculation finished (13 values) (org.nem.peer.trust.CachedTrustProvider a)
2016-04-17 08:20:27.634 INFO updating local node endpoint from
2016-04-17 08:20:27.681 INFO auto harvesting with '
2016-04-17 08:20:27.681 SEVERE something really bad happened: java.util.concurrent.CompletionException: java.lang.IllegalStateException: FAILURE_UNKNOWN_ACCOUNT (org.nem.nis.NisMain b)
You're trying to harvest with an account that isn't known to the network probably because you haven't snyced yet.
Turn autoharvest off again.
Restart NIS and let it sync.
Then turn autoharvest on again and restart NIS.
Ah I understand. The Delegated transaction I made from the account is not known yet to my NIS, because it's not fully synced indeed.
After I changed that NIS doesn't start well; end of logs;
2016-04-17 08:20:26.931 INFO loadBlocks (from height 516902 to height 517001) needed 0ms (org.nem.nis.dao.BlockDaoImpl d)
2016-04-17 08:20:26.946 INFO loadBlocks (from height 516968 to height 517067) needed 0ms (org.nem.nis.dao.BlockDaoImpl d)
2016-04-17 08:20:27.181 INFO clustering completed: { clusters: 3 (average size: 14.33), hubs: 1, outliers: 1433 } (org.nem.nis.pox.poi.PoiContext$AccountProcessor dd)
2016-04-17 08:20:27.321 INFO Iterations required: 21; converged?: true (org.nem.nis.cx.na.xgf run)
2016-04-17 08:20:27.321 INFO POI iterator needed 62ms. (org.nem.nis.pox.poi.PoiImportanceCalculator c)
2016-04-17 08:20:27.337 INFO block loading completed; height 516967 (org.nem.nis.service.BlockChainLastBlockLayer dX)
2016-04-17 08:20:27.400 WARNING auto-booting
2016-04-17 08:20:27.446 INFO calculating trust values (org.nem.peer.trust.CachedTrustProvider a)
2016-04-17 08:20:27.462 INFO trust calculation finished (13 values) (org.nem.peer.trust.CachedTrustProvider a)
2016-04-17 08:20:27.634 INFO updating local node endpoint from
2016-04-17 08:20:27.681 INFO auto harvesting with '
2016-04-17 08:20:27.681 SEVERE something really bad happened: java.util.concurrent.CompletionException: java.lang.IllegalStateException: FAILURE_UNKNOWN_ACCOUNT (org.nem.nis.NisMain b)
You're trying to harvest with an account that isn't known to the network probably because you haven't snyced yet.
Turn autoharvest off again.
Restart NIS and let it sync.
Then turn autoharvest on again and restart NIS.
okay so i was finally able to start delegated harvesting by changing the remote server host in the settings.
i got some more questions. in the auto-boot what node name do i put? also, how can i do local harvesting while doing delegated harvesting? thanks all
i got some more questions. in the auto-boot what node name do i put? also, how can i do local harvesting while doing delegated harvesting? thanks all
you can put any name you like. im not sure if you can activate delegated harvesting in the GUI and then start local harvesting, but what you can do is activate delegated harvesting, and then get the delegated key and set its private key as the boot key for your local nis in the config files and set autostart harvesting to true.(<- not sure of the exact name of the config property for that). that way it should start harvesting as soon as nis is up and running using your delegated account.
thanks. where can i find the delegated key? and where do i set its private key for my local nis? can you please give me a link to a tutorial for this? thanks again
if you go to your account dash board, click the settings cog next to your account address on the left. then go view account details > show remote accounts private key.
to find the config file you need to edit go to c:\
edit the following:
#nis.bootKey = #0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef
#nis.bootName = foobar
remove the #'s, all 3.
change the bootkey shown to the private key for your delegated account and change the bootname to anything you want(bootname shows public just so you know)
then:
set "nis.shouldAutoHarvestOnBoot = false" to true.
After I changed that NIS doesn't start well; end of logs;
2016-04-17 08:20:26.931 INFO loadBlocks (from height 516902 to height 517001) needed 0ms (org.nem.nis.dao.BlockDaoImpl d)
2016-04-17 08:20:26.946 INFO loadBlocks (from height 516968 to height 517067) needed 0ms (org.nem.nis.dao.BlockDaoImpl d)
2016-04-17 08:20:27.181 INFO clustering completed: { clusters: 3 (average size: 14.33), hubs: 1, outliers: 1433 } (org.nem.nis.pox.poi.PoiContext$AccountProcessor dd)
2016-04-17 08:20:27.321 INFO Iterations required: 21; converged?: true (org.nem.nis.cx.na.xgf run)
2016-04-17 08:20:27.321 INFO POI iterator needed 62ms. (org.nem.nis.pox.poi.PoiImportanceCalculator c)
2016-04-17 08:20:27.337 INFO block loading completed; height 516967 (org.nem.nis.service.BlockChainLastBlockLayer dX)
2016-04-17 08:20:27.400 WARNING auto-booting
2016-04-17 08:20:27.446 INFO calculating trust values (org.nem.peer.trust.CachedTrustProvider a)
2016-04-17 08:20:27.462 INFO trust calculation finished (13 values) (org.nem.peer.trust.CachedTrustProvider a)
2016-04-17 08:20:27.634 INFO updating local node endpoint from
2016-04-17 08:20:27.681 INFO auto harvesting with '
2016-04-17 08:20:27.681 SEVERE something really bad happened: java.util.concurrent.CompletionException: java.lang.IllegalStateException: FAILURE_UNKNOWN_ACCOUNT (org.nem.nis.NisMain b)
Jump to: