I read a few pages of the forum, I understand that we need a new wallet, but for now we can mining on the wallet of the exchange.
I hope for the further development of the project
Topic: [ANN] AGAcoin (currency for the Amiga community and others) - Developers wanted! - page 2. (Read 32635 times)
July 06, 2018, 03:19:18 AM
June 27, 2018, 05:04:51 AM
Please provide more information about the bounty program
June 24, 2018, 10:00:41 AM
Not too much if the diff retargeting time and algo is not updated
June 24, 2018, 09:56:39 AM
How long do you guys think we can keep our AGA at Cryptopia? The block explorer seems working at least. Good that agacoin.dk is registered, someone creating an exchange for it?
We could start out very simple, but I'm not sure about legalities in our country. I have long been dreaming about creating an exchange, but I think the rules are a bit too strict here where I live.
We could start out very simple, but I'm not sure about legalities in our country. I have long been dreaming about creating an exchange, but I think the rules are a bit too strict here where I live.
June 13, 2018, 04:59:09 AM
May 16, 2018, 10:44:56 AM
Why the volume on this coin?
May 12, 2018, 04:32:54 PM
Have added the Coin to my pool :
https://lafuhosting.top/
Happy Mining !
https://lafuhosting.top/
Code:
stratum+tcp://lafuhosting.top:3437 -u YourWalletAdress -p c=AGA
Happy Mining !
May 02, 2018, 03:48:05 AM
We have added AMIGA to our pools !
We have live help ! DDos Protected Servers
Blockfinders Mpos Pools !
Twitter: https://twitter.com/Blockfinders - Skype - [email protected]
Homepage - www.blockfinders.co.uk
Twitter: https://twitter.com/Blockfinders - Skype - [email protected]
April 07, 2018, 09:16:16 AM
Such a great project, hope you guys success
April 05, 2018, 09:07:35 PM
Looking in my last push i saw it will never change the diff, could somebody check if this look's good? it should be working after height 535020
Code:
// Limit adjustment step
int64 nActualTimespan = pindexLast->GetBlockTime() - pindexFirst->GetBlockTime();
printf(" nActualTimespan = %"PRI64d" before bounds\n", nActualTimespan);
if(pindexLast->nHeight+1 > 535020)
{
// From Digibyte to implement Digishield
static const int64 nAveragingInterval = 10; // 10 blocks
static const int64 nAveragingTargetTimespan = nAveragingInterval * nTargetSpacing; // *10
static const int64 nMaxAdjustDown = 16; // 16% adjustment down
static const int64 nMaxAdjustUp = 8; // adjustment up
static const int64 nMinActualTimespan = nAveragingTargetTimespan * (100 - nMaxAdjustUp) / 100;
static const int64 nMaxActualTimespan = nAveragingTargetTimespan * (100 + nMaxAdjustDown) / 100;
if (nActualTimespan < nMinActualTimespan)
nActualTimespan = nMinActualTimespan;
if (nActualTimespan > nMaxActualTimespan)
nActualTimespan = nMaxActualTimespan;
}
else if(pindexLast->nHeight+1 > 10000)
{
if (nActualTimespan < nTargetTimespan/4)
nActualTimespan = nTargetTimespan/4;
if (nActualTimespan > nTargetTimespan*4)
nActualTimespan = nTargetTimespan*4;
}
else if(pindexLast->nHeight+1 > 5000)
{
if (nActualTimespan < nTargetTimespan/8)
nActualTimespan = nTargetTimespan/8;
if (nActualTimespan > nTargetTimespan*4)
nActualTimespan = nTargetTimespan*4;
}
else
{
if (nActualTimespan < nTargetTimespan/16)
nActualTimespan = nTargetTimespan/16;
if (nActualTimespan > nTargetTimespan*4)
nActualTimespan = nTargetTimespan*4;
}
// Retarget
CBigNum bnNew;
bnNew.SetCompact(pindexLast->nBits);
bnNew *= nActualTimespan;
bnNew /= nTargetTimespan;
if (bnNew > bnProofOfWorkLimit)
bnNew = bnProofOfWorkLimit;
Can these kinds of changes be made without causing a fork? I assumed we need to collect all changes into a new "major release" then get everybody (including the wallets run by any exchanges) to move to the new version ahead of time. Shouldn't there be a built-in block height a few weeks/months in the future at which time the new code changes become live, so we can make sure everyone has upgraded before then? If that's the case then I think we should only choose the specs like block time and difficulty adjustment after some agreement as to what the changes should be.
Also - since @sonountaleban has stated they left the AGAcoin project, I suggest everyone submit code changes to https://github.com/AGAcoin/amigacoin where we have set up the new GitHub Organization (If you need commit access just ask).
Sorry for the late answer, i was kind of busy developing my own coin, but meanwhile i was able to make some tests. If we modify the diff algorithm and time per block only pool's and solo miners should update its wallets at first. Old wallet's will continue sending a receiving transactions.
I will submit new changes i have tested on my own coin to https://github.com/AGAcoin/amigacoin for review
April 05, 2018, 07:11:24 PM
Not really to do with AGAcoin directly, but if you happen to still own an Amiga500 you may want to check out the New Amiga 500 Cases Campaign. https://www.indiegogo.com/projects/new-compatible-case-for-amiga-500-plus/x/18291379#/
I got one of their 1200 cases and it is great quality - everything they said it would be.
I got one of their 1200 cases and it is great quality - everything they said it would be.
March 02, 2018, 06:58:59 PM
hi guys as you know we have been running a pool for amiga coin
Join our discord ,
We have a lot of hashrate on the pool and have found loads of blocks
maybe post the updates here also
https://discord.gg/ZgAqCPu
Join our discord ,
We have a lot of hashrate on the pool and have found loads of blocks
maybe post the updates here also
https://discord.gg/ZgAqCPu
March 02, 2018, 03:30:19 AM
Looking in my last push i saw it will never change the diff, could somebody check if this look's good? it should be working after height 535020
Code:
// Limit adjustment step
int64 nActualTimespan = pindexLast->GetBlockTime() - pindexFirst->GetBlockTime();
printf(" nActualTimespan = %"PRI64d" before bounds\n", nActualTimespan);
if(pindexLast->nHeight+1 > 535020)
{
// From Digibyte to implement Digishield
static const int64 nAveragingInterval = 10; // 10 blocks
static const int64 nAveragingTargetTimespan = nAveragingInterval * nTargetSpacing; // *10
static const int64 nMaxAdjustDown = 16; // 16% adjustment down
static const int64 nMaxAdjustUp = 8; // adjustment up
static const int64 nMinActualTimespan = nAveragingTargetTimespan * (100 - nMaxAdjustUp) / 100;
static const int64 nMaxActualTimespan = nAveragingTargetTimespan * (100 + nMaxAdjustDown) / 100;
if (nActualTimespan < nMinActualTimespan)
nActualTimespan = nMinActualTimespan;
if (nActualTimespan > nMaxActualTimespan)
nActualTimespan = nMaxActualTimespan;
}
else if(pindexLast->nHeight+1 > 10000)
{
if (nActualTimespan < nTargetTimespan/4)
nActualTimespan = nTargetTimespan/4;
if (nActualTimespan > nTargetTimespan*4)
nActualTimespan = nTargetTimespan*4;
}
else if(pindexLast->nHeight+1 > 5000)
{
if (nActualTimespan < nTargetTimespan/8)
nActualTimespan = nTargetTimespan/8;
if (nActualTimespan > nTargetTimespan*4)
nActualTimespan = nTargetTimespan*4;
}
else
{
if (nActualTimespan < nTargetTimespan/16)
nActualTimespan = nTargetTimespan/16;
if (nActualTimespan > nTargetTimespan*4)
nActualTimespan = nTargetTimespan*4;
}
// Retarget
CBigNum bnNew;
bnNew.SetCompact(pindexLast->nBits);
bnNew *= nActualTimespan;
bnNew /= nTargetTimespan;
if (bnNew > bnProofOfWorkLimit)
bnNew = bnProofOfWorkLimit;
Can these kinds of changes be made without causing a fork? I assumed we need to collect all changes into a new "major release" then get everybody (including the wallets run by any exchanges) to move to the new version ahead of time. Shouldn't there be a built-in block height a few weeks/months in the future at which time the new code changes become live, so we can make sure everyone has upgraded before then? If that's the case then I think we should only choose the specs like block time and difficulty adjustment after some agreement as to what the changes should be.
Also - since @sonountaleban has stated they left the AGAcoin project, I suggest everyone submit code changes to https://github.com/AGAcoin/amigacoin where we have set up the new GitHub Organization (If you need commit access just ask).
March 02, 2018, 03:28:50 AM
With respect, that answer doesn't really provide a working answer. It actually sounds like it does the exact opposite. Within the past couple pages it's been stated that actual Amigas are not capable of running the wallet (unless we get one that's web-based), to say nothing of mining. In point of fact, it sounds as if AGAcoin cannot actually be used by Amigans.
Yes, AGAcoin needs to be updated. It also needs concrete reasons to exist, and what it brings to the market that other coins do not. Not defining this makes the work a technical endeavor, not a practical one. And there is certainly value in honing those skills.
I say this as someone who very much wants to see Amiga and AGAcoin succeed.
Ideas? Maybe a few. Develop new hardware. What does that look like? That's a longer discussion for another venue. I would contribute this way before I'd ever contribute to a Kickstarter.
Yes, AGAcoin needs to be updated. It also needs concrete reasons to exist, and what it brings to the market that other coins do not. Not defining this makes the work a technical endeavor, not a practical one. And there is certainly value in honing those skills.
I say this as someone who very much wants to see Amiga and AGAcoin succeed.
Ideas? Maybe a few. Develop new hardware. What does that look like? That's a longer discussion for another venue. I would contribute this way before I'd ever contribute to a Kickstarter.
Thanks for pointing these things out. It is important that AGAcoin clarifies its purpose. The original dev is no longer working on the project, so the purpose is whatever we decide to make of it.
Perhaps I should have said that https://agacoin.github.io/about is all that AGAcoin has for now in the way of answers to your question, and that you are (and anyone else in the AGA community) welcome to improve on AGAcoin's mission statement, via discussion and/or editing that page on GitHub.
I believe the suggestion that AGAcoin can not be used by Amigans because it does not run on Amiga hardware is incorrect. How many modern Amiga related websites are there? Lots. How many of them are running on actual Amiga hardware? Approximately zero. In the same way that modern Amigans can use modern Amiga related websites (to purchase or research Amiga), I think it's fair to say that AGAcoin can certainly be used by Amigans - even though it must be via a modern "mainstream OS" like windows/mac/linux for the moment.
Making a secure crypto-currency that runs on real Amigas would be a very noteworthy achievement, but also unlikely to have a large positive impact, as it would be a niche concept with no interoperability with broader cryptocurrency, crowdfunding, or online-retail.
New Amiga-based hardware/software/media projects are announced regularly by the Amiga community, and I believe AGAcoin should be aiming to support and promote these projects, rather than trying to come up with its own hardware as well as a coin. As exciting as it would be, I do not think that AGAcoin should develop new hardware itself. Rather, it should aim to act as an economic catalyst and supporter of such projects in the Amiga community.
I personally imagine the following purposes, and objectives for AGAcoin.
Purposes of AGAcoin:
* Raising general public awareness in modern Amiga community developments.
* Helping to promote and fund Amiga community related development (hardware, software, websites, podcasts, etc).
* Supporting the Amiga hardware/software economy (by providing a software-based currency that is held and managed by those with an interest in the Amiga community).
Objectives or "roadmap" to achieve said purpose (in order of implementation):
1. Update the code. For this I think we need to update to a modern codebase (e.g. latest litecoin with tweaks to mining specs and block times).
2. Establish a long-term distribution programme (by which AGAcoin community will offer to distribute a sizable amount of AGAcoin to active projects within the wider Amiga community over time).
3. Offer an online payment API, so that online retailers can get a reliable message when they are paid in AGA, so they can integrate it as a payment option in their web store.
4. Become an accepted form of payment/currency within the Amiga scene for online-retail, crowdfunding, and p2p payments.
5. If all that happens, then develop AGAcoin software for modern web-aware Amiga-based systems, so that AGAcoin can be used on modern Amiga-like systems (web wallet to start with).
For #1. I don't have the time or ability to upgrade and maintain the C++ code. But I can review it and help manage the GitHub repository. Thus, we need active developers.
For #2, I have slowly been acquiring AGA and I'm willing to donate it to a long-term AGA distribution programme for the wider Amiga community, once we have a codebase that isn't embarrasingly out of date.
For #3, I think it's important that AGAcoin help online-retailers to accept AGA for their products.
For #4, This can be combined with #2 by offering online-retailers a bonus portion of the distribution programme if they choose to accept AGAcoin for their products.
For #5, Well, obviously it would be nice for AGAcoin to run on an Amiga-based or Amiga-inspired OS eventually.
All just thoughts on which I encourage discussion.
March 01, 2018, 08:19:11 PM
Well, i have pushed the fork, hope somebody else can test it. I have it runnimg on main net y my explorer and personal node without problems, jus i think the new diff algorithm wont work until there's nodes mining wirh it.
I use Linux, so i haven't test it on Windows nor Mac, i will try to compile it on VirtualBox for both of them.
And finally, i would like to make a staff so we can make a road map, who say me?
Any question please findme in Discord: https://discord.gg/dEuwyEk
I use Linux, so i haven't test it on Windows nor Mac, i will try to compile it on VirtualBox for both of them.
And finally, i would like to make a staff so we can make a road map, who say me?
Any question please findme in Discord: https://discord.gg/dEuwyEk
March 01, 2018, 10:04:25 AM
I opened a page on facebook for agacoin: https://www.facebook.com/agacoin and a group: https://www.facebook.com/groups/agacoin/ please like the page and join the group
February 28, 2018, 03:26:51 PM
Looking in my last push i saw it will never change the diff, could somebody check if this look's good? it should be working after height 535020
Code:
// Limit adjustment step
int64 nActualTimespan = pindexLast->GetBlockTime() - pindexFirst->GetBlockTime();
printf(" nActualTimespan = %"PRI64d" before bounds\n", nActualTimespan);
if(pindexLast->nHeight+1 > 535020)
{
// From Digibyte to implement Digishield
static const int64 nAveragingInterval = 10; // 10 blocks
static const int64 nAveragingTargetTimespan = nAveragingInterval * nTargetSpacing; // *10
static const int64 nMaxAdjustDown = 16; // 16% adjustment down
static const int64 nMaxAdjustUp = 8; // adjustment up
static const int64 nMinActualTimespan = nAveragingTargetTimespan * (100 - nMaxAdjustUp) / 100;
static const int64 nMaxActualTimespan = nAveragingTargetTimespan * (100 + nMaxAdjustDown) / 100;
if (nActualTimespan < nMinActualTimespan)
nActualTimespan = nMinActualTimespan;
if (nActualTimespan > nMaxActualTimespan)
nActualTimespan = nMaxActualTimespan;
}
else if(pindexLast->nHeight+1 > 10000)
{
if (nActualTimespan < nTargetTimespan/4)
nActualTimespan = nTargetTimespan/4;
if (nActualTimespan > nTargetTimespan*4)
nActualTimespan = nTargetTimespan*4;
}
else if(pindexLast->nHeight+1 > 5000)
{
if (nActualTimespan < nTargetTimespan/8)
nActualTimespan = nTargetTimespan/8;
if (nActualTimespan > nTargetTimespan*4)
nActualTimespan = nTargetTimespan*4;
}
else
{
if (nActualTimespan < nTargetTimespan/16)
nActualTimespan = nTargetTimespan/16;
if (nActualTimespan > nTargetTimespan*4)
nActualTimespan = nTargetTimespan*4;
}
// Retarget
CBigNum bnNew;
bnNew.SetCompact(pindexLast->nBits);
bnNew *= nActualTimespan;
bnNew /= nTargetTimespan;
if (bnNew > bnProofOfWorkLimit)
bnNew = bnProofOfWorkLimit;
February 28, 2018, 02:55:50 PM
Guys, i think i necesary more hashing power, im mining at http://coincave.nl/agastats.php please get in
3ghs on my pool
http://findblocks.com/amiga/public/index.php?page=dashboard
February 28, 2018, 02:34:11 PM
Guys, i think i necesary more hashing power, im mining at http://coincave.nl/agastats.php please get in
February 28, 2018, 02:00:44 PM
I made some changes, corrected de seed nodes and a try to implement the digishield algorithm. I have it running, it connected well to 5 nodes. Some one could try it?
https://github.com/sonountaleban/amigacoin/pull/4/commits/49ef724cd7aa85c284afc4ffd3003aa4dc3be075
https://github.com/sonountaleban/amigacoin/pull/4/commits/49ef724cd7aa85c284afc4ffd3003aa4dc3be075
Jump to: