Author

Topic: [ANN][LSK] Lisk | Blockchain Application Platform for JavaScript Developers - page 1013. (Read 3074324 times)

full member
Activity: 126
Merit: 100

Andreas Antonopoulos could be the new Lisk Advisor



Call him to the interview. Wink

For the skeptics: https://twitter.com/aantonop/status/734837846578761730

Andreas Antonopoulos is an awesome guy... it will be huge for Lisk if he's an advisor

Just for the record, the BTCs in the chart are worth more than $ 8 million at the moment.

Billion.
And this is only the beginning for bitcoin too

I'm not referring to BTC marketcap, but to ICO funds.
full member
Activity: 196
Merit: 100
full member
Activity: 196
Merit: 100

Why SideChains make Lisk More Scalable Than Ethereum (Interview with Lisk Co-Founder)


Amazing interview!
GO LSK GO!!!

Thanks for sharing, this cleared lot of my questions about Lisk.


Lisk has huge potential indeed. I'll be watching the development closely.

Lot of Lisk interest in Devs community lately.

There's still almost no press or media coverage on Lisk

I wonder where Lisk will be if they actually start covering it like Ethereum or even just 1/10 of that kind of coverage.


The media circus is about to begin now that Devs have access to that $8 million USD of ICO funding.


This week is going to be huge for Lisk


I feel sorry for the people who sold Lisk to chase other ICOs...


Yeah, this week is going to be huge for Lisk.
full member
Activity: 210
Merit: 100
DASH is now in Lisk's rear view mirror.



The pedal is to the metal.  Watch out, DAO, here we come...



New proposal idea for the DAO:

Release a big chunk of ETH to a contractor who sells the ETH then buys/holds LSK.

Contractor can use the LSK to get a top 101 delegate position.

The income from the LSK delegate can be converted back to ETH then sent back to the DAO as interest on their investment.

+++ so good

Go for it!

I'll vote YES for this proposal.
full member
Activity: 560
Merit: 101
When will delegates be earning lisk with forging?
newbie
Activity: 43
Merit: 0

Andreas Antonopoulos could be the new Lisk Advisor

https://i.imgur.com/b6WCD3S.png

Call him to the interview. Wink

For the skeptics: https://twitter.com/aantonop/status/734837846578761730

Andreas Antonopoulos is an awesome guy... it will be huge for Lisk if he's an advisor

Just for the record, the BTCs in the chart are worth more than $ 8 million at the moment.

Billion.
And this is only the beginning for bitcoin too
hero member
Activity: 1134
Merit: 501
I think Lisk it will be good on long term better than waves! So keep your coin! Lisk team  are more great!
Just have faith and dont sell your lisk coin!
legendary
Activity: 1025
Merit: 1000
DASH is now in Lisk's rear view mirror.

The pedal is to the metal.  Watch out, DAO, here we come...



New proposal idea for the DAO:

Release a big chunk of ETH to a contractor who sells the ETH then buys/holds LSK.

Contractor can use the LSK to get a top 101 delegate position.

The income from the LSK delegate can be converted back to ETH then sent back to the DAO as interest on their investment.

That is insane. You think it will go? If it pans out the coins will be join together in value

All coins join together, it will become 'too big to fail' situation. DAO is already convoluted, now add Lisk, and Lisk's own DAO that hedges in other coins. This kind of thing could get crazy fast.
full member
Activity: 126
Merit: 100

Andreas Antonopoulos could be the new Lisk Advisor



Call him to the interview. Wink

For the skeptics: https://twitter.com/aantonop/status/734837846578761730

Andreas Antonopoulos is an awesome guy... it will be huge for Lisk if he's an advisor

Just for the record, the BTCs in the chart are worth more than $ 8 million at the moment.
sr. member
Activity: 616
Merit: 250
m33
legendary
Activity: 1064
Merit: 1000
Never invest with borrowed coins
DASH is now in Lisk's rear view mirror.



The pedal is to the metal.  Watch out, DAO, here we come...



New proposal idea for the DAO:

Release a big chunk of ETH to a contractor who sells the ETH then buys/holds LSK.

Contractor can use the LSK to get a top 101 delegate position.

The income from the LSK delegate can be converted back to ETH then sent back to the DAO as interest on their investment.

That is insane. You think it will go? If it pans out the coins will be join together in value
legendary
Activity: 1120
Merit: 1000

Crypti raised 750 BTC and has a current market cap of 1153 BTC. Smiley

Can confirm this as I was a part of that ICO as well!

Glad I made it in time for the first day bonuses, looking forward for the future that awaits this idea! Smiley

Omg I just stumbled on proof I invested in the first day. Now I can sleep happy. :3

Everything looks nice here Smiley Lisk is a clone of Crypti and Rise and DL(i)sk are clones of Lisk. So all coins are basically crypti coins Cheesy If all of them do the same as crypti then i don't complain Cheesy
sr. member
Activity: 356
Merit: 250

Crypti raised 750 BTC and has a current market cap of 1153 BTC. Smiley

Can confirm this as I was a part of that ICO as well!

Glad I made it in time for the first day bonuses, looking forward for the future that awaits this idea! Smiley

Omg I just stumbled on proof I invested in the first day. Now I can sleep happy. :3
legendary
Activity: 910
Merit: 1000
Hi, at end i received my newsletter bounty, but there are a problem, they have paid me only two weeks, 96.26 LISK but i subscribed to newsletter before 15 of march, in fact  i started to received the newsletter at 15 of march, it is more than 5 weeks old, which who can i speak about it to try to fix?


pray?

But they only have to check my subscription date, i dont think it is so difficulty, i only want the bounties are fairly distributed, so can some dev help me please?, i tried to use the chat but no ones replies and no one speaks, i only need to know an email or contact for support

the problems is how long they are interested about support after dumping ICO.
when all is dumped, then coin waits for takeover.
legendary
Activity: 966
Merit: 1000
Hi, at end i received my newsletter bounty, but there are a problem, they have paid me only two weeks, 96.26 LISK but i subscribed to newsletter before 15 of march, in fact  i started to received the newsletter at 15 of march, it is more than 5 weeks old, which who can i speak about it to try to fix?


pray?

But they only have to check my subscription date, i dont think it is so difficulty, i only want the bounties are fairly distributed, so can some dev help me please?, i tried to use the chat but no ones replies and no one speaks, i only need to know an email or contact for support
full member
Activity: 210
Merit: 100

Andreas Antonopoulos could be the new Lisk Advisor



Call him to the interview. Wink

For the skeptics: https://twitter.com/aantonop/status/734837846578761730

Andreas Antonopoulos is an awesome guy... it will be huge for Lisk if he's an advisor
legendary
Activity: 966
Merit: 1000
Hi, at end i received my newsletter bounty, but there are a problem, they have paid me only two weeks, 96.26 LISK but i subscribed to newsletter before 15 of march, in fact  i started to received the newsletter at 15 of march, it is more than 5 weeks old, which who can i speak about it to try to fix?
legendary
Activity: 910
Merit: 1000
Dear Developers!

Client crashes after loading,
WHAT IS GOING WRONG?:

==============================

debian:~$ bash ~/lisk-main/lisk.sh status
√ Lisk is running (as process 13560).

debian:~$ bash ~/lisk-main/lisk.sh logs
  
info 2016-06-05 20:29:33 Blocks 92479
warn 2016-06-05 20:29:33 Detected missed blocks in mem_accounts
warn 2016-06-05 20:29:33 Recreating memory tables
NOTICE:  relation "mem_accounts" already exists, skipping
NOTICE:  relation "mem_round" already exists, skipping
NOTICE:  relation "mem_accounts2delegates" already exists, skipping
NOTICE:  relation "mem_accounts2u_delegates" already exists, skipping
NOTICE:  relation "mem_accounts2multisignatures" already exists, skipping
NOTICE:  relation "mem_accounts2u_multisignatures" already exists, skipping
info 2016-06-05 20:30:04 Rebuilding blockchain, current block height: 0
info 2016-06-05 20:35:17 Rebuilding blockchain, current block height: 5000
info 2016-06-05 20:38:00 Rebuilding blockchain, current block height: 10000
info 2016-06-05 20:40:15 Rebuilding blockchain, current block height: 15000
info 2016-06-05 20:42:12 Rebuilding blockchain, current block height: 20000
error 2016-06-05 20:42:21 { message: 'Maximum number of 101 votes exceeded (2 too many).',
  transaction:
   { id: '5524930565698900323',
     height: 20407,
     blockId: '16820105418178921867',
     type: 3,
     timestamp: 238365,
     senderPublicKey: 'd09b5883f98350934345932d2e030e8478d2dba2985deaef85222cbc315d6421',
     requesterPublicKey: null,
     senderId: '6272272422739160383L',
     recipientId: '6272272422739160383L',
     amount: 0,
     fee: 100000000,
     signature: '18be11b3d5ce002b1f7866b01a87f02fb36ec9a95bf6eb53245b3fddee957c2e1f7618415e2ad02 316c61c420bc9be7e3649104caa43d03579d3cbeba161430e',
     signSignature: 'bbfc43aa7fe7def729f4f73f3547f6e57a7a4776fc5a95169b309c5eb5f066e23c87017a12f095c e40c49d848ac1ff210a3c0383a6cf8c7df5f16302d6aa3107',
     signatures: null,
     confirmations: NaN,
     asset: { votes: [Object] } },
  block:
   { id: '16820105418178921867',
     version: 0,
     timestamp: 238370,
     height: 20407,
     previousBlock: '4143114733638054568',
     numberOfTransactions: 2,
     totalAmount: 0,
     totalFee: 200000000,
     reward: 0,
     payloadLength: 3872,
     payloadHash: '3775d35d05c4c05b7d5063527e90e225d50c821ebd2b892787b75faa0b1cc110',
     generatorPublicKey: '2f872264534a1722e136bddf29a301fa97708f88583130770d54c1d11366e5fc',
     generatorId: '9926064757911337096L',
     blockSignature: 'a1c22b553e495228ec43ee24b450d74c6512064fea5fdcd794cfa33ea8596f053aeb9aa175d9b7a 7a8f82e85443d71e5da064733b099a6dfc77c6e48a8b03409',
     confirmations: NaN,
     totalForged: '200000000',
     transactions: [ [Object], [Object] ] } }
fatal 2016-06-05 20:42:21 System error { message: 'undefined is not a function',
  stack: 'TypeError: undefined is not a function\n    at /home/serg/lisk-main/app.js:3:9842\n    at /home/serg/lisk-main/node_modules/async/lib/async.js:52:16\n    at Immediate. (/home/serg/lisk-main/node_modules/async/lib/async.js:264:21)\n    at Immediate. (/home/serg/lisk-main/node_modules/async/lib/async.js:44:16)\n    at Immediate.immediate._onImmediate (timers.js:418:16)\n    at processImmediate [as _immediateCallback] (timers.js:367:17)' }
info 2016-06-05 20:42:21 Cleaning up...
info 2016-06-05 20:42:21 Cleaned up successfully
error 2016-06-05 20:42:21 null
error: Forever detected script exited with code: 1

Please login to Lisk.Chat in order to receive assistance from the Lisk team (#lisk-support) or the community (#community-support)

why?
coin is out and good as it will ever be.
hero member
Activity: 504
Merit: 500
Communications Lead
Dear Developers!

Client crashes after loading,
WHAT IS GOING WRONG?:

==============================

debian:~$ bash ~/lisk-main/lisk.sh status
√ Lisk is running (as process 13560).

debian:~$ bash ~/lisk-main/lisk.sh logs
  
info 2016-06-05 20:29:33 Blocks 92479
warn 2016-06-05 20:29:33 Detected missed blocks in mem_accounts
warn 2016-06-05 20:29:33 Recreating memory tables
NOTICE:  relation "mem_accounts" already exists, skipping
NOTICE:  relation "mem_round" already exists, skipping
NOTICE:  relation "mem_accounts2delegates" already exists, skipping
NOTICE:  relation "mem_accounts2u_delegates" already exists, skipping
NOTICE:  relation "mem_accounts2multisignatures" already exists, skipping
NOTICE:  relation "mem_accounts2u_multisignatures" already exists, skipping
info 2016-06-05 20:30:04 Rebuilding blockchain, current block height: 0
info 2016-06-05 20:35:17 Rebuilding blockchain, current block height: 5000
info 2016-06-05 20:38:00 Rebuilding blockchain, current block height: 10000
info 2016-06-05 20:40:15 Rebuilding blockchain, current block height: 15000
info 2016-06-05 20:42:12 Rebuilding blockchain, current block height: 20000
error 2016-06-05 20:42:21 { message: 'Maximum number of 101 votes exceeded (2 too many).',
  transaction:
   { id: '5524930565698900323',
     height: 20407,
     blockId: '16820105418178921867',
     type: 3,
     timestamp: 238365,
     senderPublicKey: 'd09b5883f98350934345932d2e030e8478d2dba2985deaef85222cbc315d6421',
     requesterPublicKey: null,
     senderId: '6272272422739160383L',
     recipientId: '6272272422739160383L',
     amount: 0,
     fee: 100000000,
     signature: '18be11b3d5ce002b1f7866b01a87f02fb36ec9a95bf6eb53245b3fddee957c2e1f7618415e2ad02 316c61c420bc9be7e3649104caa43d03579d3cbeba161430e',
     signSignature: 'bbfc43aa7fe7def729f4f73f3547f6e57a7a4776fc5a95169b309c5eb5f066e23c87017a12f095c e40c49d848ac1ff210a3c0383a6cf8c7df5f16302d6aa3107',
     signatures: null,
     confirmations: NaN,
     asset: { votes: [Object] } },
  block:
   { id: '16820105418178921867',
     version: 0,
     timestamp: 238370,
     height: 20407,
     previousBlock: '4143114733638054568',
     numberOfTransactions: 2,
     totalAmount: 0,
     totalFee: 200000000,
     reward: 0,
     payloadLength: 3872,
     payloadHash: '3775d35d05c4c05b7d5063527e90e225d50c821ebd2b892787b75faa0b1cc110',
     generatorPublicKey: '2f872264534a1722e136bddf29a301fa97708f88583130770d54c1d11366e5fc',
     generatorId: '9926064757911337096L',
     blockSignature: 'a1c22b553e495228ec43ee24b450d74c6512064fea5fdcd794cfa33ea8596f053aeb9aa175d9b7a 7a8f82e85443d71e5da064733b099a6dfc77c6e48a8b03409',
     confirmations: NaN,
     totalForged: '200000000',
     transactions: [ [Object], [Object] ] } }
fatal 2016-06-05 20:42:21 System error { message: 'undefined is not a function',
  stack: 'TypeError: undefined is not a function\n    at /home/serg/lisk-main/app.js:3:9842\n    at /home/serg/lisk-main/node_modules/async/lib/async.js:52:16\n    at Immediate. (/home/serg/lisk-main/node_modules/async/lib/async.js:264:21)\n    at Immediate. (/home/serg/lisk-main/node_modules/async/lib/async.js:44:16)\n    at Immediate.immediate._onImmediate (timers.js:418:16)\n    at processImmediate [as _immediateCallback] (timers.js:367:17)' }
info 2016-06-05 20:42:21 Cleaning up...
info 2016-06-05 20:42:21 Cleaned up successfully
error 2016-06-05 20:42:21 null
error: Forever detected script exited with code: 1

Please login to Lisk.Chat in order to receive assistance from the Lisk team (#lisk-support) or the community (#community-support)
Jump to: