St.Bit
|
|
December 05, 2013, 01:59:12 AM |
|
does anyone know how many YAC will be minted total?
Many Thanks
It has POS (5% p.a.) so there is no limit in terms of total number of coins. Since PoW rewards depend on difficulty it's hard to predict how much will be generated. As rule of thumb I'd say 10million/yr for the first years, but that's a wild guess and impossible to predict precise.
|
|
|
|
tuukerX
Newbie
Offline
Activity: 8
Merit: 0
|
|
December 05, 2013, 04:23:29 AM |
|
I really hope YAC development goes well and will be synced with newer features from BTC and building more stable releases. YAC solution is quite good to be future proof.
Please sync qrcode function from BTC too.
|
|
|
|
Chris180Z
|
|
December 05, 2013, 10:21:38 PM |
|
IS anyone selling any YAC? Let me know. I don't know where to buy it.
|
|
|
|
|
Chris180Z
|
|
December 07, 2013, 02:02:22 AM |
|
I think i've tried everything. I simply cant mine with this, or get it to sync. I assume the original post relates to applying commands through command prompt? (ie yacoin-qt -gen)
|
|
|
|
|
rodeoric
Member
Offline
Activity: 89
Merit: 10
|
|
December 11, 2013, 03:17:50 PM |
|
Hello, my System is an i7 - 4770k @ 4,3 GH/z watercooled with an Windows 7 Extrem Edition. It seems like my GPU is detected and is working but it does not accept a single share, how can i fix this ? Best Regards rodeoric
|
|
|
|
|
sairon
Sr. Member
Offline
Activity: 406
Merit: 250
One does not simply mine Bitcoins
|
|
December 11, 2013, 06:57:43 PM |
|
Also, please note that you will get MUCH LOWER hashrates when you switch to the correct algorithm. This is NORMAL.
|
GPG key ID: 5E4F108A || BTC: 1hoardyponb9AMWhyA28DZb5n5g2bRY8v
|
|
|
bitdwarf
Sr. Member
Offline
Activity: 406
Merit: 250
The cryptocoin watcher
|
|
December 13, 2013, 04:34:26 PM |
|
Going up again. Did I miss any news?
|
𝖄𝖆𝖈: YF3feU4PNLHrjwa1zV63BcCdWVk5z6DAh5 · 𝕭𝖙𝖈: 12F78M4oaNmyGE5C25ZixarG2Nk6UBEqme Ɏ: "the altcoin for the everyman, where the sweat on one's brow can be used to cool one's overheating CPU" -- theprofileth
|
|
|
koguma
Member
Offline
Activity: 106
Merit: 10
|
|
January 04, 2014, 12:12:53 PM |
|
Hi All,
I grabbed the latest github sources and built the master branch. Running yacoind, I would say about 90% of the connections I see stuff like:
11/19/13 15:21:03 Moving 72.12.81.222:7688 to tried 11/19/13 15:21:03 receive version message: version 60005, blocks=294457, us=23.94.28.23:49332, them=72.12.81.222:7688, peer=72.12.81.222:7688 11/19/13 15:21:03 trying connection 81.17.30.114 lastseen=0.0hrs 11/19/13 15:21:03 socket recv flood control disconnect (10136 bytes)
Curious why that happens....
That's kinda expected during the initial block download. A workaround is adding "maxreceivebuffer=500000" into yacoin.conf. This was the best advice I've received all week. So many coins have issues downloading the blockchain because the maxreceivebuffer is too low. Is there a need for a pool?
|
|
|
|
sairon
Sr. Member
Offline
Activity: 406
Merit: 250
One does not simply mine Bitcoins
|
|
January 04, 2014, 12:16:04 PM |
|
Hi All,
I grabbed the latest github sources and built the master branch. Running yacoind, I would say about 90% of the connections I see stuff like:
11/19/13 15:21:03 Moving 72.12.81.222:7688 to tried 11/19/13 15:21:03 receive version message: version 60005, blocks=294457, us=23.94.28.23:49332, them=72.12.81.222:7688, peer=72.12.81.222:7688 11/19/13 15:21:03 trying connection 81.17.30.114 lastseen=0.0hrs 11/19/13 15:21:03 socket recv flood control disconnect (10136 bytes)
Curious why that happens....
That's kinda expected during the initial block download. A workaround is adding "maxreceivebuffer=500000" into yacoin.conf. This was the best advice I've received all week. So many coins have issues downloading the blockchain because the maxreceivebuffer is too low. Is there a need for a pool? You're welcome. A pool?
|
GPG key ID: 5E4F108A || BTC: 1hoardyponb9AMWhyA28DZb5n5g2bRY8v
|
|
|
CaptainBeck
|
|
January 09, 2014, 12:33:25 PM |
|
Hi, I cant get the Qt wallet to connect to any nodes. I;ve tried on multiple machines without fire walls. rpcuser=*** rpcpassword=*** rpcallowip=127.0.0.1 rpcport=3339 port=7688 daemon=1 server=1 addnode=62.210.189.139 addnode=78.21.9.49 addnode=76.115.8.101 addnode=124.149.56.205 addnode=178.130.36.81 addnode=82.6.77.126 addnode=106.187.55.212 addnode=81.202.104.33 addnode=84.200.17.178 addnode=88.204.169.242
This is my conf file in the appdata roaming folder.
|
|
|
|
CaptainBeck
|
|
January 09, 2014, 12:37:42 PM |
|
Final lk_max_locks is 537000, sufficient for (worst case) 11 blocks in a single transaction (up to a 5-deep reorganization) Loading block index... block.GetHash() == 0000060fc90618113cde415ead019a1052a9abc43afcccff38608ff8751353e5 block.hashMerkleRoot == 678b76419ff06676a591d3fa9d57d7f7b26d8021b7cc69dde925f39d4cf2244f CBlock(hash=0000060fc90618113cde, ver=1, hashPrevBlock=00000000000000000000, hashMerkleRoot=678b76419f, nTime=1367991220, nBits=1e0fffff, nNonce=127357, vtx=1, vchBlockSig=) Coinbase(hash=678b76419f, nTime=1367991200, ver=1, vin.size=1, vout.size=1, nLockTime=0) CTxIn(COutPoint(0000000000, 4294967295), coinbase 04ffff001d020f272e68747470733a2f2f626974636f696e74616c6b2e6f72672f696e6465782e7068703f746f7069633d313936313936) CTxOut(empty) vMerkleTree: 678b76419f SetBestChain: new best=0000060fc90618113cde height=0 trust=1 date=05/08/13 05:33:40 ResetSyncCheckpoint: pending for sync-checkpoint 00000019f67b00bc3482208d5b82393df96c648b510f24ab0d3318294a9bcde5 ResetSyncCheckpoint: sync-checkpoint reset to 0000060fc90618113cde415ead019a1052a9abc43afcccff38608ff8751353e5 block index 204ms Loading wallet... nFileVersion = 70200 Performing wallet upgrade to 60000 keypool added key 1, size=1 keypool added key 2, size=2 keypool added key 3, size=3 keypool added key 4, size=4 keypool added key 5, size=5 keypool added key 6, size=6 keypool added key 7, size=7 keypool added key 8, size=8 keypool added key 9, size=9 keypool added key 10, size=10 keypool added key 11, size=11 keypool added key 12, size=12 keypool added key 13, size=13 keypool added key 14, size=14 keypool added key 15, size=15 keypool added key 16, size=16 keypool added key 17, size=17 keypool added key 18, size=18 keypool added key 19, size=19 keypool added key 20, size=20 keypool added key 21, size=21 keypool added key 22, size=22 keypool added key 23, size=23 keypool added key 24, size=24 keypool added key 25, size=25 keypool added key 26, size=26 keypool added key 27, size=27 keypool added key 28, size=28 keypool added key 29, size=29 keypool added key 30, size=30 keypool added key 31, size=31 keypool added key 32, size=32 keypool added key 33, size=33 keypool added key 34, size=34 keypool added key 35, size=35 keypool added key 36, size=36 keypool added key 37, size=37 keypool added key 38, size=38 keypool added key 39, size=39 keypool added key 40, size=40 keypool added key 41, size=41 keypool added key 42, size=42 keypool added key 43, size=43 keypool added key 44, size=44 keypool added key 45, size=45 keypool added key 46, size=46 keypool added key 47, size=47 keypool added key 48, size=48 keypool added key 49, size=49 keypool added key 50, size=50 keypool added key 51, size=51 keypool added key 52, size=52 keypool added key 53, size=53 keypool added key 54, size=54 keypool added key 55, size=55 keypool added key 56, size=56 keypool added key 57, size=57 keypool added key 58, size=58 keypool added key 59, size=59 keypool added key 60, size=60 keypool added key 61, size=61 keypool added key 62, size=62 keypool added key 63, size=63 keypool added key 64, size=64 keypool added key 65, size=65 keypool added key 66, size=66 keypool added key 67, size=67 keypool added key 68, size=68 keypool added key 69, size=69 keypool added key 70, size=70 keypool added key 71, size=71 keypool added key 72, size=72 keypool added key 73, size=73 keypool added key 74, size=74 keypool added key 75, size=75 keypool added key 76, size=76 keypool added key 77, size=77 keypool added key 78, size=78 keypool added key 79, size=79 keypool added key 80, size=80 keypool added key 81, size=81 keypool added key 82, size=82 keypool added key 83, size=83 keypool added key 84, size=84 keypool added key 85, size=85 keypool added key 86, size=86 keypool added key 87, size=87 keypool added key 88, size=88 keypool added key 89, size=89 keypool added key 90, size=90 keypool added key 91, size=91 keypool added key 92, size=92 keypool added key 93, size=93 keypool added key 94, size=94 keypool added key 95, size=95 keypool added key 96, size=96 keypool added key 97, size=97 keypool added key 98, size=98 keypool added key 99, size=99 keypool added key 100, size=100 keypool added key 101, size=101 keypool keep 1 wallet 2493ms Loading addresses... ERROR: CAddrman::Read() : open failed Invalid or missing peers.dat; recreating Loaded 0 addresses from peers.dat 0ms mapBlockIndex.size() = 1 nBestHeight = 0 setKeyPool.size() = 100 mapWallet.size() = 0 mapAddressBook.size() = 1 Done loading send version message: version 60005, blocks=0, us=0.0.0.0:0, them=0.0.0.0:0, peer=127.0.0.1:0 refreshWallet DNS seeding disabled ThreadMapPort started ThreadIRCSeed started ThreadOpenConnections started ThreadMessageHandler started trying connection 82.211.30.212 lastseen=0.0hrs ThreadStakeMinter started ThreadSocketHandler started ThreadOpenAddedConnections started ThreadOpenAddedConnections exited CPUMiner started for proof-of-stake Flushed 0 addresses to peers.dat 23ms ipcThread started Flushing wallet.dat Flushed wallet.dat 41ms connection timeout connection timeout IRC connect failed IRC waiting 71 seconds to reconnect trying connection 81.17.30.114 lastseen=0.0hrs No valid UPnP IGDs found Flush(false) blkindex.dat refcount=0 blkindex.dat checkpoint ThreadMessageHandler exited ThreadSocketHandler exited blkindex.dat closed DBFlush(false) ended 45ms StopNode() ipcThread exited ThreadStakeMinter exiting, 0 threads remaining ThreadIRCSeed exited ThreadMapPort exited Flushed 0 addresses to peers.dat 31ms Flush(true) DBFlush(true) ended 0ms YACoin exited
select() for connection failed: 10038
This is the debug file produced
|
|
|
|
Thirtybird
|
|
January 09, 2014, 04:09:30 PM |
|
Please make sure you're using the latest wallet, which you can download off http://yacoin.org/. I know the seeds were different in the very first release. I know that this wallet works, even without any addnode lines in the config file because I don't have any and have 50+ connections in my wallet. with that said, here are the first three addresses in my peerinfo that allow inbound 89.151.191.81 194.190.198.22 5.104.106.18
|
|
|
|
sairon
Sr. Member
Offline
Activity: 406
Merit: 250
One does not simply mine Bitcoins
|
|
January 09, 2014, 04:17:30 PM |
|
Please make sure you're using the latest wallet, which you can download off http://yacoin.org/. I know the seeds were different in the very first release. I know that this wallet works, even without any addnode lines in the config file because I don't have any and have 50+ connections in my wallet. with that said, here are the first three addresses in my peerinfo that allow inbound 89.151.191.81 194.190.198.22 5.104.106.18 Nah, his problem is that he closed the wallet before it connected to irc (failed on first try, 71s delay before next attempt and then he closed it).
|
GPG key ID: 5E4F108A || BTC: 1hoardyponb9AMWhyA28DZb5n5g2bRY8v
|
|
|
CaptainBeck
|
|
January 09, 2014, 04:33:07 PM |
|
Sorry i posted the first one in my debug window rather than the last one. Here is what it is currently saying, ive still got the client open and nothing is happening. I've got the lastest client aswell straight from the website Final lk_max_locks is 537000, sufficient for (worst case) 11 blocks in a single transaction (up to a 5-deep reorganization) Bound to [::]:7688 Bound to 0.0.0.0:7688 Loading block index... LoadBlockIndex(): hashBestChain=0000060fc90618113cde height=0 trust=1 date=05/08/13 05:33:40 LoadBlockIndex(): synchronized checkpoint 0000060fc90618113cde415ead019a1052a9abc43afcccff38608ff8751353e5 Verifying last 0 blocks at level 1 block index 2ms Loading wallet... nFileVersion = 70200 wallet 559ms Loading addresses... Loaded 4 addresses from peers.dat 1ms mapBlockIndex.size() = 1 nBestHeight = 0 setKeyPool.size() = 100 mapWallet.size() = 0 mapAddressBook.size() = 1 ThreadRPCServer started send version message: version 60005, blocks=0, us=0.0.0.0:0, them=0.0.0.0:0, peer=127.0.0.1:0 Done loading refreshWallet AddLocal([2001:630:e4:42fc:ffff:ffff:fe9f:68a3]:7688,1) DNS seeding disabled ThreadSocketHandler started ThreadOpenAddedConnections started trying connection 62.210.189.139:7688 lastseen=358134.7hrs ThreadStakeMinter started CPUMiner started for proof-of-stake ThreadMessageHandler started ThreadMapPort started ThreadIRCSeed started ThreadOpenConnections started trying connection 82.211.30.212 lastseen=0.0hrs Flushed 4 addresses to peers.dat 26ms ipcThread started GetMyExternalIP() received [137.222.114.245] 137.222.114.245:0 GetMyExternalIP() returned 137.222.114.245 AddLocal(137.222.114.245:7688,5) connection timeout connection timeout connection timeout IRC connect failed IRC waiting 71 seconds to reconnect trying connection 78.21.9.49:7688 lastseen=358134.7hrs trying connection 81.200.241.54:7688 lastseen=300.9hrs No valid UPnP IGDs found connection timeout connection timeout trying connection 81.17.30.114 lastseen=0.0hrs trying connection 76.115.8.101:7688 lastseen=358134.7hrs connection timeout connection timeout trying connection 188.120.239.144:7688 lastseen=284.5hrs trying connection 124.149.56.205:7688 lastseen=358134.7hrs connection timeout trying connection 82.211.30.212 lastseen=0.0hrs connection timeout trying connection 178.130.36.81:7688 lastseen=358134.7hrs connection timeout trying connection 81.200.241.54:7688 lastseen=300.9hrs connection timeout trying connection 82.6.77.126:7688 lastseen=358134.7hrs connection timeout trying connection 81.17.30.114 lastseen=0.0hrs connection timeout trying connection 106.187.55.212:7688 lastseen=358134.7hrs connection timeout trying connection 188.120.239.144:7688 lastseen=284.5hrs connection timeout trying connection 81.202.104.33:7688 lastseen=358134.7hrs connection timeout trying connection 82.211.30.212 lastseen=0.0hrs connection timeout trying connection 84.200.17.178:7688 lastseen=358134.7hrs connection timeout trying connection 81.200.245.198:7688 lastseen=338.2hrs connection timeout trying connection 88.204.169.242:7688 lastseen=358134.7hrs connection timeout trying connection 81.17.30.114 lastseen=0.0hrs connection timeout connection timeout trying connection 188.120.239.144:7688 lastseen=284.5hrs connection timeout trying connection 82.211.30.212 lastseen=0.0hrs connection timeout trying connection 188.120.239.144:7688 lastseen=284.5hrs connection timeout trying connection 81.17.30.114 lastseen=0.0hrs connection timeout trying connection 188.120.239.144:7688 lastseen=284.5hrs connection timeout IRC connect failed IRC waiting 138 seconds to reconnect connection timeout trying connection 82.211.30.212 lastseen=0.0hrs connection timeout trying connection 81.200.241.51:7688 lastseen=314.6hrs connection timeout trying connection 81.17.30.114 lastseen=0.0hrs connection timeout Flushed 4 addresses to peers.dat 60ms trying connection 188.120.239.144:7688 lastseen=284.6hrs connection timeout trying connection 82.211.30.212 lastseen=0.0hrs connection timeout trying connection 81.200.241.51:7688 lastseen=314.6hrs connection timeout trying connection 81.17.30.114 lastseen=0.0hrs connection timeout trying connection 188.120.239.144:7688 lastseen=284.6hrs connection timeout trying connection 82.211.30.212 lastseen=0.0hrs connection timeout trying connection 188.120.239.144:7688 lastseen=284.6hrs connection timeout trying connection 81.17.30.114 lastseen=0.0hrs
|
|
|
|
Thirtybird
|
|
January 09, 2014, 04:38:31 PM |
|
Please make sure you're using the latest wallet, which you can download off http://yacoin.org/. I know the seeds were different in the very first release. I know that this wallet works, even without any addnode lines in the config file because I don't have any and have 50+ connections in my wallet. with that said, here are the first three addresses in my peerinfo that allow inbound 89.151.191.81 194.190.198.22 5.104.106.18 Nah, his problem is that he closed the wallet before it connected to irc (failed on first try, 71s delay before next attempt and then he closed it). You still aren't connecting to IRC for some reason.. try adding those nodes to get started and then figure out the irc connection problem... I just verified a fresh client with no known nodes can connect to IRC. Bringing up my peer list brought an interesting question up for me. getpeerinfo reports a subvers string, most of which were "/YACoin-WM:0.7.2/" - I couldn't find a command that would show my own subvers string? The 0.7.2 shows up in the file information, but I didn't see it in the application anywhere. On a side note, It appears there are still quite a few people running really old wallets (as Satoshi showed up a number of times)
|
|
|
|
CaptainBeck
|
|
January 09, 2014, 04:54:05 PM |
|
Nvm.... I put your three in at the start the start of my addnodes and its all working
Cheers for this.
|
|
|
|
Thirtybird
|
|
January 09, 2014, 04:58:53 PM |
|
peers info?? I;ve got peers.dat Ùæçå H¡ºÎ—CènZESäô‰—‘››‘jD1Ú¦ yCÛ» -¿R ÿÿ¼xï ÿÿ ù†½R ÿÿQÈñ3 ÿÿ `F¾R ÿÿQÈñ6 ÿÿ •:¼R ÿÿQÈõÆ ÿÿ ⠴ӵѬ]÷Ö}ŠÈ¶†Õ`ñ0Gå8J“ak?A9
Is what it says in there. getpeerinfo - it's a command in the debug console. peers.dat is a database file that contains peers you've connected to.
|
|
|
|
|