Pages:
Author

Topic: [ANN] Maieuticoin | 2014% PoS | 10k/MMXIV and BALLS/MMXIV Markets NOW OPEN - page 74. (Read 283202 times)

legendary
Activity: 2548
Merit: 1054
CPU Web Mining 🕸️ on webmining.io
Just so everyone is clear...the new daily stake will be about 5.5% a day
Is that now or when does that start?

Block 80k. First post on this page
I never read the first page. I only read new posts.

You should try reading my last post again, then
hero member
Activity: 556
Merit: 500
Just so everyone is clear...the new daily stake will be about 5.5% a day
Is that now or when does that start?

Block 80k. First post on this page
I never read the first page. I only read new posts.
legendary
Activity: 2548
Merit: 1054
CPU Web Mining 🕸️ on webmining.io
Just so everyone is clear...the new daily stake will be about 5.5% a day
Is that now or when does that start?

Block 80k. First post on this page
hero member
Activity: 556
Merit: 500
Just so everyone is clear...the new daily stake will be about 5.5% a day
Is that now or when does that start?
legendary
Activity: 2548
Merit: 1054
CPU Web Mining 🕸️ on webmining.io
Just so everyone is clear...the new daily stake will be about 5.5% a day
legendary
Activity: 2548
Merit: 1054
CPU Web Mining 🕸️ on webmining.io
I don't know if it was intentional or not, but the new client code, installed a new wallet.dat file.  Luckily I just backed that up yesterday.  If that was the intended install sequence a BIG warning should be made.  

   Yea, I know you should always backup your wallets.  And I do, but I haven't had a client update change my wallet.dat.  So that's a big warning sign.  

It worked for me just fine when I downloaded and opened it. Pretty much picked up where the old client was without re-indexing.

Reindex will only occur if you were using 1.0.3. If you were previously on 1.0.2, there will be no need for a reindex or blockchain rescanning
hero member
Activity: 518
Merit: 501
I don't know if it was intentional or not, but the new client code, installed a new wallet.dat file.  Luckily I just backed that up yesterday.  If that was the intended install sequence a BIG warning should be made. 

   Yea, I know you should always backup your wallets.  And I do, but I haven't had a client update change my wallet.dat.  So that's a big warning sign.   

It worked for me just fine when I downloaded and opened it. Pretty much picked up where the old client was without re-indexing.
legendary
Activity: 1007
Merit: 1000
I don't know if it was intentional or not, but the new client code, installed a new wallet.dat file.  Luckily I just backed that up yesterday.  If that was the intended install sequence a BIG warning should be made. 

   Yea, I know you should always backup your wallets.  And I do, but I haven't had a client update change my wallet.dat.  So that's a big warning sign.   

That would not happen unless you did not have a file named wallet.dat in the roaming folder

   I had the old 1.0.3 code running. Downloaded the new client, installed (un-rar'ed) it to a new folder, stopped the old wallet, and started up the new one.   Waited about 4 hours for it to re-download the blockchain.  I was assuming it was re-syncing.  The new wallet had a balance of 0.  Copied my old wallet back-up over and now all is good. 

   Can't be a different folder in the roaming directory, because I had a backup folder hung off that folder, and it was still there.  Not sure what happened.     
legendary
Activity: 2548
Merit: 1054
CPU Web Mining 🕸️ on webmining.io
I don't know if it was intentional or not, but the new client code, installed a new wallet.dat file.  Luckily I just backed that up yesterday.  If that was the intended install sequence a BIG warning should be made. 

   Yea, I know you should always backup your wallets.  And I do, but I haven't had a client update change my wallet.dat.  So that's a big warning sign.   

That would not happen unless you did not have a file named wallet.dat in the roaming folder
legendary
Activity: 1007
Merit: 1000
I don't know if it was intentional or not, but the new client code, installed a new wallet.dat file.  Luckily I just backed that up yesterday.  If that was the intended install sequence a BIG warning should be made. 

   Yea, I know you should always backup your wallets.  And I do, but I haven't had a client update change my wallet.dat.  So that's a big warning sign.   
legendary
Activity: 2548
Merit: 1054
CPU Web Mining 🕸️ on webmining.io
I have a problem with Transaction ID: f54312fb9a34beac8e54a0d19b7b00d1bc5a6e9e73d1b728d1c7ddadc201ff1a
sent it on 11/16 still showing unconfirmed in my wallet, confirmations go up to 4 then back to 0. What did I do and how can I fix it lol

repwairwallet
sr. member
Activity: 434
Merit: 250
"The mass of men lead lives of quiet desperation."
I have a problem with Transaction ID: f54312fb9a34beac8e54a0d19b7b00d1bc5a6e9e73d1b728d1c7ddadc201ff1a
sent it on 11/16 still showing unconfirmed in my wallet, confirmations go up to 4 then back to 0. What did I do and how can I fix it lol
hero member
Activity: 595
Merit: 500
It won't be delisted
Good to hear that.
Earlier today I have sent a request to them to wait with de-listing due to new developments for this coin, which will cause new traffic, but that might take a week before it shows in the average, so that it would be good to wait.
Now you already have taken care of this, so that is good. Thanks.
legendary
Activity: 2548
Merit: 1054
CPU Web Mining 🕸️ on webmining.io
Even if it gets delisted from Bittrex, it doesn't matter. It's still on Poloniex anyway
You need to check the volume of M on poloniex, the last trade happened on 16th and before that 10 days ago. M getting delisted from bittrex means killing a dead coin again. The only thing you can do right now is prevent it from getting delisted from bittrex . All you have to do is put a sell wall and buy into your own sell wall, which would generate trade volume and cause you no loss.
There still is traffic on BitTrex, but they are *very* quick with de-listing - I experienced that with another coin that is far from dead,
in fact the coin was a year old before it got listed and they have de-listed it, but it has not affected the value or the traffic on the other exchanges...

It won't be delisted
hero member
Activity: 595
Merit: 500
Even if it gets delisted from Bittrex, it doesn't matter. It's still on Poloniex anyway
You need to check the volume of M on poloniex, the last trade happened on 16th and before that 10 days ago. M getting delisted from bittrex means killing a dead coin again. The only thing you can do right now is prevent it from getting delisted from bittrex . All you have to do is put a sell wall and buy into your own sell wall, which would generate trade volume and cause you no loss.
There still is traffic on BitTrex, but they are *very* quick with de-listing - I experienced that with another coin that is far from dead,
in fact the coin was a year old before it got listed and they have de-listed it, but it has not affected the value or the traffic on the other exchanges...
hero member
Activity: 595
Merit: 500
Many changes in this client. At block 80,000, Maieuticoin will fork to a much higher yearly yield from staking. This change will take effect immediately after block 80,000. This will also be, barring any security threats, the final mandatory update to Maieuticoin's base parameters. Any updates from here forward will be responsive in nature to security risks or optional GUI and feature upgrades
Great news! I am looking forward to that and buying more MMXIV
legendary
Activity: 2548
Merit: 1054
CPU Web Mining 🕸️ on webmining.io
Maieuticoin 1.0.8

Many changes in this client. At block 80,000, Maieuticoin will fork to a much higher yearly yield from staking. This change will take effect immediately after block 80,000. This will also be, barring any security threats, the final mandatory update to Maieuticoin's base parameters. Any updates from here forward will be responsive in nature to security risks or optional GUI and feature upgrades

Important updates at block 80,000 include:
  • The MMXIV Ticker has returned! We found a creative way to incorporate it back into the coin
  • Yearly staking yield increased to 2014%. The previous rate of 50% was below market average
  • Peers that do not update prior to the hard fork will all become rejected nodes after block 80,000
  • If you were previously using 1.0.3, the client will automatically reindex the blockchain on first load
  • We were unimpressed with 1.0.3; increased orphans with coin control lacking utility. That being said...
  • Coin control has been removed for the current build, but will come back with more features very soon

We are very excited about this update. Maieuticoin now runs with a very lightweight, easily modifiable source code and GUI clients. This fork could not come at a better time. The Snowball staking hardware is about to ship and will include this version of Maieuticoin upon arrival. You will be quickly set up, ready to deposit, and start staking in minutes!


 
legendary
Activity: 2548
Merit: 1054
CPU Web Mining 🕸️ on webmining.io
Windows is up, will be on github shortly
newbie
Activity: 19
Merit: 0
Even if it gets delisted from Bittrex, it doesn't matter. It's still on Poloniex anyway
You need to check the volume of M on poloniex, the last trade happened on 16th and before that 10 days ago. M getting delisted from bittrex means killing a dead coin again. The only thing you can do right now is prevent it from getting delisted from bittrex . All you have to do is put a sell wall and buy into your own sell wall, which would generate trade volume and cause you no loss.
hero member
Activity: 556
Merit: 500
We are aware of that UI issue, but getinfo will always be accurate. Still not sure where the hiccup is in the display, though
Why don't you call getinfo() for the display if getinfo is always accurate?

I don't like the idea of being diluted as such a rate, I like it how it is now.

It seems like this is just your little toy. Every few days you wake up and ask, "what should I do to M coin today? Change the name? change the staking? how about another fork?" Would be nice to see an overall plan and strategy that is stuck to and executed.

Pages:
Jump to: