[ANN][AID] AidBit | Digital-currency redefined | POW/POS | Groestl | Charity

[AidBit]

Good morning community. Good news! The night went without any fork whatsoever. Let's wait for couple more hours for final analysis but on our end everything seems to be running smoothly. We've just cleaned up blockchains on our nodes. Cleaning up pools databases and wallets will follow, meaning that the ports will be closed until all the blocks are confirmed and everything is paid to miners. This will be done gradually, server by server.

There are still couple of forks in the wild, so if you're having problems synching, try the following:

-Close the AidBit wallet
-Re-run our installer and select "fix sync problems" checkbox or delete all files except wallet.dat from %appdata%/AidBit/

If you're still having problems syncing:

-Close the AidBit wallet
-Delete all files except wallet.dat from %appdata%/AidBit/
-Create the file aidbit.conf inside %appdata%/AidBit

#aidbit.conf
connect=23.100.32.37
connect=23.100.8.20
connect=193.77.159.166
maxconnections=3

Run the wallet and let it sync. Then exit the wallet and delete the file aidbit.conf.

Thank you very much for believing in us,

Sincerely,

AidBit

[1715636379]

1715636379

[1715636379]

1715636379

[1715636379]

1715636379

[1715636379]

1715636379

[1715636379]

1715636379

[1715636379]

1715636379

[AidBit]

So I was in the shower and came up with an idea that could help both the wallet woes and give the devs time to rethink the POS issues. Its kinda funny how running water can have such heavy influences on our awareness. I was think instead of implimenting POS into the current payouts we could instead make the POS for early adopters more like a certificate of deposit(CD). In other words allow users to choose how much they want to put into a savings account in the wallet that is not spendable unitl it has matured to a specific date. Allow users to specify between different amounts of time like 2yr 3 yr and 4yr. This way the devs could have time to figure out how to payout the 20% interest on these accounts over tim for at least 2 years, The users get to keep mining groestl pow and making aidbit..and the best point of all...This would be even more assurance that those with CDs would hold aidbit and not dump it for at least 2 yrs. IMO this would be highly lucrative for early adopters and also an added bonus for late adopters to keep adoption going. It would also encourage more buy orders than sell orders increasing aidbits liquidity.

A very nice idea. As soon as the things settle down a bit, we will take the time and talk it over thoroughly with the community. Actually it seems that POS works as intended, only the POS diff went higher due to larger POS Target Spacing, so we're not seing many POS blocks, atm.

[HR]

Is the Windows wallet supported on Windows XP?

[AidBit]

Is the Windows wallet supported on Windows XP?

Yes, it was tested and should work well.

[AidBit]

fyi Moolah.io exchange (the one I recommended) bought out mintpal just this week. They will be upgrading the security among other things.

http://www.coindesk.com/moolah-acquires-troubled-altcoin-exchange-mintpal/

Moolah seems a really interesting Exchange; it has lower number of alt-coins and offers exchange to Fiat. Exactly what we need. It'll be probably quite hard to get accepted, so we would need massive support from your side. I will talk to our financial adviser and contact Moolah shortly. Thank you for the info.

AidBit

[AidBit]

REQUEST:

Dear AidBit Comunity,

Please check you Aidbit Wallet Versions, especially Linux users.

./aidbitd getinfo

If you're not on 1.0.2.1, please delete the git clone and
clone it again from https://github.com/aidbit/aidbit.

Thank you!

AidBit

[dstorm]

aid.altmine.net is updated.

Code:

./aidbitd getblockhash 18702
000000000b37e082ab886c715213537a0422d9e63a0f64f088261c4c0e586bc4

[AidBit]

aid.altmine.net is updated.

Code:

./aidbitd getblockhash 18702
000000000b37e082ab886c715213537a0422d9e63a0f64f088261c4c0e586bc4

Hash is OK!

[virgojeep]

fyi Moolah.io exchange (the one I recommended) bought out mintpal just this week. They will be upgrading the security among other things.

http://www.coindesk.com/moolah-acquires-troubled-altcoin-exchange-mintpal/

Moolah seems a really interesting Exchange; it has lower number of alt-coins and offers exchange to Fiat. Exactly what we need. It'll be probably quite hard to get accepted, so we would need massive support from your side. I will talk to our financial adviser and contact Moolah shortly. Thank you for the info.

AidBit

(Moolah will be starting with an audit of MintPal to get an idea of what needs to be done, and adding additional security features, since "security is something we are very good at."

They will also be removing dead coins from the exchange, and will add and remove new coins if they meet their criteria.

Green reports that though his company will be taking over operation of MintPal, they will maintain it as a separate service from Moolah. MintPal's focus will be on altcoin markets, while Moolah will be geared toward fiat markets.

The full takeover won't occur until August.) . He has an affinity toward charity coins which is why he is so involved in Dogecoin. I am also a member of doge and I participated in the NASCAR funding which happened mostly thanks to Moolah's accidental donation of 20 Mill doge. He put up a large portion of the funding for sponsoring Josh Wise. I think we have a better chance of getting added on mintpal than other altcoins because we're not a scam coin and we're focused on charity. 

[SimkoMiner]

There are still couple of forks in the wild, so if you're having problems synching, try the following:

-Close the AidBit wallet
-Re-run our installer and select "fix sync problems" checkbox or delete all files except wallet.dat from %appdata%/AidBit/

If you're still having problems syncing:

-Close the AidBit wallet
-Delete all files except wallet.dat from %appdata%/AidBit/
-Create the file aidbit.conf inside %appdata%/AidBit

#aidbit.conf
connect=23.100.32.37
connect=23.100.8.20
connect=193.77.159.166
maxconnections=3

Run the wallet and let it sync. Then exit the wallet and delete the file aidbit.conf.

Thanks for this instructions. I followed them and finally wallet seems to synchronize correctly. I want to stress the fact that it is imperative to follow this instructions in the right sequence where first the aidbit.conf file needs to be created in empty folder and then wallet needs to be run so that it connects to correct nodes from beginning. When I first synchronized wallet and then I created aidbit.conf with above settings and then restarted wallet, it simply couldn't synchronize properly because apparently I was already on wrong fork. Why don't you hardcode those 3 IP addresses in the wallet directly so that users don't need to create that aidbit.conf file manually?

[AidBit]

There are still couple of forks in the wild, so if you're having problems synching, try the following:

-Close the AidBit wallet
-Re-run our installer and select "fix sync problems" checkbox or delete all files except wallet.dat from %appdata%/AidBit/

If you're still having problems syncing:

-Close the AidBit wallet
-Delete all files except wallet.dat from %appdata%/AidBit/
-Create the file aidbit.conf inside %appdata%/AidBit

#aidbit.conf
connect=23.100.32.37
connect=23.100.8.20
connect=193.77.159.166
maxconnections=3

Run the wallet and let it sync. Then exit the wallet and delete the file aidbit.conf.

Thanks for this instructions. I followed them and finally wallet seems to synchronize correctly. I want to stress the fat that it is imperative to follow this instructions in the right sequence where first the aidbit.conf file needs to be created in empty folder and then wallet needs to be run so that it connects to correct nodes from beginning. When I first synchronized wallet and then I created aidbit.conf with above settings and then restarted wallet, it simply couldn't synchronize properly because apparently I was already on wrong fork. Why don't you hardcode those 3 IP addresses in the wallet directly so that users don't need to create that aidbit.conf file manually?

Actually those addresses and a few more are already hardcoded in the wallet. The wallets connected correctly to our nodes and got a list of various nodes in the system, including the rogue ones, which started sending wrong blocks. With the above commands you limit the connection to only three nodes and no more. It would not be good to keep the above commands permanently since the wallet would loose connection if all three nodes would go down. The problem is just temporary, when all users update their wallets and "find" the correct fork it will go away. There is also one more mechanism we will add soon - dns seed nodes. Wallets are already prepared but we didn't implement it yet.

[AidBit]

Please post NOMP pool instructions / codes .. or if done p2pool but this is going to require some more work?
I will make a new pool..
Or can you just use a pool with support for groestl?

Please see necessary stratum modifications, posted on our git:
https://github.com/AidBit/node-stratum-pool/tree/AidBit

Configuring NOMP is a pretty straight forward process.
Due to our modifications, first two reward recipients in the pool config must be configured with 0 percentages:

Code:

"rewardRecipients": {
"ANhmhMCxJZkV7M5nmBMaXZWVfRuba79B3m": 0,
"AVBLFaezaUM83odu4x3Rr8dQ8vHVFHEddC": 0
},

Cheers,

V

Hi!

Is it possible to use vanilla NOMP without modifications?
Perhaps increase the donation/dev from 10% and 3% to 12% and 3.6% or something like this?

Code:

    "rewardRecipients": {
        "ANhmhMCxJZkV7M5nmBMaXZWVfRuba79B3m": 12,
        "AVBLFaezaUM83odu4x3Rr8dQ8vHVFHEddC": 3.6,

I have a NOMP pool with multiple coins and don't want to modify the code.

Currently I'm always getting "ERROR: ConnectBlock() : coinbase does not pay enough to donation address!". Even if I have "ANhmhMCxJZkV7M5nmBMaXZWVfRuba79B3m": 10 in config. Why???

Thanks

Never mind. I have integrated your change in a way that it does not break all other coins.
https://github.com/srcxxx/node-stratum-pool/commit/172bd3483be8b79262b742c2dcaa0111c037e093

And now I'm happy to announce that Groestl Optimized Pool finally supports AidBit!
You should be getting 20.0 MH/s on R9 290.
See https://bitcointalk.org/index.php?topic=652849

Thanks

Sorry for late reply, we were as you've probably noticed pretty busy. Actually our code should not break other coins. If and only if the percentages are set to 0, which you would never use in other coins, it sets the donation/foundation amounts to first two addresses.

[coke15]

hi

last wallet look's good

good work  dev's

[HR]

Good morning community. Good news! The night went without any fork whatsoever. Let's wait for couple more hours for final analysis but on our end everything seems to be running smoothly. We've just cleaned up blockchains on our nodes. Cleaning up pools databases and wallets will follow, meaning that the ports will be closed until all the blocks are confirmed and everything is paid to miners. This will be done gradually, server by server.

There are still couple of forks in the wild, so if you're having problems synching, try the following:

-Close the AidBit wallet
-Re-run our installer and select "fix sync problems" checkbox or delete all files except wallet.dat from %appdata%/AidBit/

If you're still having problems syncing:

-Close the AidBit wallet
-Delete all files except wallet.dat from %appdata%/AidBit/
-Create the file aidbit.conf inside %appdata%/AidBit

#aidbit.conf
connect=23.100.32.37
connect=23.100.8.20
connect=193.77.159.166
maxconnections=3

Run the wallet and let it sync. Then exit the wallet and delete the file aidbit.conf.

Thank you very much for believing in us,

Sincerely,

AidBit

Is it still just a bit too early to state that this was a smashing success? Should we still knock on/touch wood?

Congratulations!!!

[AidBit]

Good morning community. Good news! The night went without any fork whatsoever. Let's wait for couple more hours for final analysis but on our end everything seems to be running smoothly. We've just cleaned up blockchains on our nodes. Cleaning up pools databases and wallets will follow, meaning that the ports will be closed until all the blocks are confirmed and everything is paid to miners. This will be done gradually, server by server.

There are still couple of forks in the wild, so if you're having problems synching, try the following:

-Close the AidBit wallet
-Re-run our installer and select "fix sync problems" checkbox or delete all files except wallet.dat from %appdata%/AidBit/

If you're still having problems syncing:

-Close the AidBit wallet
-Delete all files except wallet.dat from %appdata%/AidBit/
-Create the file aidbit.conf inside %appdata%/AidBit

#aidbit.conf
connect=23.100.32.37
connect=23.100.8.20
connect=193.77.159.166
maxconnections=3

Run the wallet and let it sync. Then exit the wallet and delete the file aidbit.conf.

Thank you very much for believing in us,

Sincerely,

AidBit

Is it still just a bit too early to state that this was a smashing success? Should we still knock on/touch wood?

Congratulations!!!

Let's run it for couple more hours maybe a night, just to be sure. But we're almost certain we fixed it. But another post-forking issue arose and I just realized it is not so innocent. What happened is the forks messed up peoples blockchain databases, so we've devised a pretty neat plan - to extend our "fix synching problem" option in the installer. The new installer will include a cleaned up blockchain that will replace the old one on the install. Unfortunatelly we have to update the version again. It'll be just the version bump to notify the wallets and to see who already updated. More details in couple of minutes.

[AidBit]

SPECIAL UPDATE FOR WINDOWS USERS:

Updated AidBit Wallet v1.0.2.2.

Fix: Extended "Fix Syncing Problems" option in the installer

We realized the forking issues messed up people's blockchain databases.
In turn this caused synching problems for new wallets which get served blocks
from corrupted wallets.

The v1.0.2.2 Installer includes cleaned-up blockchain which gets installed if
you select "fix synching problems" option.

Even if you are synched, we recommend you to fix your bc database.

For Linux and advanced Windows users we recommend the following method:

-Close the AidBit wallet
-Delete all files except wallet.dat from %appdata%/AidBit      Linux:  ~/.AidBit/
-Create the file aidbit.conf inside %appdata%/AidBit                       ~/.AidBit/

#aidbit.conf
connect=23.100.32.37
connect=23.100.8.20
connect=193.77.159.166
maxconnections=3

-Sync your wallet
-Close the wallet and delete connect & maxconnections arguments from aidbit.conf

www.aidbit.net/download

Thank you!

AidBit

[Singman33]

With the following informations, could you explain me how you calculate the block reward ?

Code:

$ aidbitd getinfo
{
    "version" : "v1.0.2.0",
    "protocolversion" : 60015,
    "walletversion" : 60000,
    "balance" : 0.00000000,
    "newmint" : 0.00000000,
    "stake" : 0.00000000,
    "blocks" : 17965,
    "timeoffset" : 0,
    "moneysupply" : 4054901.95566341,
    "connections" : 3,
    "proxy" : "",
    "ip" : "--.--.--.--",
    "difficulty" : {
        "proof-of-work" : 12.67447368,
        "proof-of-stake" : 0.00060976
    },
    "testnet" : false,
    "keypoololdest" : 1405716160,
    "keypoolsize" : 101,
    "paytxfee" : 0.00010000,
    "mininput" : 0.00000000,
    "errors" : "WARNING: Invalid checkpoint found! Displayed transactions may not be correct! You may need to upgrade, or notify developers."
}

The error message will be corrected soon, when wallet will get updated

Thanks.

[AidBit]

With the following informations, could you explain me how you calculate the block reward ?

Code:

$ aidbitd getinfo
{
    "version" : "v1.0.2.0",
    "protocolversion" : 60015,
    "walletversion" : 60000,
    "balance" : 0.00000000,
    "newmint" : 0.00000000,
    "stake" : 0.00000000,
    "blocks" : 17965,
    "timeoffset" : 0,
    "moneysupply" : 4054901.95566341,
    "connections" : 3,
    "proxy" : "",
    "ip" : "82.229.26.235",
    "difficulty" : {
        "proof-of-work" : 12.67447368,
        "proof-of-stake" : 0.00060976
    },
    "testnet" : false,
    "keypoololdest" : 1405716160,
    "keypoolsize" : 101,
    "paytxfee" : 0.00010000,
    "mininput" : 0.00000000,
    "errors" : "WARNING: Invalid checkpoint found! Displayed transactions may not be correct! You may need to upgrade, or notify developers."
}

The error message will be corrected soon, when wallet will get updated

Thanks.

Well, with the above information you could only estimate the reward for block 19765, since the reward is now based on previous block's height and difficulty. But you could call getblockhash 17964 and getblock #hash to get the correct difficulty, then you'd just need to calculate it using: ceil(8 * dDiff / (525600 + 17964) * 525600). Or you could use getmininginfo command.

Regards,

AidBit

[smallkite]

SOS!!!!

I have mined twice,the time is 2014.7.19-2014.7.24 and 7.30-7.31,but my old wallet show 47000 coins ,these coins were the first step's coins,

wo download the new wallet in another computer ,the old wallet is working very well,but not accept the twiec step's coins,noly gei me the interests of 47000,

the new wallet only gei me the twice'coins  ,surprise to me ,the twice'coins is only 100+ coins.

I find the net wallet address ,the address show 55000+coins.

can you  help me?

my new wallet and old wallet

[smallkite]

ok !no problem!

the new wallet is beautifull!

thanks!