FlyingMongoose
|
|
November 06, 2014, 04:20:27 AM |
|
The premine is only a couple thousand bucks worth at todays prices anyway. BK has bought tons more since then, so it doesn't really matter. I wouldn't be surprised if he's the biggest holder by far at this point, as he's often announced his purchases publicly.
And also remember all the money he spent to keep the blockchain alive (DigiSheild issue) by renting rigs. So premine is definitely not a big issue like the other 2 gents before me said. But there is one thing that bothers me ... why are we still talking about transitioning from PoW to PoS. Why can't we just implement dynamic PoS on a new blockchain/coin and simply swap out ? BK apparently has done branding and trademark stuff. Otherwise a graph with his lawyer wouldn't have been necessary when I asked to use the spiral logo for nautijobs. There's apparently a lot invested into this coin and its brand.
|
qoinpro.com/951c974b34f66cc68e805832df0c9d8c
|
|
|
newra
|
|
November 06, 2014, 04:39:06 AM |
|
The premine is only a couple thousand bucks worth at todays prices anyway. BK has bought tons more since then, so it doesn't really matter. I wouldn't be surprised if he's the biggest holder by far at this point, as he's often announced his purchases publicly.
And also remember all the money he spent to keep the blockchain alive (DigiSheild issue) by renting rigs. So premine is definitely not a big issue like the other 2 gents before me said. But there is one thing that bothers me ... why are we still talking about transitioning from PoW to PoS. Why can't we just implement dynamic PoS on a new blockchain/coin and simply swap out ? BK apparently has done branding and trademark stuff. Otherwise a graph with his lawyer wouldn't have been necessary when I asked to use the spiral logo for nautijobs. There's apparently a lot invested into this coin and its brand. Oh sorry I wasn't implying any branding changes. It would still be the same coin, just a different approach to getting to Dynamic PoS (a much cleaner way of getting there)
|
|
|
|
Lord Of The Internet
|
|
November 06, 2014, 04:59:41 AM Last edit: November 06, 2014, 06:38:36 AM by Lord Of The Internet |
|
Like i said before, the network hashrate here is somewhere around 50mh. I personally own over 500mh of scrypt asics.
Before seeing jyap post, I was very much tempted to fork nautilus on my own, implement POS, and then hand it back to him. I'd be willing to bet i could get this done before december ... all on my own.
BK: You need to come in here and update us or i will be more and more tempted to take your coin, fix it for you, and then dump the hell out of it. Believe me when i say that I would be taking a large bounty for myself if i feel forced to fix this shit for you.
EDIT: I'm sure he could try to rent some hash to defend his coin. Well, I can rent hash too. And i have a 550Mh head start. If we end up battling for hashpower, he will most certainly lose. I'm harping on this because that's a serious security risk.
And it's a risk that will be mitigated when naut is on PoS. That's why it's all the more important to get PoS done ASAP. Even if it's plain vanilla PoS with a later plan to do the complicated dynamic PoS.
|
|
|
|
jh83
Newbie
Offline
Activity: 8
Merit: 0
|
|
November 06, 2014, 05:14:57 AM |
|
BK, some friendly advice before your next developer debacle: http://www.dummies.com/how-to/content/business-contracts-kit-for-dummies-cheat-sheet.htmlWith one of them there fancy business contracts Weiner leaving is Blocktech's problem, not yours! Say it with me "Breach: A claim by one party to a contract that the other party has failed to perform as required under the contract". Don't forget to date and sign! Flying Mongoose has to get approval to use the dumb spiral logo for his handjob site but you don't have an enforceable contract in place with Blocktech. Great job focusing your legal team on the important things. Signed, Everyone who's been watching this slow motion train wreck
|
|
|
|
Lord Of The Internet
|
|
November 06, 2014, 06:56:59 AM |
|
that had me laughing out loud for real, which is rare He may very well have all this stuff covered, but he sure isn't communicating anywhere. So, you're forced to assume that he doesn't.
|
|
|
|
Doging
|
|
November 06, 2014, 08:24:04 AM |
|
Isn't there any way to get this person off this forum? everyone report. I am mentally challenged and find his use or the word retard offensive!!!
Nutildah is such an obvious troll it's best to just hit the ignore button, I think most regulars on this thread already have.
|
|
|
|
Doging
|
|
November 06, 2014, 08:32:13 AM |
|
Was any work done? Were were told several times the dynamic PoS was in testing.
I saw an apparent coinmarkets post from cogburn on twitter saying he has NAUT POS code but I'm sceptical.
|
|
|
|
cypz
|
|
November 06, 2014, 11:45:53 AM |
|
i think BW is butthurt cuz BK wanted a real dev and not some shitty hack
|
|
|
|
FlyingMongoose
|
|
November 07, 2014, 06:13:05 AM |
|
So much cheap NAUT...
|
qoinpro.com/951c974b34f66cc68e805832df0c9d8c
|
|
|
BitcoinNational
Legendary
Offline
Activity: 1470
Merit: 1010
Join The Blockchain Revolution In Logistics
|
|
November 07, 2014, 07:57:59 AM |
|
NAUT going anywhere ... like it
|
|
|
|
salfter
|
|
November 07, 2014, 10:47:30 PM |
|
I'm trying to spin up a new nautiluscoind instance, but it's having trouble finding any peers. I have the addnode statements from the OP in nautiluscoin.conf, but am just getting lots of this: 2014-11-07 22:38:10 connect() to 54.187.101.97:11161 failed after select(): Connection refused 2014-11-07 22:38:11 connect() to 54.187.101.97:11161 failed after select(): Connection refused 2014-11-07 22:38:11 connect() to 54.186.223.183:11161 failed after select(): Connection refused 2014-11-07 22:38:12 connect() to 54.186.223.183:11161 failed after select(): Connection refused 2014-11-07 22:38:12 connect() to 54.186.223.183:11161 failed after select(): Connection refused 2014-11-07 22:38:13 connect() to 54.187.101.97:11161 failed after select(): Connection refused 2014-11-07 22:38:14 connect() to 54.186.223.183:11161 failed after select(): Connection refused 2014-11-07 22:38:14 connect() to 54.186.223.183:11161 failed after select(): Connection refused 2014-11-07 22:38:14 connect() to 54.186.223.183:11161 failed after select(): Connection refused 2014-11-07 22:38:15 connect() to 54.186.223.183:11161 failed after select(): Connection refused 2014-11-07 22:38:15 connect() to 54.187.101.97:11161 failed after select(): Connection refused 2014-11-07 22:38:15 connect() to 54.186.223.183:11161 failed after select(): Connection refused 2014-11-07 22:38:15 connect() to 74.208.230.160:11161 failed after select(): Connection refused 2014-11-07 22:38:16 connect() to 54.187.101.97:11161 failed after select(): Connection refused 2014-11-07 22:38:16 connect() to 54.187.101.97:11161 failed after select(): Connection refused 2014-11-07 22:38:17 connect() to 54.187.101.97:11161 failed after select(): Connection refused 2014-11-07 22:38:17 connect() to 54.187.101.97:11161 failed after select(): Connection refused 2014-11-07 22:38:18 connect() to 54.187.101.97:11161 failed after select(): Connection refused 2014-11-07 22:38:18 connect() to 54.186.223.183:11161 failed after select(): Connection refused 2014-11-07 22:38:19 connect() to 54.186.223.183:11161 failed after select(): Connection refused 2014-11-07 22:38:20 connect() to 54.186.223.183:11161 failed after select(): Connection refused 2014-11-07 22:38:20 connect() to 54.186.223.183:11161 failed after select(): Connection refused 2014-11-07 22:38:21 connect() to 54.187.101.97:11161 failed after select(): Connection refused 2014-11-07 22:38:21 connect() to 54.187.101.97:11161 failed after select(): Connection refused 2014-11-07 22:38:22 connect() to 54.187.101.97:11161 failed after select(): Connection refused 2014-11-07 22:38:22 connect() to 54.186.223.183:11161 failed after select(): Connection refused 2014-11-07 22:38:23 connect() to 54.187.101.97:11161 failed after select(): Connection refused 2014-11-07 22:38:23 connect() to 54.187.101.97:11161 failed after select(): Connection refused 2014-11-07 22:38:24 connect() to 54.186.223.183:11161 failed after select(): Connection refused 2014-11-07 22:38:25 connect() to 54.186.223.183:11161 failed after select(): Connection refused 2014-11-07 22:38:25 connect() to 54.186.223.183:11161 failed after select(): Connection refused 2014-11-07 22:38:26 connect() to 54.186.223.183:11161 failed after select(): Connection refused 2014-11-07 22:38:26 connect() to 54.187.101.97:11161 failed after select(): Connection refused 2014-11-07 22:38:27 connect() to 54.187.101.97:11161 failed after select(): Connection refused 2014-11-07 22:38:27 connect() to 54.186.223.183:11161 failed after select(): Connection refused 2014-11-07 22:38:28 connect() to 54.187.101.97:11161 failed after select(): Connection refused 2014-11-07 22:38:28 connect() to 54.186.223.183:11161 failed after select(): Connection refused 2014-11-07 22:38:29 connect() to 54.187.101.97:11161 failed after select(): Connection refused 2014-11-07 22:38:30 connect() to 54.187.101.97:11161 failed after select(): Connection refused 2014-11-07 22:38:30 connect() to 54.186.223.183:11161 failed after select(): Connection refused 2014-11-07 22:38:31 connect() to 54.187.101.97:11161 failed after select(): Connection refused 2014-11-07 22:38:31 connect() to 54.186.223.183:11161 failed after select(): Connection refused 2014-11-07 22:38:32 connect() to 54.186.223.183:11161 failed after select(): Connection refused 2014-11-07 22:38:32 connect() to 54.186.223.183:11161 failed after select(): Connection refused 2014-11-07 22:38:32 connect() to 109.201.154.157:11161 failed after select(): Connection refused 2014-11-07 22:38:33 connect() to 54.187.101.97:11161 failed after select(): Connection refused 2014-11-07 22:38:33 connect() to 54.186.223.183:11161 failed after select(): Connection refused 2014-11-07 22:38:34 connect() to 54.186.223.183:11161 failed after select(): Connection refused 2014-11-07 22:38:35 connect() to 54.186.223.183:11161 failed after select(): Connection refused 2014-11-07 22:38:35 connect() to 54.186.223.183:11161 failed after select(): Connection refused 2014-11-07 22:38:36 connect() to 54.186.223.183:11161 failed after select(): Connection refused 2014-11-07 22:38:36 connect() to 54.187.101.97:11161 failed after select(): Connection refused
A bunch of other coin daemons are working without issue. Is there an updated set of nodes to use? There's mining activity going on, so there has to be a node available somewhere, but the current git source can't find it.
|
|
|
|
salfter
|
|
November 08, 2014, 12:40:56 AM |
|
I'm trying to spin up a new nautiluscoind instance, but it's having trouble finding any peers. I have the addnode statements from the OP in nautiluscoin.conf, but am just getting lots of this:
Make sure you are compiling using the "master" branch of the Git repository. I used this to download, configure, and build (I have a newer bdb and don't care about binary wallet compatibility): git clone https://github.com/nautiluscoin/nautiluscoin cd nautiluscoin ./autogen.sh && ./configure --with-incompatible-bdb && make -j3
That should be the master branch. Just in case it isn't for some reason, I'm building it again after this: As I was writing this post, the build completed. I restarted with the newly-built binary, and it's now downloading the blockchain. Weird, but I'll take it...thanks!
|
|
|
|
Equalizer1970
|
|
November 08, 2014, 01:34:27 AM |
|
Please contact me if you want to assist in the transition to PoS.
Thanks
jyap - can you please, for the love of gawd, give us an update of where POS stands. I think the long and strong deserve some information! Particularly, after the Byrce debacle. Thanks!
|
|
|
|
FlyingMongoose
|
|
November 08, 2014, 03:25:03 AM Last edit: November 08, 2014, 03:36:00 AM by FlyingMongoose |
|
Please contact me if you want to assist in the transition to PoS.
Thanks
jyap - can you please, for the love of gawd, give us an update of where POS stands. I think the long and strong deserve some information! Particularly, after the Byrce debacle. Thanks! He has told me he is DEFINITELY working on it. That's all the information I've been given.
|
qoinpro.com/951c974b34f66cc68e805832df0c9d8c
|
|
|
HKBvM
|
|
November 08, 2014, 02:15:22 PM |
|
Please contact me if you want to assist in the transition to PoS.
Thanks
jyap - can you please, for the love of gawd, give us an update of where POS stands. I think the long and strong deserve some information! Particularly, after the Byrce debacle. Thanks! He has told me he is DEFINITELY working on it. That's all the information I've been given. and this time I am sure it will actually be true. I am quite happy that julian agreed to help out. One of the few people that actually seem to care about cryptos and not just about a quick buck. If you arent following him and havent subscribed to his newletter - do it.
|
|
|
|
langvad
|
|
November 08, 2014, 02:48:12 PM |
|
Please contact me if you want to assist in the transition to PoS.
Thanks
jyap - can you please, for the love of gawd, give us an update of where POS stands. I think the long and strong deserve some information! Particularly, after the Byrce debacle. Thanks! He has told me he is DEFINITELY working on it. That's all the information I've been given. and this time I am sure it will actually be true. I am quite happy that julian agreed to help out. One of the few people that actually seem to care about cryptos and not just about a quick buck. If you arent following him and havent subscribed to his newletter - do it. I agree! I follow him on twitter, could be awesome to get him involved, he seems legit
|
|
|
|
FlyingMongoose
|
|
November 09, 2014, 03:49:31 PM |
|
Good day to be a buyer
|
qoinpro.com/951c974b34f66cc68e805832df0c9d8c
|
|
|
boogi
Member
Offline
Activity: 105
Merit: 10
|
|
November 09, 2014, 11:22:21 PM |
|
Good day to be a buyer
by the looks of those sell orders it looks there might be a few more "good days to be a buyer " to come.
|
|
|
|
halinyo
Legendary
Offline
Activity: 1106
Merit: 1000
The future is bright with DigiByte.
|
|
November 09, 2014, 11:37:36 PM |
|
100k sell wall ...
|
|
|
|
FlyingMongoose
|
|
November 10, 2014, 12:13:39 AM |
|
Good day to be a buyer
by the looks of those sell orders it looks there might be a few more "good days to be a buyer " to come. Could be. To let you guys know I've been contacted by Julian (jyap) and he asked me to let everyone know the following. This was pm'd to me. Hi,
Just to give you a quick update. You can pass on these messages.
I'm working on the NAUT PoS with my buddy @jemredin from Pinkcoin.
He has experience with Pinkcoin and with a recent ICO coin Seedcoin which was an experimental PoS coin.
Thank you NAUT holders for the patience.
- Julian
So definitely good days to be a buyer.
|
qoinpro.com/951c974b34f66cc68e805832df0c9d8c
|
|
|
|