With the openCL miner I can find a block every 2 hours 40 minutes.
With the C miner it takes 5 hours 20 minutes.
With the javascript miner it takes a little over 2 days.
Amoveo ♥🧿
Previous messages
and point the miner at port 3011
To open the blockchain and see the height
Next messages
26 February 2018
Z
08:37
Zack
G
MH
09:24
Mandel Hoff
Ok, pool is up again. Node died and corrupted. Sync'd from 0 on first attempt with fresh clone worked.
Z
09:26
Zack
did you update? it should be propagating txs better now
09:27
thanks for restarting. hopefully we will start finding blocks again
G
09:28
Gonzalo
found!
Z
09:28
Zack
great
G
09:28
Gonzalo
8489
MH
09:28
Mandel Hoff
Yes, fresh clone with latest code. Thanks for working on the tx propagation issues.
G
09:30
Gonzalo
Mandel just curiosity, when your miner says:
FoundShare: bDiff:8346 sDiff:7912
H/S: 1304919 S:0 S/Hr:0
[-6,102,111,117,110,100,32,119,111,114,107]
09:30
is it because my miner found it? or the pool?
MH
09:31
Mandel Hoff
Your miner. Miner doesn't know any pool stats. Website dashboard shows any pool level metric.
G
09:32
Gonzalo
👍
09:33
wow this is funny, my cheap $5/month VPS just found a block as well, 8492
09:40
and again, 8495!
lw
G
09:41
Gonzalo
poor vps, so many hours without luck and now 2 blocks
09:43
Mandel's pool fee is 9,9% for testnet, don't know for mainnet
MH
09:44
Mandel Hoff
Probably same main net at 9.9% pool fee. Overtime, I expect it to be reduced significantly.
lw
09:45
lijun wang
expensive😢
Z
09:45
Zack
In reply to this message
my $5/month vps gets 0.2 mh/s, so it would take about 9 hours to find a block.
Maybe we are estimating difficulty wrong. It seems impossible for Gonzalo to find blocks so fast.
Maybe we are estimating difficulty wrong. It seems impossible for Gonzalo to find blocks so fast.
MH
09:50
Mandel Hoff
I agree 6,878,658,560 / 200,000 / 60 / 60 should be ~ 9 hours
G
09:53
Gonzalo
Well it depends. I believe these 2 blocks are the only ones I've found with this VPS in the last 24 hours
09:53
is it possible to verify?
09:53
BCGevClpitrspqZsxSpyctZvS0VDGlfxQJZPHs4qLtMD9HC6rOoovRNT0TVZ3l+CywEQmCEANhkxqB8RWdwwZVg=
MH
10:00
Mandel Hoff
If there was a bug in the hash-difficulty math, that would explain why my pool estimates miner speeds higher than they actually are. (This doesn't effect pool payouts, because it's even across the board.)
10:02
It would probably be in hash2integer or pair2sci functions
Z
10:20
Zack
In reply to this message
[6334,6338,6339,6340,6342,6349,6354,6356,6362,6365,6366,6372,6375,6385,6388,6389,7068,7108,7247,7268,7294,7471,8125,8491,8494]
10:23
block:all_mined_by(base64:decode("BCGevClpitrspqZsxSpyctZvS0VDGlfxQJZPHs4qLtMD9HC6rOoovRNT0TVZ3l+CywEQmCEANhkxqB8RWdwwZVg=")).I just pushed code for this. it takes about 10 minutes to scan only 8000 blocks on my old laptop.
G
10:24
Gonzalo
Anyway I would wait for the next 24 hours... just because I found two blocks almost consecutively this does not imply any bug.
Z
10:25
Zack
yeah, there was more than 300 blocks before that where you found none
G
10:26
Gonzalo
well maybe it was below the height, maybe.. who knows
Z
10:26
Zack
I know. I just pasted it above
10:26
6334,6338,6339,6340,6342,6349,6354,6356,6362,6365,6366,6372,6375,6385,6388,6389,7068,7108,7247,7268,7294,7471,8125,8491,8494]
These are the heights that you mined.
These are the heights that you mined.
10:27
looks like you found 25 blocks
MH
10:29
Mandel Hoff
No... I suspect a hash - diff bug. You start over on every new block. 9 hours starts over every block.
G
10:29
Gonzalo
👍 I will be checking for the next 27 hours (9x3)... If this VPS founds more than 3 blocks in that time maybe there's a bug. I don't think so
MH
10:29
Mandel Hoff
That would also explain exactly why I calculated gpu level hash rates when blocks were found fast
G
10:34
Gonzalo
In reply to this message
Ok maybe I'm wrong but I believe it still possible to find 2 consecutive blocks. 1 block at the end of this 9 hours lapse, the other jsut at the start of the next 9 hours time lapse
Z
10:34
Zack
that is the thing about randomness, it is hard to tell
G
10:34
Gonzalo
😂
Z
10:35
Zack
G
10:35
Gonzalo
10:35
hahah
10:35
so funny!
10:35
😂
Z
10:42
Zack
Here is how much time passed between Gonzalo's blocks. measured in 1/10ths of a second.
block:time_mining(X).
[366991130,29067,29248,2067,25748,76980,20094,13958,44558,21378,8957,26430,22533,65926,8383,925,1029988,46314,150817,59623,152447,264376,542113,703390,3850]
block:time_mining(X).
[366991130,29067,29248,2067,25748,76980,20094,13958,44558,21378,8957,26430,22533,65926,8383,925,1029988,46314,150817,59623,152447,264376,542113,703390,3850]
G
10:44
Gonzalo
wow nice
10:46
Now that the network is running smoother it would be better if we check this in the next 24/48 hours
G
11:32
Gonzalo
did not find a block in that periodIs this OK?
Found a block. 1
read nonce n is 2
nonce failed 2
read nonce n is 1
nonce failed 1
nonce 0 error
did not find a block in that period
Z
11:45
Zack
it looks like the amoveo c code failed to write the nonce in the directory it was supposed to write it in.
G
11:55
Gonzalo
👍
11:56
My cheap VPS found another block... 8524
12:07
Deleted Account
so i spent the day building my miner. small 1 gpu msi gtx 1050 i7-7800. all the good stuff is sold out haha for mining gear!
12:08
now i can try the open cl miner
Z
12:08
Zack
the openCL miner only works for cpu right now.
12:09
I will add gpu support eventually
12:09
Deleted Account
i know. that’s why i only got one gpu. buy later when it can be used. thanks
12:10
i couldn’t use the open cl miner on my vps. no gpu. so now i can get better hashing rate running opencl on my i7 cpu
12:11
upgrade as we go 😎
Z
12:11
Zack
you don't need a gpu to run the opencl software now. you do need to install some tools
12:12
I updated the readme today with some notes on how to install these tools
12:13
Deleted Account
no problem. needed to build a miner anyway better than renting vps for long term mining
12:16
i only have my laptop so not mining with that 24/7. now i can just run my small miner and upgrade as needed
14:07
Deleted Account
i just saw the command for blocks above awesome! block:all_mined_by(base64:decode("BCGevClpitrspqZsxSpyctZvS0VDGlfxQJZPHs4qLtMD9HC6rOoovRNT0TVZ3l+CywEQmCEANhkxqB8RWdwwZVg=")).
14:07
i was mining all day today, and didn't get a single block :(
14:09
the opencl miner gives me GCC: opencl error. i did download the opencl package I found, but not sure if it worked. also got an error ./amoveo_miner binary error
14:10
i reinstalled database from 0 and started mining opencl with my new computer 5 cores.. see if it make a difference at all tonight
DZ
Z
17:52
In reply to this message
Awesome. Do you have any notes on how to install? Should I change the instructions in the README?
Z
20:07
Zack
I added the command
block_absorber:recover(). which re-syncs the blockchain by reading the block files from your hard drive. This is useful after doing make prod-clean.
20:19
This makes it possible to torrent a zip file containing lots of blocks.
Torrenting is a lot faster than the protocol I made for downloading blocks, so this will get more useful as the blockchain gets longer.
Torrenting is a lot faster than the protocol I made for downloading blocks, so this will get more useful as the blockchain gets longer.
20:52
Deleted Account
How to check whether my node was added? I remember there was a command. But can’t find it anymore.
Z
20:54
Zack
peers:all(). lists everyone.my_ip:get(). gives your ip addresss.
21:09
After the recent updates to make block propagation and tx propagation faster, we are using a lot of bandwidth.
21:43
Deleted Account
i mined all night, and either my blocks are counting, or my miner isn't working.. my node is at top height
Z
21:44
Deleted Account
opencl miner says "did not find a block in that period" but I haven't actually seen it mine a block yet.
Z
21:48
Zack
In reply to this message
so how many mh/s is your miner?
maybe it is just not powerful enough to find blocks.
maybe it is just not powerful enough to find blocks.
21:49
I used
is your CPU going to 100%?
maybe the miner isn't compiling correctly, so it isn't doing anything.
make multi-quick to launch a test network on my laptop with lower difficulty. the opencl miner can connect to it and find blocks.is your CPU going to 100%?
maybe the miner isn't compiling correctly, so it isn't doing anything.
21:52
Deleted Account
I'm checking with c-miner now.. I'll try the opencl miner again later today
21:52
using new system for mining
Z
21:53
Zack
How many mh/s is your new system?
MH
21:54
Mandel Hoff
In reply to this message
Confirmed. I'm at about 8gb/day output and 4gb/day input bandwidth. Thank you for reporting this.
G
21:54
Gonzalo
Scott, remember to edit "miner.erl" on the c-miner to add all your cores
Z
21:56
this is c-miner
Z
21:56
Zack
So you should find a block every 2000 seconds or so. I think that is like 33 minutes
21:57
you didn't measure the opencl speed test?
22:03
Deleted Account
i couldn't
22:03
./amoveo_miner gave an error for opencl mining test
22:05
opencl looked like it was mining
Z
22:06
Zack
if the speed test doesn't work, then mining probably doesn't work either.
MH
22:07
If anyone is looking for business ideas, generate and sell Vanity Addresses:
Z
22:07
Zack
don't buy a vanity address. they probably kept your private key.
G
22:08
Gonzalo
That was me
22:08
😂
22:08
I'm doing a very ugly vanuty addres generator
22:08
vanity
Z
22:08
Zack
haha
MH
22:08
Mandel Hoff
True - fairly unsafe. But, hilarious and fun.
G
22:08
Gonzalo
just a do-while pubkey
22:10
wait, in 10 minutes time ;-)
Z
22:12
Zack
it is unsafe to let someone else generate your key for you, because they might keep a copy of the private key.
MH
22:12
Mandel Hoff
Yes, unsafe to buy them from someone. Safe to make your own.
G
22:13
Gonzalo
In reply to this message
Yes, this is true. But this is done on your browser, so no problem
MH
22:16
Mandel Hoff
It will be an effort to educate users not to load their keys in to untrusted site's browsers too. Zack's and my sites don't send the private keys to the server, but it would be very easy for someone to launch a site that looks exactly like a light wallet and sends the private key to the server.
M
MH
G
M
22:35
is it possible to connect to my own full node, or it works only with your pool?
G
22:35
Gonzalo
my cheap vps found another block (8596), this is the second one after the 2 consecutives yesterday
Z
G
22:36
Gonzalo
So 2 blocks after almost 13 hours
22:38
Well, Mandels Pool "stole" my block
22:39
It's strange because for a few seconds I saw my addres beside block 8596 on Mandels pool. Then changed to BKyLqCv...
Z
22:40
Zack
I think his pool and the interface might be running different amoveo full node back ends. Because sometimes one works and the other doesn't
MH
22:40
Mandel Hoff
My web page's "unconfirmed block" list is polled from other nodes, so my dashboard knows about that block but maybe my Amoveo node didn't.
Z
22:41
Zack
In reply to this message
Cool. Too bad it isn't open source, we could reuse stuff like that.
G
22:42
Gonzalo
ok but you should first ask your pool to see if there's a block there, isn't it?
22:43
well, just guessing
MH
22:43
Mandel Hoff
It just calls the get block api on peers. No magic. It uses pull rather than push though, which is bad for block propagation. It's just a hack to get uncofirmed block data.
G
22:43
Gonzalo
👍
Z
22:49
Zack
In reply to this message
ideally you would keep asking for their block:height, and only download a block when you know there is a new one.
22:50
or maybe we can get your ip on a list, so they send you new blocks when found.
MH
22:52
Mandel Hoff
Yes, I check height and only ask for a small number. I cache them too. It's not polling more lots of blocks and often. It's like 3 blocks every 5 minutes.
Z
22:52
Zack
sounds great
MH
22:52
Mandel Hoff
When block times go up, it'll even be less. Like 1 block per 10 min.
M
22:52
Mike
what's current real block height? my node is at 8596, while Mandel's is at 8600
22:53
only 4 blocks away, but not propagating for minutes...
Z
22:53
Zack
looks like 8600
MH
22:53
Mandel Hoff
Do you have the latest code from git? Lots of propagation changes in the last 24 hours.
M
22:54
I've updated code several hours ago, and now just got home
22:54
will try update now
22:55
yeah, there were some changes
MH
22:55
Mandel Hoff
Zack, do you have block hash - difficulty tests? I'm looking around github, but I'm struggling to find what I'm looking for.
22:56
Example Hash: 00FFFFFFFFFFFFFFFFFFFFFFFFFFFFFF - what's the difficulty score for this hash?
Z
22:58
Zack
In reply to this message
https://github.com/BumblebeeBat/pink_crypto/blob/master/src/pow.erl
There is a test on this page.
You can make small modifications to find out the answers to these questions. We should probably have more tests for this stuff.
There is a test on this page.
You can make small modifications to find out the answers to these questions. We should probably have more tests for this stuff.
MH
23:01
Mandel Hoff
Thank you.
M
23:41
Mike
Zack trying to mine on my full node (running on VPS) from my laptop via your C miner, getting the following:
23:41
"If you are running a solo-mining node, then this error may have happened because you need to turn on and sync your Amoveo node before you can mine. You can get it here: https://github.com/zack-bitcoin/amoveo
If this error happens while connected to the public mining node, then it can probably be safely ignored."
If this error happens while connected to the public mining node, then it can probably be safely ignored."
23:41
I am using 8081 port in miner.erl, is it right?
23:42
I have no pool installed on that vps, only running full node
Z
23:42
Zack
If they are on different computers, then you need to use a mining pool.
M
23:42
Mike
oh, ok
Z
23:42
Zack
if they are on the same computer, then you don't need a mining pool.
27 February 2018
MH
00:06
Mandel Hoff
Zack, I'm confused by hash2integer. I certainly could be wrong, but I'd expect these to hashes to have the same difficulty:
0x00FFFFFFFFFFFFFFFFFFFFFFFFFFFFFF
0x00EFFFFFFFFFFFFFFFFFFFFFFFFFFFFF
Is that right?
hash2integer gives the top one 0x8FF and the bottom one 0x8FE
0x00FFFFFFFFFFFFFFFFFFFFFFFFFFFFFF
0x00EFFFFFFFFFFFFFFFFFFFFFFFFFFFFF
Is that right?
hash2integer gives the top one 0x8FF and the bottom one 0x8FE
00:09
Deleted Account
update: the c-miner gave me 3 blocks in the last 2 hours or so
00:10
i think i need to install nivida drivers and then try installing opencl. which I will try today
Z
MH
00:14
Mandel Hoff
All 0's should be the highest diff, right?
P
00:16
Psdev
got a Segmentation fault like this... https://gist.github.com/p-s-dev/18ad33d7c971fe9c0b845dd33f1d3461
Z
MH
00:17
Mandel Hoff
These two hashes both give a diff of 0xF81 with hash2integer:
0x000102FFFFFFFFFFFFFFFFFFFFFFFFFF
0x007FFFFFFFFFFFFFFFFFFFFFFFFFFFFF
That seems incorrect, right?
0x000102FFFFFFFFFFFFFFFFFFFFFFFFFF
0x007FFFFFFFFFFFFFFFFFFFFFFFFFFFFF
That seems incorrect, right?
Z
00:17
Zack
the first byte of diff should be the number of leading zeros, and the next byte is the first non-zero byte
That dos seem incorrect.
That dos seem incorrect.
MH
00:18
Mandel Hoff
👍 Good. I thought I was going crazy until I found that counter-example.
Z
00:23
Zack
In reply to this message
test2() ->It works correctly when I do it.
%0x000102FFFFFFFFFFFFFFFFFFFFFFFFFF
A = <<0, 1, 2, 255, 255, 255, 255, 255>>,
%0x007FFFFFFFFFFFFFFFFFFFFFFFFFFFFF
B = <<0, 111, 255, 255, 255, 255, 255>>,
[hash2integer(A),
hash2integer(B)] == [3969,2527].%returns true.
00:24
The one with more leading zeros is a difficulty of almost 4000, and the one with less leading zeros has a difficulty of about 2500
MH
00:25
Mandel Hoff
Maybe this is just in the c-miner code then. Testing more.
Z
00:25
Zack
hash2integer makes an integer, not 2 bytes.
00:25
and you wrote 3 nibbles.
00:25
F81
00:28
In reply to this message
https://github.com/zack-bitcoin/amoveo-c-miner/blob/master/amoveo_pow.c#L202
you want this test then.
you want this test then.
P
00:34
Psdev
Can a node run without any in-bound ports open to other nodes? behind nat/firewall it will sync quick to "absorb block 8620" but then start to see a lot of "they are not accepting our blocks", "tx_pool_feeder died". Seem that if other nodes can't contact my node's port 8080, things go bad?
Z
00:36
Zack
In reply to this message
it works better if that port is open.
You probably cannot mine if the port is closed, because you wont find out about blocks quick enough.
"they are not accepting our blocks", "tx pool feeder died", neither of these are a problem.
As long as it is working, then you should ignore the errors.
You probably cannot mine if the port is closed, because you wont find out about blocks quick enough.
"they are not accepting our blocks", "tx pool feeder died", neither of these are a problem.
As long as it is working, then you should ignore the errors.
P
00:38
Psdev
thanks, ill keep trying. haven't got miner working yet
MH
00:52
Mandel Hoff
Ok, I think I broke something in my test app's hash2integer. Thank you for confirming the node's diff calc worked as expected.
Note: The c-miner crashes (yours and mine) if a user gets an all-0's hash, but that's crazy unlikely to happen.
(h[i] * 128) + (h[i + 1] / 2)
There's no check on h[i+1], so it goes beyond end of buffer for "all zeros" hash.
Note: The c-miner crashes (yours and mine) if a user gets an all-0's hash, but that's crazy unlikely to happen.
(h[i] * 128) + (h[i + 1] / 2)
There's no check on h[i+1], so it goes beyond end of buffer for "all zeros" hash.
Z
00:54
Zack
right, you got it.
00:55
the hash of the top bitcoin header:
0000000000000000001801d8c336b1f2a346d3a082638b38688d48c5e1ef502d
0000
0000
0000
0000
001801d8
looks like 9 bytes of 0s
0000000000000000001801d8c336b1f2a346d3a082638b38688d48c5e1ef502d
0000
0000
0000
0000
001801d8
looks like 9 bytes of 0s
00:56
so by Amoveo calculation, this would be around difficulty 18000
00:57
0x725A something like this in hex
01:27
Deleted Account
still getting error for speed test opencl, but the miner says it's looking for blocks
01:28
opencl miner is way faster than c-miner
01:28
if I can get it working anyway
Z
01:28
Zack
It is like 2x faster.
01:43
Deleted Account
looks like I'm going to have to reinstall ubuntu and start again with this opencl issue
01:44
ubuntu 16.04 LTS with a msi gtx 1050 graphics card.. if anyone's been able to get opencl to work then please tell me your secret. I'll try some more stuff today
G
03:10
Gonzalo
Zack, FYI I've got this on my cheap VPS node:
And this on the c-miner, same VPS:
they are not accepting our blocks.eheap_alloc: Cannot allocate 441485240 bytes of memory (of type "old_heap").
[End]
make[1]: Leaving directory '/home/amoveouser/amoveo'
amoveouser@amoveo-scaleway-01:~/amoveo$ they are not accepting our blocks.eheap_alloc: Cannot allocate 441485240 bytes of memory (of type "old_heap").
[End]
make[1]: Leaving directory '/home/amoveouser/amoveo'
amoveouser@amoveo-scaleway-01:~/amoveo$
And this on the c-miner, same VPS:
If you are running a solo-mining node, then this error may have happened because you need to turn on and sync your Amoveo node before you can mine. You can get it here: https://github.com/zack-bitcoin/amoveoLet me know if you need any log.
If this error happens while connected to the public mining node, then it can probably be safely ignored.** exception error: bad argument
in function list_to_binary/1
called as list_to_binary(ok)
in call from miner:unpack_mining_data/1 (miner.erl, line 20)
in call from miner:start_c_miners/1 (miner.erl, line 61)
2>
03:21
Mandel FYI, sometimes I see weird things on the timestamps:
03:21
03:21
Probably there's an explanation I ignore
MH
03:34
Mandel Hoff
Yes, that's a result of the dashboard getting unconfirmed blocks from other nodes and the confirmed blocks being local. Different nodes in different timezones, and I'm not accounting for that. I'm trying to store/display everything in GMT, but something is wrong somewhere.
G
03:35
Gonzalo
oh I understand now, thnaks
Z
03:58
Zack
In reply to this message
Thanks for sharing.
I haven't seen this error before, but I think it means that you ran out of ram. You had 4 gigabytes, which is a lot more than me.
I haven't seen this error before, but I think it means that you ran out of ram. You had 4 gigabytes, which is a lot more than me.
04:00
Deleted Account
Mandel i have been mining usings windows miner i get around 4 mhs. But the miner doesn't follow thread argument.
G
Z
G
04:02
Gonzalo
👍
04:03
Deleted Account
When i mine it uses 50 percent cpu it doesn't follow threads given to it for e.g (i gave it 2 threads and 8 threads individualy but it still utilizes at 50% cpu). So there is definitely room for 2x improvement.
04:08
And your pool is down
04:15
Deleted Account
In reply to this message
yah still working on it.. i had to completely reinstall ubuntu, last try resulting in my graphics cards not working AT ALL. but back now and thinking about next steps to get opencl to work with nivida / msi graphics cards
04:17
Deleted Account
In reply to this message
I have same laptop but with shitty card. I would be testing too but i used up my limited internet package. Well good luck ✌
G
04:32
Gonzalo
Based on Zacks wallet I have made a very ugly "Amoveo vanity address generator". Now you can have your cool BANANA address, or BATMAN, or BANG, BING, etc... But please, please, don't touch my BITCH! The BITCH is mine 😂
04:32
MH
04:34
Mandel Hoff
Nice!👍
04:35
In reply to this message
Yes, was practicing "database migration" and had an issue. No data was lost, but I did have to drop the pool a few minutes.
04:36
In reply to this message
How many cores do you have? Here's me with 2 threads and then changing to 7 threads. Seems right.
04:36
04:36
34% cpu with 2 threads, 93% with 7 threads.
Z
04:45
A lot of nodes fell out of sync. Can anyone share the crash.log so I can figure out what went wrong?
04:51
I made a bunch of changes to reduce bandwidth consumption today.
MH
04:55
Mandel Hoff
👍
04:56
Thank you! That saves me money immediately. Will update soon.
G
04:56
Gonzalo
Nice, I will update my nodes in a few minutes
MH
05:09
Mandel Hoff
Ok, I'm updated.
G
05:28
Gonzalo
Me too
MH
05:45
Mandel Hoff
Bandwidth updates look great so far. Thank you.
05:45
Z
05:46
Zack
great
05:55
Deleted Account
Z
05:56
Zack
oh, my mistake
05:56
Deleted Account
https://developer.nvidia.com/cuda-downloads < this link is on the page to get this to work
Z
05:56
Zack
I guess you might need a Nvideo CUDA SDK
05:57
Deleted Account
now i have this software installed, and nothings changed.. still getting the same error as before..so just giving you some info about this
Z
05:58
Zack
great. Thank you for this helpful error report
05:58
Deleted Account
so far I've tried a bunch of different ways, and this isn't my first time trying to get difficult software to work
05:59
Now.. is anyone else using linux and able to get opencl miner to work correctly?
Z
05:59
Zack
yes, opencl seems difficult to set up.
I guess it is mostly used by video gamers?
I guess it is mostly used by video gamers?
G
06:00
Gonzalo
Zack, two questions: 1) I did "git pull" without "make prod-clean" on my nodes, they are having troubles to catch the height. I have to do "sync:all" many times for them to update. Any idea?
Z
06:01
In reply to this message
with the new code, after you do "make prod-clean" it preserves your blocks.
When you turn it on, do not do
The node will automatically try and rescan the blocks from your hard drive before asking peers for blocks.
When you turn it on, do not do
sync:start().The node will automatically try and rescan the blocks from your hard drive before asking peers for blocks.
MH
06:02
Mandel Hoff
Scott, I have not attempted to run the opencl miner yet. I have installed cuda on windows a few times, but never opencl.
G
06:03
Gonzalo
2) After the git pull, my cheap VPS node is finding 1 block per minute! Looking at Mandels pool, none of them is being credited. http://piratepad.net/amoveoGonzalo
06:03
Deleted Account
just wondering if anyones been successful.. I've spent alot of time trying to get it to work, with the same gcc: error: openCL
G
06:04
Gonzalo
So I don't know what to do... reinstall the node or hire 10 cheap vps more ;-)
Z
06:05
Zack
In reply to this message
did you sync the blocks before mining?
If you are mining at height <2000, it makes sense you would find 1 per minute
If you are mining at height <2000, it makes sense you would find 1 per minute
MH
06:05
Mandel Hoff
That's why I was certain there was a bug in the hash-difficulty calculations earlier. There's no way single cpu should be finding block solutions at the observed rates. 🙈
06:06
Yes, maybe height is <2k. Good thought.
06:06
Deleted Account
In reply to this message
that happened to me couple days ago.. clear error.. had to reset everything
G
06:07
Gonzalo
In reply to this message
Im mining at height 86XX. Now my nodes are at 8692, like yours, but mandels is at 8698
06:10
In reply to this message
I still don't believe theres a bug, because my other nodes dont have this issue, and also Im not getting any VEO. Since yesterday, when I found 2 blocks, I've been rewarded only 1 VEO more
Z
G
MH
06:11
Mandel Hoff
Agreed - I haven't found a bug location yet, so my hunch was wrong.
G
Z
06:11
Zack
according to my laptop, these are the only 2 nodes that respond properly when I try to contact them:
[{{52,234,133,196},8080},{{159,89,106,253},8080}]
[{{52,234,133,196},8080},{{159,89,106,253},8080}]
G
06:11
Gonzalo
BCGevClpitrspqZsxSpyctZvS0VDGlfxQJZPHs4qLtMD9HC6rOoovRNT0TVZ3l+CywEQmCEANhkxqB8RWdwwZVg=
Z
G
06:12
Gonzalo
wich one?
Z
06:12
Zack
_build/prod/rel/amoveo_core/log/crash.log
G
06:12
Gonzalo
👍
Z
G
06:15
Now I'm testing with 3 nodes, did git pull on the 3 minutes ago... and all of them are at height 8692
06:29
Deleted Account
ok so I fixed an issue where /user/include/ didn't have CL/cl.h link.. by installing apt-get install opencl-headers so now CL/cl.h has a valid path to /user/include/ but it didn't fix the issue but was an issue
Z
06:33
Zack
In reply to this message
great! sounds like progress. ill make a note of this in that repository.
06:36
I think that reading the blocks off of my old fasioned disk-hard drive is slower than downloading them from my vps with a solid state hard drive from a different country.
G
06:37
Gonzalo
yeah probably
Z
06:37
Zack
In reply to this message
yes, we aren't receiving blocks when mandel finds them they way we should be
06:42
@Mandelhoff could you check something on your node for me?
Maybe the blocks aren't propagating from your pool because it didn't switch to normal mode automatically
sync_mode:check().Maybe the blocks aren't propagating from your pool because it didn't switch to normal mode automatically
06:42
I got rid of almost every case where blocks are being pulled, now they are just pushed.
But they only get pushed when we are in
But they only get pushed when we are in
normal mode.
06:43
This heavily improved the bandwidth consumption
G
06:43
Gonzalo
oh yes... I had to change to normal mode on all my nodes
06:43
that makes sense
Z
06:45
Zack
I think I need to improve this part of the code, but it would be nice to have a confirmation that it is actually broken before I fix it
MH
06:57
Mandel Hoff
Checking.
06:59
Z
06:59
Zack
Great. thank you for sharing this Mandel.
07:04
So I was wrong about why Mandel's node isn't sharing blocks.
Z
07:25
Zack
I notice that Mandel's node correctly pushed the most recent block to me when found. So at least it works sometimes.
I rewrote some code for pushing new blocks when you find them. This time I reused old tools that are confirmed working, rather than trying to write new tools.
So hopefully blocks will propagate better once Mandel updates.
I rewrote some code for pushing new blocks when you find them. This time I reused old tools that are confirmed working, rather than trying to write new tools.
So hopefully blocks will propagate better once Mandel updates.
07:25
Deleted Account
i dug as deep as I could in the opencl-miner code.. looks like it needs to be updated to work with ubuntu linux. but i'm no coder.. so I'll run the c-miner until Zack gives an update on the opencl-miner
Z
07:27
Zack
In reply to this message
Great. Thanks for the progress report.
I will boot up linux soon and try to fix it.
I will boot up linux soon and try to fix it.
MH
07:41
Mandel Hoff
Are there new updates I should pull down?
Z
07:41
Zack
yes
MH
07:45
Mandel Hoff
I'm updated now.
Z
07:45
Zack
cool
07:45
hopefully when the next block is mined, you will push the changes to the rest of us
07:46
or you could type the command to test immediately
07:46
sync:push_new_block(block:top()).
MH
07:47
Mandel Hoff
8720 just mined
Z
07:47
Zack
yes, and I didn't get it
07:48
I guess my fix didn't work.
07:49
oh right, you just turned on. so you might still be in
sync_mode:quick().
MH
07:52
Mandel Hoff
I did prod-restart and then commanded it back to normal.
07:52
Z
07:52
Zack
cool, thank you
07:59
once again, did not sync.
I will try to write some integration tests to test these situations out on a single computer.
I will try to write some integration tests to test these situations out on a single computer.
08:22
Deleted Account
08:22
For some reason it is not working on my pc
Z
08:23
Zack
I bet this is because Mandel just rebooted a couple times for testing. if you restart the miner, does it work?
08:24
Deleted Account
No i am getting 4 mhs on 1 core😂
Z
08:24
Zack
oh, i misunderstood
08:25
that seems impossibly fast
08:25
Deleted Account
its wrong my cpu usage is at 50 percent
08:25
It doesnt change even whem i give 8 instead of 1
08:27
And when the pool goes down and comes back miner takes alot of time to regain hash speed. It takes 10 min(estimate) to reach from .5 mhs to 4mhs. It should quickly pickup the speed.
08:29
Weird part is my cpu usage stays same while the hashrate increases. Maybe the taskbar is drunk😂.
MH
08:29
Mandel Hoff
Are you on a VM or VPS? Sometimes VMs with capped cpu can look like that. I had IT admins that capped my VM cpu once, and it was like that.
08:30
Deleted Account
No im mining on personal pc
MH
08:30
Mandel Hoff
Probably the reason it takes a long time to "speed back up" is that I'm measuring elapsed time even when Getwork fails, which is pretty dumb but not serious.
08:30
The getwork fail elapsed time is counting against your hashrate.
08:30
Can you give it more threads like 12?
08:31
Yes, 1 vs 8 - same cpu is very strange. I have no idea why.
08:32
Back later to check for updates. Offline a couple hours.
08:32
Deleted Account
No effect with 12 threads but if i run another instance of windows miner my total speed increases to 5.7 aproximate with 100 cpu usage.
08:34
08:37
In reply to this message
This could be it i cut the internet connection n turned it on and the miner started at 4mhs.
08:49
Deleted Account
block:all_mined_by(base64:decode("BKF9voxgoBJjwd3p+J2DFvXfMWiA2SijeZ350UGAEkfCoKueKIUlnTrIEnwMqoSDa8wpPc4XT1XFBiLubeq+k2s=")).
08:50
[6383,7007,7009,7010,7011,7028,7029,7030,7270,7271,
7272,7273,7274,7275,7276,7277,7278,7279,7280,7281,
7501,7502,7528,7531,8058,8061,8062,8064,8065|...]
7272,7273,7274,7275,7276,7277,7278,7279,7280,7281,
7501,7502,7528,7531,8058,8061,8062,8064,8065|...]
Z
08:50
Zack
they got a lot of the blocks. is that the mining pool?
08:50
Deleted Account
i mined 3 blocks after 8065 just a few hours ago according to my balance.. but don't show up
08:50
no.. that's me
08:51
the report is being cut off? not sure
Z
08:53
Zack
yes. erlang doesn't pollute your interface much by default.
You can make it display the entire thing like
too bad this will start the calculation over. If you had stored the result in variable
You can make it display the entire thing like
rp(block:all_mined_by(base64:decode("BKF9voxgoBJjwd3p+J2DFvXfMWiA2SijeZ350UGAEkfCoKueKIUlnTrIEnwMqoSDa8wpPc4XT1XFBiLubeq+k2s="))).too bad this will start the calculation over. If you had stored the result in variable
Z, then you could do rp(Z). and it would be quick.
08:54
Deleted Account
[6383,7007,7009,7010,7011,7028,7029,7030,7270,7271,
7272,7273,7274,7275,7276,7277,7278,7279,7280,7281,
7501,7502,7528,7531,8058,8061,8062,8064,8065,8100,
8117,8118,8119,8121,8122,8123,8124,8126,8127,8129,
8130,8136,8164,8165,8302,8322,8336,8605,8615,8620,
8654,8656,8657,8658]
7272,7273,7274,7275,7276,7277,7278,7279,7280,7281,
7501,7502,7528,7531,8058,8061,8062,8064,8065,8100,
8117,8118,8119,8121,8122,8123,8124,8126,8127,8129,
8130,8136,8164,8165,8302,8322,8336,8605,8615,8620,
8654,8656,8657,8658]
08:54
cool
08:55
is there a way to show the last 10 blocks or just the end?
Z
08:57
Zack
http://erlang.org/doc/man/lists.html#split-2
looks like it would store the first 10 elements of List into First.
{First, Tail} = lists:split(10, List).looks like it would store the first 10 elements of List into First.
08:58
http://erlang.org/doc/man/lists.html#reverse-1
looks like this would store a reverse order of List into List2.
List2 = lists:reverse(List). looks like this would store a reverse order of List into List2.
08:59
Deleted Account
alright looks like im learning erlang
08:59
just add that to my resume lo
08:59
lol
Z
08:59
Deleted Account
yah.. i'm going to need that one . thanks.
Z
09:11
Zack
My integration tests are all showing the blocks should be propagating.
09:12
Deleted Account
i just got 2 blocks
09:12
last 30 min
09:13
not sure if they are propagating but hope so
Z
09:14
Deleted Account
8727
09:14
always behind
Z
09:15
Zack
then your block can't be included.
09:17
Deleted Account
i just updated and restarted and did sync start a couple times
09:17
before i mean like an hour ago
09:17
he mined a bunch and i never caught up
09:31
zach and mandel are synched at 8740/8741. but I'm stuck at 8727
09:31
I'm not getting any new blocks
Z
09:37
Zack
yes
09:40
Deleted Account
Im having a bit of trouble getting the AmoveoMiningPool functioning. I had a node set up that is on at http://45.33.115.100:8080/wallet.html and also set up the https://github.com/zack-bitcoin/amoveo-mining-pool on the same server. I then tried to used the mandelhoff miner (https://github.com/Mandelhoff/AmoveoMinerCpu/) to connect to this server but received errors Any insights or suggestions for how to set up a mining pool to allow for other servers to send work to?
09:40
I am able to connect to amoveopool.com using this method just fine
09:41
So i think I'm not just setting up the mining pool correctly, and may be missing a step
09:41
incorrectly*
Z
09:42
Zack
Mandel's miner works differently. I don't think it can connect to the mining pool I wrote.
09:42
Mandel's mining pool is closed-source.
09:42
Deleted Account
okay, im not against using your miner
09:44
my understanding with your miner is i will replace the url in line 6 of https://github.com/zack-bitcoin/amoveo-c-miner/blob/master/miner.erl with the domain of my server http://45.33.115.100:8085/
09:44
and correct me if im wrong, but the workers will just reward all work to this node, and there is no tracking or distribution of the mined veo
Z
09:44
Zack
yes. and change the number of cores
09:45
yes, correct. all the reward goes to the pubkey on the amoveo full node.
09:45
Deleted Account
ok ill give it a shot now
09:47
is opencl-miner the current fastest cpu miner? (moreso than c miner)
Z
09:47
Zack
yes, but it is very difficult to install right now.
09:47
Deleted Account
what exchanges are we on
Z
09:47
Zack
the instructions aren't good
09:47
Deleted Account
ok ill stick with c miner for now then
09:47
at least until i get it working
Z
09:48
Zack
In reply to this message
https://www.reddit.com/r/AmoveoTrader/
I made a reddit group to find people to trade with.
I made a reddit group to find people to trade with.
09:48
Deleted Account
so theres no exchange at the moment
09:48
ok
09:54
Deleted Account
do i need amoveo.git even if im just running a worker and have the node elsewhere? seems I am running into an error running the script
09:54
root@localhost:~/amoveo-c-miner# sh build_ubuntu.sh
build_ubuntu.sh: 10: build_ubuntu.sh: erlc: not found
build_ubuntu.sh: 12: build_ubuntu.sh: erl: not found
build_ubuntu.sh: 10: build_ubuntu.sh: erlc: not found
build_ubuntu.sh: 12: build_ubuntu.sh: erl: not found
11:42
Deleted Account
my node seemed to quit working at 8727.. so I restarted at 0 and it seems like no one on the network is up to date.. everyone has different block heights
Z
11:42
Zack
yes.
11:47
Deleted Account
on the up side.. amoveo works better than IOTA lol
11:47
at least from what i've read 👍
Z
12:05
Deleted Account
So little people
12:39
Deleted Account
anyway to check my success connecting to the mining pool
12:39
im getting this response now: If you are running a solo-mining node, then this error may have happened because you need to turn on and sync your Amoveo node before you can mine. You can get it here: https://github.com/zack-bitcoin/amoveo
If this error happens while connected to the public mining node, then it can probably be safely ignored.
If this error happens while connected to the public mining node, then it can probably be safely ignored.
12:39
the mining pool should be connected, i suppose i can wait to see if i get any coins
Z
12:40
Zack
the mining pool uses port 8085
12:52
Deleted Account
right
Z
13:02
Zack
you can use
They use port 3030, 3020, and 3010
make multi-quick to turn on a small testnet of 3 nodes on the same computer. Then you can connect the mining pool to one of those nodes, and it will be easy to mine because the difficulty is low.They use port 3030, 3020, and 3010
13:06
Deleted Account
are you running a pool
Z
13:07
Zack
usually yes, but for the next few hours it wont be synced up, so the blocks you miner wont be included in the testnet chain.
13:11
Deleted Account
any comments on these warnings
13:11
~/amoveo-c-miner$ sh build_ubuntu.sh
miner.erl:99: Warning: variable 'E' is unused
miner.erl:110: Warning: no clause will ever match
Erlang/OTP 18 [erts-7.3] [source] [64-bit] [smp:4:4] [async-threads:10] [hipe] [kernel-poll:false]
miner.erl:99: Warning: variable 'E' is unused
miner.erl:110: Warning: no clause will ever match
Erlang/OTP 18 [erts-7.3] [source] [64-bit] [smp:4:4] [async-threads:10] [hipe] [kernel-poll:false]
Z
13:12
Zack
they can be ignored.
13:12
Deleted Account
server gave confusing response
Z
13:13
Zack
that means the mining pool is having trouble contacting your full node.
13:13
they need to be on the same computer
13:15
Deleted Account
i was actually experimenting with full node mining
13:15
I have a full node on this server, and used this in the miner.erl
13:15
-define(Peer, "http://localhost:8081/").%for a full node on same computer.
%-define(Peer, "http://localhost:8085/").%for a mining pool on the same computer.
%define(Peer, "http://159.89.106.253:8085/").%for a mining pool on the server.
%-define(Peer, "http://localhost:8085/").%for a mining pool on the same computer.
%define(Peer, "http://159.89.106.253:8085/").%for a mining pool on the server.
Z
13:15
Zack
I did some updated so that blocks should be propagating again.
The problem was that we were trying to talk to too many peers at once.
So I de-parallelized the process, and made it so you talk to one peer at a time.
I also added some fail-fast features, so if a peer isn't helpful, you immediately stop talking to them and don't waste more time.
Once Mandel updates, then the network should work a lot better.
The problem was that we were trying to talk to too many peers at once.
So I de-parallelized the process, and made it so you talk to one peer at a time.
I also added some fail-fast features, so if a peer isn't helpful, you immediately stop talking to them and don't waste more time.
Once Mandel updates, then the network should work a lot better.
13:16
In reply to this message
if your miner is on the same computer, then you don't need a mining pool.
13:16
Deleted Account
im only using amoveo and amoveo-c-miner in this case
Z
13:16
Zack
and they are on the same computer?
13:17
Deleted Account
yeah
Z
13:18
Zack
are you sure Amoveo is running?
13:18
is Amoveo fully synced?
Z
13:20
Zack
it looks like you have a corrupted database, because I am not sending you the recent blocks.
13:21
to fix the amoveo full node
api:off().
halt().
git pull
make prod-clean
make prod-restart
13:21
or you can start a test network which would allow you to mine more quickly and verify that it works
13:22
api:off().
halt().
git pull
make multi-quick
and point the miner at port 3011
To open the blockchain and see the height
make attach1
block:height().
13:45
Deleted Account
my height is less than their top header
could not get block 250 from peer [-7,[-7,64,137,240,136],8080]tx_pool_feeder died
could not get block 250 from peer [-7,[-7,64,137,240,136],8080]tx_pool_feeder died
Missy N joined group by link from Group
Z
18:10
Zack
After the changes yesterday, now sometimes we quickly run out of RAM and crash.
MH
19:25
Mandel Hoff
My node crashed overnight. I just tried a fresh clone and sync from 0. Sync stalled at 8684. Zack's node shows 8802. I'll try again in a couple hours.
G
19:26
Gonzalo
My nodes: stoped / 8824 / 8829 for a long time
Z
19:32
Zack
yes. the recovery by reading blocks from the hard drive was occasionally leaving us in a broken state.
19:44
I pushed a fix.
I think you will have to do
but it wont take long to rescan the blocks because you can read them from your hard drive.
I think you will have to do
make prod-cleanbut it wont take long to rescan the blocks because you can read them from your hard drive.
20:08
Deleted Account
I dont know what i have done but i have lost my balance. i had 2 blocks this morning (checked in Mandel Pool, my node and zacks node) and now i dont see any balance neither my full node nor zacks node. Can you figure out what could be?
20:08
pubkey BPFuy9IF7xKGyYwmedCNuY+epxKnzdK/UoUCmpasD366l3sttKyERyR2daHlaxc8IrzVEajSGwI3YL9VZrhbMsg=
Z
20:08
Deleted Account
ok thanks
Z
20:35
Zack
My node is up, and I think it's mining pool is working.
So the network is alive again.
So the network is alive again.
20:44
Deleted Account
the problem still remains
Z
20:45
Zack
you need to install the new version of the software.
about 32 blocks were lost. so maybe you wont get your block reward back.
about 32 blocks were lost. so maybe you wont get your block reward back.
20:46
Deleted Account
ok thanks.
Z
20:46
Zack
api:off().
halt().
git pull
make prod-clean
make prod-restart
20:47
Deleted Account
I have git pull and make prod-restart
Z
20:47
Zack
that might work too
20:51
Deleted Account
confirmed blocks lost
20:52
is your mining pool up? http://159.89.106.253:8085
20:55
i am starting playing with openCL and i cant get it to work. Log very strange, it is in loop? :126470197301283475284019883269908652836189911532790369567999873516800
server gave confusing response
server gave confusing response
Found a block. 2
found work
126470197301283475284019883269908652836189911532790369567999873516800
server gave confusing response
server gave confusing response
Found a block. 2
found work
126470197301283475284019883269908652836189911532790369567999873516800
server gave confusing response
server gave confusing response
server gave confusing response
Found a block. 2
found work
126470197301283475284019883269908652836189911532790369567999873516800
server gave confusing response
server gave confusing response
Found a block. 2
found work
126470197301283475284019883269908652836189911532790369567999873516800
server gave confusing response
Z
21:01
In reply to this message
Yes, the opencl one is very difficult to set up.
The one in C is much easier.
The one in C is much easier.
21:02
Deleted Account
ok, thanks
Z
21:03
Zack
3 days till main net launch.
Anyone want to guess what portion of the time the network will be available for the first month?
I guess it will be available 1 day out of 3.
Anyone want to guess what portion of the time the network will be available for the first month?
I guess it will be available 1 day out of 3.
21:05
Deleted Account
the test speed in openCL works great, but the miner gives loops messages, i will change to C miner
Z
21:07
Zack
that is good you got the speed test working.
If it says something above 10 mh/s, it is probably not actually working.
If it says something above 10 mh/s, it is probably not actually working.
21:07
Deleted Account
no, 2mhs
Z
21:08
Zack
cool, you got it to pass
21:08
Deleted Account
and the miner seems to work but is in a loop or something
Z
21:09
Zack
the miner is supposed to be in a loop. every time it finds work, or it fails to find work. then it starts over.
21:09
Deleted Account
yes but the messages are repeating with the same work:
21:09
server gave confusing response
server gave confusing response
Found a block. 2
found work
126470197301283475284019883269908652836189911532790369567999873516800
server gave confusing response
server gave confusing response
Found a block. 2
found work
126470197301283475284019883269908652836189911532790369567999873516800
server gave confusing response
server gave confusing response
Found a block. 2
found work
126470197301283475284019883269908652836189911532790369567999873516800
server gave confusing response
server gave confusing response
Found a block. 2
server gave confusing response
Found a block. 2
found work
126470197301283475284019883269908652836189911532790369567999873516800
server gave confusing response
server gave confusing response
Found a block. 2
found work
126470197301283475284019883269908652836189911532790369567999873516800
server gave confusing response
server gave confusing response
Found a block. 2
found work
126470197301283475284019883269908652836189911532790369567999873516800
server gave confusing response
server gave confusing response
Found a block. 2
21:09
once and again
Z
21:10
Zack
yes, that does seem like a bug
22:08
Deleted Account
ok.. updated node.. synch from 0, and now miner up and running.. lets see what happens. never boring
MH
22:16
Mandel Hoff
What is the right height? Zack's explorer shows 8802 and wallet shows 8834.
Z
22:17
Zack
I think we may have lost some blocks. hopefully they will be recovered from your node
MH
22:18
Mandel Hoff
I'm sync'd to 8802 but stalled out there.
22:18
Maybe that's the right height. I'm seeing some "could not get block 9052 from peer..." messages but still at 8802.
Z
22:18
Zack
so we probably lost some blocks.
We should be able to start mining from 8802, and eventually become longest.
but the light node will display wrong info until then.
We should be able to start mining from 8802, and eventually become longest.
but the light node will display wrong info until then.
MH
22:22
Mandel Hoff
Yes, my pool has confirmed blocks up to 8828, so probably did get to ~8834 before.
Z
22:23
Zack
cool
22:24
yes, headers go to 8834.
MH
22:28
Mandel Hoff
Pool up to 8804.
Z
22:28
Zack
Great. hopefully this means mining is working, and we verified that we can recover from an attack where someone makes headers and doesn't publish blocks.
22:29
and my node is at 8804 too. so it looks like propagation could be fixed.
MH
22:30
Mandel Hoff
👍
Z
22:33
Zack
I did not get 8805. so I guess it isn't perfect yet.
I hope it is good enough so it doesn't crash.
I hope it is good enough so it doesn't crash.
MH
22:35
Mandel Hoff
I turned on several miners, so lots of hash power thrown at my pool for a while here. Trying to push back to 8834 quick.
22:57
Deleted Account
i’m at the top height again. 🎉🎉
22:59
or maybe not 8834 showing on light node like zach and mandel
23:00
node reset and miner going sync 🙏
MH
23:04
Mandel Hoff
Mined up to 8841. Turning off my miners. Several others still using the pool, so it'll continue at normal speeds.
Z
23:06
Zack
mine is at 8841 as well. looking good
23:06
Thanks for the support Mandel
23:09
Deleted Account
8842
Z
23:12
Zack
8843
23:13
It seems to be staying in sync, and the bandwidth requirement is lower than before.
MH
23:55
Mandel Hoff
Zack, does github give you any Analytics about how big the community might be aside from the participants we know about from Telegram and reported issues?
28 February 2018
00:06
Deleted Account
so anyone else have errors.
block:height().
** exception error: undefined function gotblock:height/0
block:height().
** exception error: undefined function gotblock:height/0
00:06
miner:
** exception error: bad argument in function list_to_binary/1
called as list_to_binary(ok)
in call from miner:unpack_mining_data/1 (miner.erl, line 20)
in call from miner:start_c_miners/1 (miner.erl, line 61)
2>
** exception error: bad argument in function list_to_binary/1
called as list_to_binary(ok)
in call from miner:unpack_mining_data/1 (miner.erl, line 20)
in call from miner:start_c_miners/1 (miner.erl, line 61)
2>
00:19
restarting node and miner
00:20
stuck at 7503, waiting for more blocks
00:21
sync:start().
00:21
now getting more blocks
00:22
8834
00:24
stuck at 8834
00:24
mandel at 8856 and rising
00:27
everyone on default peer list is at different height, and I"m stuck at 8834 :😩
00:35
Deleted Account
@scottmatheina the same error. Zack do you think the bug in openCL could be solved in few days?
M
00:42
Deleted Account
when i do prod-clean I get rm .... block folders and then prod-restart redownloads the database from 0
00:43
Deleted Account
Regarding sync: absorb block 8660
regarding cminer error, i cant get working again
regarding cminer error, i cant get working again
00:45
miner solved, wash miner.erl problem
Z
01:36
Zack
In reply to this message
It tells me how many visitors and unique visitors per day. And which pages they look at most
01:38
In reply to this message
Correct.
It deletes the other database. So when you restart, the node re-reads the blocks and rebuilds the databases.
It deletes the other database. So when you restart, the node re-reads the blocks and rebuilds the databases.
01:42
Deleted Account
ok
01:42
In reply to this message
I just copied the error report from the terminal, so not sure about it..
Z
01:46
Zack
In reply to this message
the error message says that you tried to run
Maybe you had intended to run
gotblock:height().Maybe you had intended to run
block:height().
01:47
My node is still in sync a couple hours later. It looks like the other nodes are till giving me blocks correctly.
Things are going well.
Things are going well.
01:56
Deleted Account
In reply to this message
Maybe. pasted block:height(). restarted everything and wasn’t able to get synced so just letting the node run and see if it gets synced up eventually
01:59
you are synced with mandel but everyone else from your default peer list or my node is synching
Z
02:13
Deleted Account
yes.. git pull and make prod-clean
02:13
and sych:start a bunch of times
Z
02:14
Zack
typing
sync:start(). probably doesn't make a difference, since it syncs automatically
02:15
Deleted Account
yes no difference
02:16
the only thing i could change is more powerful server in different location
02:16
i’m running 2vCPU 4 gig server in singapore
Z
02:17
Zack
I have a 1 cpu, 0.5 gig server in germany
02:17
Deleted Account
so more than enough
02:18
where is mandel server?
02:18
same data center? lol
02:34
Deleted Account
never mind mandels server :
Continent: North America
Country: United States us flag
State/Region: Virginia
City: Boydton
Continent: North America
Country: United States us flag
State/Region: Virginia
City: Boydton
02:50
Deleted Account
so i started up a second node to see if this fresh node will synch up
02:52
ok my new node 192.241.144.151 synched up to the top height no issue at all.
02:53
my first node just won't synch at all 8834 stuck
Z
02:53
Zack
I identified a bug with pushing the new block.
If a peer responds with an ill-formatted response on a certain step, then you don't push the block to anyone else on the list.
If a peer responds with an ill-formatted response on a certain step, then you don't push the block to anyone else on the list.
02:55
In reply to this message
I bet this is because you fork-tolerance is too low, and you are on a fork from the rest of us.
Mandel rebuilt 32 blocks, but the fork tolerance is only 20.
So if you have the good blocks on your hard drive, then every time you sync from the hard drive you will be unable to sync with the network.
Deleting your blocks and redownloading should fix this.
Mandel rebuilt 32 blocks, but the fork tolerance is only 20.
So if you have the good blocks on your hard drive, then every time you sync from the hard drive you will be unable to sync with the network.
Deleting your blocks and redownloading should fix this.
02:55
or you could make the fork-tolerance bigger in the config file. bigger than 32.
02:56
Deleted Account
how to completely delete the database?
02:58
i think i'll just delete my old server, since i have the new one up and running.. easier
Z
02:58
Zack
rm -rf ./_build/prod/rel/amoveo_core/blocks/This would delete the blocks
mkdir ./_build/prd/rel/amoveo_core/blocks/
03:01
Deleted Account
ok thanks.. saved for later.. I have my new server up and mining at http://192.241.144.151:8080/wallet.html
03:02
found a block. now to see if it propogates
03:17
i had to manually synch:start(). to get my new node to synch with top height
03:17
8885 vs 8886
03:26
my node is working and miner, but always behind mandel
Z
G
03:34
Gonzalo
I had 2 nodes stuck at block:height:8668 and api:height:8834 for many hours
03:34
I tried git pull & restart and nothing changes
03:34
Deleted Account
i did the same.. you have to completely delete the database...
G
03:34
Gonzalo
I tried also make prod-clean and nothing changes
03:35
Yeah
03:35
Deleted Account
and start from 0
G
03:35
Gonzalo
I did a rm -rf amoveo and now is OK
03:35
yeah
03:35
thanks
03:35
Deleted Account
I just spun up a second server
G
03:35
Gonzalo
I saw
03:35
Deleted Account
and deleted my old one.. nuclear option 😊
G
03:36
Gonzalo
😁
Z
03:40
Zack
ok, I pushed the fixes for the problem that we had identified. Once Mandel updates, then blocks should be propagating properly all the time.
Additionally, this update reduces the bandwidth consumption, and I added a make command for deleting the blocks from your hard drive.
Additionally, this update reduces the bandwidth consumption, and I added a make command for deleting the blocks from your hard drive.
03:44
@Mandelhoff
Could you update?
Could you update?
G
03:47
Gonzalo
Ive got one node updated, doing another
03:48
height 8890
03:51
Deleted Account
Make prod clean
03:51
Git pull
Make prod-restart
Make prod-restart
03:51
and thiss
03:51
./_build/prod/rel/amoveo_core/bin/amoveo_core: 30: [: /home/usman/Downloads/amoveo: unexpected operator
./_build/prod/rel/amoveo_core/bin/amoveo_core: 31: cd: can't cd to /home/usman/Downloads/amoveo
Makefile:138: recipe for target 'go' failed
make: *** [go] Error 2
./_build/prod/rel/amoveo_core/bin/amoveo_core: 31: cd: can't cd to /home/usman/Downloads/amoveo
Makefile:138: recipe for target 'go' failed
make: *** [go] Error 2
G
03:53
Gonzalo
Zack I realized there's no warning about sync_mode anymore. Do we have to change to normal or just leave it?
Z
03:54
Zack
In reply to this message
I think this is a bug from when we renamed everything from ae_core to amoveo_core.
I think you should delete the entire folder, and re-download from github.
save your keys if you want to still have your veo after.
it might be
I think you should delete the entire folder, and re-download from github.
save your keys if you want to still have your veo after.
_build/prod/rel/amoveo_core/keys/keys.dbit might be
ae_core for you instead of amoveo_core
03:55
In reply to this message
It is usually fine to just leave it.
But if blocks are coming too fast, it might not switch to normal mode, so in that case it is better to manually do
I will do more updates soon, and then it will always be fine to leave it.
But if blocks are coming too fast, it might not switch to normal mode, so in that case it is better to manually do
sync_mode:normal().I will do more updates soon, and then it will always be fine to leave it.
G
03:55
Gonzalo
ok nice, thanks
03:59
_build/default/lib/dump/src/dump.erl:58: Warning: function fast_put/2 is unused
_build/default/lib/dump/src/file_manager.erl:59: Warning: function fast_write/3 is unused
===> Compiling jiffy
===> Missing artifact priv/jiffy.so
Makefile:135: recipe for target 'build' failed
make: *** [build] Error 1
_build/default/lib/dump/src/file_manager.erl:59: Warning: function fast_write/3 is unused
===> Compiling jiffy
===> Missing artifact priv/jiffy.so
Makefile:135: recipe for target 'build' failed
make: *** [build] Error 1
03:59
this is new
MH
04:01
Mandel Hoff
I'm updated to the latest now and in sync normal mode.
Z
04:01
Zack
it looks like your dependencies didn't get installed right
MH
04:02
Mandel Hoff
I'm at 8894
04:04
Deleted Account
i did git clone amoveo
04:04
and then make prod-restart and i still get the same error
Z
04:06
Zack
In reply to this message
ok, I am doing
git clone as well. I will try and reproduce the error.
04:07
Deleted Account
wait
Z
04:07
Zack
looks like jiffy compiled correctly.
04:08
The node is syncing blocks.
04:08
Deleted Account
yes i wiped amoveo from trash and changed my dir then i added sudo make prod-restart
04:08
and it is automatically syncing
Z
04:08
Zack
right. because git has a
.git folder that is hidden.
04:09
also
.gitignore, but the gitignore one doesn't cause these problems
04:10
Deleted Account
woah it is downloading 10 blocks per package nice
Z
04:11
Zack
it is downloading 50 at a time. it prints a message after verifying 10. that way there is less messages appearing.
04:12
Deleted Account
all synced up
Z
04:13
Zack
great
04:14
I confirmed that it is still having the same error as before. My fix did not work.
04:15
Deleted Account
(amoveo_core_prod@usman-GE70-2PC)1> normal:eventually will sync with these peers [-6,[-7,[-7,199,247,26,222],8080],[-7,[-7,159,65,182,117],8080],[-7,[-7,52,234,133,196],8080]]
syncing with this peer now [-7,[-7,64,137,240,136],8080]
trade peers
get their top header
already synced with this peer
eventually will sync with these peers [-6,[-7,[-7,34,229,146,193],8080],[-7,[-7,159,65,182,117],8080],[-7,[-7,52,234,133,196],8080]]
syncing with this peer now [-7,[-7,34,229,146,193],8080]
trade peers
get their top header
get headers
removing peer [-7,[-7,34,229,146,193],8080]
they are not accepting our blocks.eventually will sync with these peers [-6,[-7,[-7,159,89,106,253],8080],[-7,[-7,199,247,26,222],8080],[-7,[-7,52,234,133,196],8080]]
syncing with this peer now [-7,[-7,64,137,240,136],8080]
trade peers
get their top header
already synced with this peer
eventually will sync with these peers [-6,[-7,[-7,34,229,146,193],8080],[-7,[-7,159,65,182,117],8080],[-7,[-7,52,234,133,196],8080]]
syncing with this peer now [-7,[-7,34,229,146,193],8080]
trade peers
get their top header
get headers
removing peer [-7,[-7,34,229,146,193],8080]
they are not accepting our blocks.eventually will sync with these peers [-6,[-7,[-7,159,89,106,253],8080],[-7,[-7,199,247,26,222],8080],[-7,[-7,52,234,133,196],8080]]
04:16
is this the problem you are referring
04:16
they are not accepting our blocks
Z
04:16
Zack
I don't see a problem
04:16
no. I already wrote about it, and you can see what I wrote in recent pull requests.
04:16
Deleted Account
i want to check my balance but messages won't stop
OK
04:40
O K
In reply to this message
Hi guys, I know this has been asked but I'm not sure about recently -- what is GPU miner status?
04:41
I ... didn't mean to quote that
Z
OK
04:42
O K
Is it on github, is it a community effort?
Z
OK
04:43
O K
Thanks Zack
04:45
both the C miner and OpenCL miner on github claim to be the best miner currently available
Z
04:45
Zack
In reply to this message
thanks for pointing this out.
opencl is faster, but almost no one can get opencl to build.
opencl is faster, but almost no one can get opencl to build.
OK
04:45
O K
I will test
04:45
thank you
Z
04:53
Zack
i notice that when syncing, sometimes you can end up on that fork and get stuck.
So I increased the fork-tolerance to 40.
This increases the RAM requirement by about 20 megabytes, and allows us to recover from bigger forks.
So I increased the fork-tolerance to 40.
This increases the RAM requirement by about 20 megabytes, and allows us to recover from bigger forks.
G
05:03
Gonzalo
Great, this happened to one of my nodes
Z
05:14
Zack
I fixed the problem that was preventing blocks from being pushed to peers. Now the push_blocks thread doesn't crash.
And I identified a different problem stopping us from pushing blocks to peers. The push_blocks thread does try to send the blocks, but they aren't always accepted upon arrival.
And I identified a different problem stopping us from pushing blocks to peers. The push_blocks thread does try to send the blocks, but they aren't always accepted upon arrival.
05:17
Deleted Account
[8884,8897,8898,8899,8900,8901,8902] i got lots of blocks now 😃
Z
05:17
Zack
cool, thanks for mining. you have been enabling me to do some important tests
05:18
although, the info you are sharing is contradictory with this page: http://amoveopool.com/pool
05:18
Deleted Account
yes i know
05:19
i mine and never get credit
05:20
says i'm height 8903 with pool
05:20
but both mandel and I show the same blocks mined
Z
05:21
Zack
it is a confusing situation. maybe you are the same height on different forks?
maybe mandel's interface is displaying the wrong person did the mining?
maybe mandel's interface is displaying the wrong person did the mining?
05:21
Deleted Account
i'm on a new install, just 2 hours ago
05:22
normal mode.. so not sure what's up
05:24
BGO26LsWF9HYxj+IzoDW3WkRden/X1h5jNu8n3jPDasHf8isZnqYtcUC6yYD5z7AXej1h2c40pg1nxMvsKJCSG0=
05:25
my node address now
MH
05:33
Mandel Hoff
My "confirmed blocks" table comes from a local cache external to my amoveo node. If my amoveo node ever switches to another fork that contains different blocks for my pool's "confirmed blocks", then my table will not match my node. My "confirmed blocks" have a 5 block delay, which (I'd assume) should be enough delay to avoid that fork-switch.
05:33
Deleted Account
is there a way to see if a node will accept my blocks?
05:37
i do get ip won’t accept blocks alot
Z
06:02
Zack
In reply to this message
I managed to make a unit test that reproduces this issue. We are getting closer to a solution.
Z
06:44
Zack
oh, messing with fork_tolerance caused the problem.
Unfortunately, this is in the config file which only gets updated if you do a
Unfortunately, this is in the config file which only gets updated if you do a
make prod-clean or rm config/prod/sys.config while your node is off.
06:46
@Mandelhoff
Could you update it one last time? I think block propagation will work now.
And the one additional step I wrote above^
Could you update it one last time? I think block propagation will work now.
And the one additional step I wrote above^
MH
06:52
Mandel Hoff
Updated. I ran the rm. Here's a screenshot.
06:52
Z
06:54
Zack
Great. Thank you Mandel
G
06:57
Gonzalo
Im updating my nodes as well. Now sync_mode remains in quick, is this ok?
Z
06:58
Zack
it is supposed to switch itself to normal
06:58
after you have synced the blocks
06:58
but if we are finding blocks too fast, it doesn't work.
G
06:59
Gonzalo
ok, now Im synced but I'll check this again later
Z
07:02
Zack
it seems like it still isn't propagating blocks correctly.
07:09
I was wrong. deleting that file does not fix it.
I am having trouble figuring out how to change the config file being used by the node.
I am having trouble figuring out how to change the config file being used by the node.
G
07:12
Gonzalo
Mandel Im PMing you with two questions about your miners
Z
07:12
Zack
I think it is an issue with git
07:15
Deleted Account
i just deleted the entire folder, rebooted, and then git clone fresh
07:16
I'm back online with mandel again, and mining... so we will see
Z
07:16
Zack
rm config/sys.config.tmplThese are the commands I did to fix the sys.config template.
git reset --hard origin/master
07:17
I wasn't aware of this problem before. It is still confusing me why and how these config files are being treated differently from all the other files.
sys.config.tmpl is not in the .gitignore, as far as I can tell.
sys.config.tmpl is not in the .gitignore, as far as I can tell.
07:21
https://github.com/zack-bitcoin/amoveo/blob/master/config/sys.config.tmpl#L37
The value on github is correct. it should be 20.
40 is an error.
The value on github is correct. it should be 20.
40 is an error.
07:25
there is a problem with block_absorber:recover if you have stored blocks from both sides of a fork on your hard drive.
07:28
Deleted Account
got this data
["spend","BHMKEKtJHrSThav/b6TSoVcbHbvayWjb5b4qvfTR4HY1wGOCVGI/mjDlt6EjJjvZDJd3CFfciD69S52ivV90ILI=",70000000]
got this data
["spend","BHMKEKtJHrSThav/b6TSoVcbHbvayWjb5b4qvfTR4HY1wGOCVGI/mjDlt6EjJjvZDJd3CFfciD69S52ivV90ILI=",70000000]
got this data
["spend","BHMKEKtJHrSThav/b6TSoVcbHbvayWjb5b4qvfTR4HY1wGOCVGI/mjDlt6EjJjvZDJd3CFfciD69S52ivV90ILI=",70000000]
got this data
["spend","BHMKEKtJHrSThav/b6TSoVcbHbvayWjb5b4qvfTR4HY1wGOCVGI/mjDlt6EjJjvZDJd3CFfciD69S52ivV90ILI=",70000000]
got this data
["spend","BHMKEKtJHrSThav/b6TSoVcbHbvayWjb5b4qvfTR4HY1wGOCVGI/mjDlt6EjJjvZDJd3CFfciD69S52ivV90ILI=",70000000]
got this data
["spend","BHMKEKtJHrSThav/b6TSoVcbHbvayWjb5b4qvfTR4HY1wGOCVGI/mjDlt6EjJjvZDJd3CFfciD69S52ivV90ILI=",70000000]
got this data
["spend","BHMKEKtJHrSThav/b6TSoVcbHbvayWjb5b4qvfTR4HY1wGOCVGI/mjDlt6EjJjvZDJd3CFfciD69S52ivV90ILI=",70000000]
got this data
["spend","BHMKEKtJHrSThav/b6TSoVcbHbvayWjb5b4qvfTR4HY1wGOCVGI/mjDlt6EjJjvZDJd3CFfciD69S52ivV90ILI=",70000000]
got this data
["mining_data"]
mining data block hash is "kLFyJHe4WPYvA913ir/+wq/zfaxumGZQIKOu4N5ytvQ="
["spend","BHMKEKtJHrSThav/b6TSoVcbHbvayWjb5b4qvfTR4HY1wGOCVGI/mjDlt6EjJjvZDJd3CFfciD69S52ivV90ILI=",70000000]
got this data
["spend","BHMKEKtJHrSThav/b6TSoVcbHbvayWjb5b4qvfTR4HY1wGOCVGI/mjDlt6EjJjvZDJd3CFfciD69S52ivV90ILI=",70000000]
got this data
["spend","BHMKEKtJHrSThav/b6TSoVcbHbvayWjb5b4qvfTR4HY1wGOCVGI/mjDlt6EjJjvZDJd3CFfciD69S52ivV90ILI=",70000000]
got this data
["spend","BHMKEKtJHrSThav/b6TSoVcbHbvayWjb5b4qvfTR4HY1wGOCVGI/mjDlt6EjJjvZDJd3CFfciD69S52ivV90ILI=",70000000]
got this data
["spend","BHMKEKtJHrSThav/b6TSoVcbHbvayWjb5b4qvfTR4HY1wGOCVGI/mjDlt6EjJjvZDJd3CFfciD69S52ivV90ILI=",70000000]
got this data
["spend","BHMKEKtJHrSThav/b6TSoVcbHbvayWjb5b4qvfTR4HY1wGOCVGI/mjDlt6EjJjvZDJd3CFfciD69S52ivV90ILI=",70000000]
got this data
["spend","BHMKEKtJHrSThav/b6TSoVcbHbvayWjb5b4qvfTR4HY1wGOCVGI/mjDlt6EjJjvZDJd3CFfciD69S52ivV90ILI=",70000000]
got this data
["spend","BHMKEKtJHrSThav/b6TSoVcbHbvayWjb5b4qvfTR4HY1wGOCVGI/mjDlt6EjJjvZDJd3CFfciD69S52ivV90ILI=",70000000]
got this data
["mining_data"]
mining data block hash is "kLFyJHe4WPYvA913ir/+wq/zfaxumGZQIKOu4N5ytvQ="
07:29
with the update, it's now printing this a bunch of times
Z
07:29
Zack
oh, I forgot to comment out my print statments
07:30
thanks for mentioning
07:31
Deleted Account
sure.. this last block.. i was 1 behind mandel and didn't update, so it won't count
Z
08:53
Zack
I did the upgrade so now we automatically switch from quick mode to normal mode at the end of syncing.
08:53
and it works well even if blocks are happening quickly.
08:56
Deleted Account
What’s the current block height?
Z
08:56
Zack
8937
lw
08:56
lijun wang
mainnet ready?
08:57
Deleted Account
Z
08:57
Deleted Account
Curious about why would this happen
lw
08:57
lijun wang
just 2 days left
08:57
🙏
Z
08:59
Zack
In reply to this message
there was a 32-block fork today, and old code can get stuck on it.
api:off().Then wait for it to sync automatically.
halt().
git pull
make prod-clean
make prod-blocks
make prod-restart
08:59
Deleted Account
Ah. Thanks.
G
09:04
Gonzalo
Zack I just did it on one node, I looks like its creating its own blockchain from 0
09:05
c-miner founding blocks quite fast, and block:height on the node is 7
Z
09:05
Zack
@Mandelhoff
I was wrong before. The command I gave you did not fix the config file.
Since then I also updated the code, so it can tolerate a wider range of values in the config file.
I was hoping that you would update your node.
Here are the commands to get rid of the config file, but preserve your blocks and the software:
This should fix our problem in 2 different ways, so hopefully I wont have to keep bugging you to restart.
I was wrong before. The command I gave you did not fix the config file.
Since then I also updated the code, so it can tolerate a wider range of values in the config file.
I was hoping that you would update your node.
Here are the commands to get rid of the config file, but preserve your blocks and the software:
api:off().
halt().
git pull
rm config/sys.config.tmpl
git reset --hard origin/master
rm config/prod/sys.config
make prod-restart
This should fix our problem in 2 different ways, so hopefully I wont have to keep bugging you to restart.
G
09:06
Gonzalo
yes I suppose
09:06
I'll reset again
09:07
did it a thousand times so no problem 😁
09:07
haha pues eso!
Z
09:09
Zack
It is a little different now because the node is trying to save the blocks and recover from last time.
but because there was a small fork today of 32 blocks, it is possible that when you try to recover you end up on a fork.
but because there was a small fork today of 32 blocks, it is possible that when you try to recover you end up on a fork.
make prod-blocks deletes the blocks from your hard drive.
G
09:11
Gonzalo
👍
09:13
Deleted Account
ok i'm all sync'ed.. just waiting for pool to give me blocks falling behind
Z
09:14
Zack
me too
MH
09:19
Mandel Hoff
Ok, I'm updated.
09:19
09:20
Deleted Account
09:20
Is this normal?
Z
09:20
Zack
awesome. thank you Mandel
09:20
Deleted Account
I rebuild with latest code.
Z
09:21
Deleted Account
Only mining data shows now?
09:22
Used to have lots of info displayed
09:22
Deleted Account
i think zach cleaned up alot of the warnings
09:23
I'm getting the same now
09:23
mining data block hash is "s3RqESItgvIkH/+qsPO9u98knSlWMe6sNkwYYGMWj98="
many headers [-6,5001,8940]
mining data block hash is "tn4KD2FIg75EOiMVEtcHWvYv9PQNTepXWaWz2lXGqLs="
mining data block hash is "cKNgYTLVuGYThQgzUCW8OFw8rDhgoV9cw2KHyMDQhaE="
mining data block hash is "skbfkj5MfYmKiNfDtROeCGkAXxG5pwYrsI/gvA73PyA="
many headers [-6,5001,8940]
mining data block hash is "1PuPanCBzbdvVQ83/XEKsEazDKjzzXSG/ZwGJ5SfoQc="
mining data block hash is "hOp+DlrgFcq6jH/PD5nkzFUqgKSqq5IYMLa9xWiDTdY="
many headers [-6,5001,8940]
mining data block hash is "Powym8Y8Fp2kbSQGQqNJwA/E2mIhKWizUxyy1A+ISrw="
api:balance().
0
(amoveo_core_prod@anode)11> many headers [-6,5001,8940]
mining data block hash is "wqz4ofxc97ViBkbVj0oE03LuhPZ7fueaWHH67KBJDA8="
mining data block hash is "0TppOe+kJsyLTW6WCiSXPJ97Ie1TmUJ4KW2pUCjs7zE="
mining data block hash is "46iMCskhri/0qbpTKZhGFUC8A3OqGYUMD/HLOEI/N6o="
many headers [-6,5001,8940]
mining data block hash is "tn4KD2FIg75EOiMVEtcHWvYv9PQNTepXWaWz2lXGqLs="
mining data block hash is "cKNgYTLVuGYThQgzUCW8OFw8rDhgoV9cw2KHyMDQhaE="
mining data block hash is "skbfkj5MfYmKiNfDtROeCGkAXxG5pwYrsI/gvA73PyA="
many headers [-6,5001,8940]
mining data block hash is "1PuPanCBzbdvVQ83/XEKsEazDKjzzXSG/ZwGJ5SfoQc="
mining data block hash is "hOp+DlrgFcq6jH/PD5nkzFUqgKSqq5IYMLa9xWiDTdY="
many headers [-6,5001,8940]
mining data block hash is "Powym8Y8Fp2kbSQGQqNJwA/E2mIhKWizUxyy1A+ISrw="
api:balance().
0
(amoveo_core_prod@anode)11> many headers [-6,5001,8940]
mining data block hash is "wqz4ofxc97ViBkbVj0oE03LuhPZ7fueaWHH67KBJDA8="
mining data block hash is "0TppOe+kJsyLTW6WCiSXPJ97Ie1TmUJ4KW2pUCjs7zE="
mining data block hash is "46iMCskhri/0qbpTKZhGFUC8A3OqGYUMD/HLOEI/N6o="
09:24
Deleted Account
Thanks.
09:25
How often can you get a block
Z
09:26
Zack
the readme of the miner explains how to do a speed test of your hardware
09:26
a block is currently about 7 gigahashes
09:28
Deleted Account
2 behind pool now
Z
09:28
Zack
Mandel hasn't found any blocks since updating. Hopefully when he finds his next block, his node will automatically give us the recent blocks
09:30
Deleted Account
ok great hope so
MH
09:34
Mandel Hoff
Ha! My node isn't finding any blocks but everything "looks" fine.
09:36
Oh, there someone got one. Maybe me.
09:38
I'm 8940
09:38
pool is gaining a strong lead again :( 8945
MH
09:39
Mandel Hoff
I boosted my miners for increased testing. I'll turn them off in a few minutes.
09:44
so everyting looked great, and right after my miner found a block... the error report was massive..
Z
09:44
Zack
after you found the block you tried to push it to a bunch of peers. one of those peers tried giving you a bunch of invalid transactions.
09:45
Deleted Account
ok
MH
09:49
Mandel Hoff
My node crashed. make prod-go not bringing it back up. Trying stuff.
09:51
Deleted Account
hay.. zach.. you got your first spammer 🚀
09:52
now you know you made it 👍
09:59
Deleted Account
I remember there was a wallet address generator.
MH
09:59
Mandel Hoff
Ok, my node is up again at 8953 and available. I'll watch it a few minutes, but them I'm out for the night.
Z
10:00
Deleted Account
8953 mine for now.. not sure if get to keep it
G
MH
10:01
Mandel Hoff
What path to crash.log?
10:01
Deleted Account
pool has 8953 too :(
10:01
Deleted Account
Thanks.
Z
10:02
Deleted Account
8953,8954 I'm the longest now i think
G
Z
10:03
Deleted Account
don't know i don't get any of yours usually
10:05
8955 now
10:05
i got 8955 from a peer
10:06
at least i didn't mine
Z
10:06
Zack
I forced it to pull blocks from you, and it worked.
10:06
now I am pushing them to everyone else
G
10:07
Gonzalo
got it on 2 nodes
10:08
Deleted Account
can we mine on windows ?
10:08
Deleted Account
8956 > me...
Z
10:09
Zack
In reply to this message
It looks like Mandel is having trouble keeping the node up.
This is probably my fault for all the updates I did today, and for confusion on how config files are updated.
This is probably my fault for all the updates I did today, and for confusion on how config files are updated.
10:09
Deleted Account
In reply to this message
İ hope that i can mine when you launch the mainnet, thank you zack
MH
10:10
Mandel Hoff
A Windows miner can be found here:
https://github.com/Mandelhoff/AmoveoMinerCpu/releases
https://github.com/Mandelhoff/AmoveoMinerCpu/releases
10:16
Deleted Account
mandel is 8 ahead of me, and i'm not getting any of his blocks
10:16
never mind took a min
Z
10:17
Zack
I manually sent them to you.
10:17
Deleted Account
oh.. that's not going to work long term..... 😂
MH
10:18
Mandel Hoff
Turning off my miners. Will update in the morning as needed.
Z
10:19
Zack
ok. You were a lot of help today Mandel.
10:20
Deleted Account
i'm going to let my miner go through the night..
Z
10:21
Zack
cool
S
10:33
Sebsebzen
So is there gpu yet or not
10:33
And does gpu have large advantage?
Z
S
10:36
Sebsebzen
Thx zack
10:37
I’m super excited for this
Deleted joined group by link from Group
14:30
Deleted Account
lol
14:31
is cloud ming possible for amoveo, zack?
14:33
btw i'll get on refining the whitepaper translations this weekend
S
14:57
Sebsebzen
Zack any chance you will make it to Bangkok some time? Would love to organise a meetup. The crypto scene is quite vibrant here. Vitalik came for eth meeup last weekend.
15:55
Deleted Account
@Mandelhoff AmoveoCpuminer hashrate keeps dropping. Have you ever encountered this?
15:58
Zack Can I connect multiple miners to the full node without setting up a pool?
O
17:13
Oliver
Hi, quick question regarding mining via a pool: should I use the miner at https://github.com/zack-bitcoin/amoveo-c-miner or at https://github.com/Mandelhoff/AmoveoMinerCpu? What is the diff between the 2?
Z
17:40
In reply to this message
I think it will not work now.
They will keep changing the problem on each other, so the work is always invalid.
I might be able to add this as a feature in future releases, if you think it is important.
They will keep changing the problem on each other, so the work is always invalid.
I might be able to add this as a feature in future releases, if you think it is important.
17:41
In reply to this message
Depends which pool you want to connect to, and which OS you are using.
The one I made is only for Linux and Mac.
The one I made is only for Linux and Mac.
O
18:12
Oliver
@Mandelhoff How do I get paid for my work, is this automatic, how much work do I need to produce? (noob question, sorry, hopefully you understand what I mean). Total Hashes=1,381,892,096
MH
18:13
Mandel Hoff
What's your address? I'll check
O
18:13
Oliver
BDSf1mtgvhS38UxXdZpYEuvuij/45e5HMXe5VPGuue31nI1eQhZbHOFn7cvMRnr5Rza9ZC5/+HQg4oc4xWQYctw=
MH
18:17
Mandel Hoff
When your unpaid balance > 1.0, you get a payment sent to your address. You have 0.002 unpaid at the moment, which is not alot. Here are some other miner's to compare your hashes and balance against:
http://amoveopool.com/miner?address=BITCHx33q94k90RGFb2LgcFnZxalgT9djGA550jgrIR5E6iqo6TEBl3UMUz2OOr8firoejaptuOf%2BgEIGDgT%2Bbg%3D
http://amoveopool.com/miner?address=BPn5Ngt%2FYOL5rXZbytX%2FJ%2BcvagIa3KWtSY%2BvxJJoBHEm9EFnwOLhmRiS7ZdyZQHXjtnE299fU537ZBXhSPWFAqI%3D
http://amoveopool.com/miner?address=BITCHx33q94k90RGFb2LgcFnZxalgT9djGA550jgrIR5E6iqo6TEBl3UMUz2OOr8firoejaptuOf%2BgEIGDgT%2Bbg%3D
http://amoveopool.com/miner?address=BPn5Ngt%2FYOL5rXZbytX%2FJ%2BcvagIa3KWtSY%2BvxJJoBHEm9EFnwOLhmRiS7ZdyZQHXjtnE299fU537ZBXhSPWFAqI%3D
18:19
When network goes to main net, I expect the same hash rate for everyone will earn much less because there will be many more miners. Solo miners and my pool.
O
Z
18:21
Zack
I turned off the feature that reads blocks from your hard drive. I turned off the feature that keeps automatically pulling blocks at the beginning.
I made it so you cannot mine in sync_mode:quick().
Hopefully these changes will help with block propagation
I made it so you cannot mine in sync_mode:quick().
Hopefully these changes will help with block propagation
MH
18:21
Mandel Hoff
When a block is found by the pool, it keeps 9.9% of the veo. The rest is paid out (weighted) by difficulty to the miners that contributed hashes towards any blocks not yet credited.
18:23
So, if my pool doesn't find a block for 8 hours, all hashes for those 8 hours will divide up the veo in the next block that is found.
Z
18:56
Zack
48 hours till mainnet
19:13
Deleted Account
Still. I think discord is better for communication. Multi channels, search function, works well on PC...
Z
19:33
Deleted Account
19:33
It seems I got lucky.😃
Z
19:34
Zack
looks like you found a block. but my nodes height didn't increase
19:35
Deleted Account
No. Should be earlier. Current height?
Z
19:36
Scott is on a fork: http://192.241.144.151:8080/explorer.html
Since Mandel stopped mining, Scott's fork might win.
Since Mandel stopped mining, Scott's fork might win.
19:39
Deleted Account
Mine still 8976😂
19:42
Shall I manually sync my node from time to time?
19:44
I made my node run in normal mode earlier.
Z
20:41
Zack
I fixed some more bugs that were stopping blocks from propagating, and I fixed a bug that was making the mining pool crash.
20:42
Deleted Account
git pull + prod-restart and strange log: start keys
tx_pool- blockchain ready
starting secrets
start order book
Eshell V7.3 (abort with ^G)
(amoveo_core_prod@vmroa)1> talk_helper failed_connect 1
talk_helper failed_connect 1
talk_helper failed_connect 1
talk_helper failed_connect 1
tx_pool- blockchain ready
starting secrets
start order book
Eshell V7.3 (abort with ^G)
(amoveo_core_prod@vmroa)1> talk_helper failed_connect 1
talk_helper failed_connect 1
talk_helper failed_connect 1
talk_helper failed_connect 1
20:42
is the network on? i have missed smth?
Z
20:44
Zack
the network is on.
do
do
sync:start(). to download blocks.
20:45
Deleted Account
sync:start(). and:
20:45
(amoveo_core_prod@vmroa)4> sync:start().
[-7,[-7,162,218,209,18],8080]
[-7,[-7,159,65,182,117],8080]
eventually will sync with these peers [-6,[-7,[-7,64,137,240,136],8080]]
syncing with this peer now ok
[-7,[-7,64,137,240,136],8080](amoveo_core_prod@vmroa)5>
trade peers
get their top header
get headers
don't have a parent for this header
[-7,[-7,162,218,209,18],8080]
[-7,[-7,159,65,182,117],8080]
eventually will sync with these peers [-6,[-7,[-7,64,137,240,136],8080]]
syncing with this peer now ok
[-7,[-7,64,137,240,136],8080](amoveo_core_prod@vmroa)5>
trade peers
get their top header
get headers
don't have a parent for this header
20:45
and stops, is ok?
20:45
sorry stop thowing logs
20:53
make prod-clean make prod-restar sync:start() and now is syncing.
21:08
i have a full node with keys unlocked (sync with 9039), i have a mining pool and when i trie to atach mining pool,:Node is not running!
21:08
could you know why?
Z
21:08
Zack
you need to be in
sync_mode:normal() to run the mining pool.
21:08
Deleted Account
yes already
Z
21:09
Zack
redownload the mining pool, I just made some changes
21:09
git pull
21:09
Deleted Account
ok , i have git pull 20 mins ago, i will retry
Z
21:09
Zack
I made the changes <3 minutes ago
21:10
https://github.com/zack-bitcoin/amoveo-mining-pool/commits/master
actually 10 minutes.
actually 10 minutes.
21:11
Deleted Account
righ, thanks now is working!!
Z
21:11
Zack
I grew up in Mexican culture. We work the longest hours of any culture.
21:16
I will make spiritual incantations to help you
Z
21:17
Zack
I sleep twice a day
21:18
Deleted Account
Ok, good
21:18
I think you are a kind of genius
O
21:30
Oliver
@Mandelhoff is the pool down? I see I keep getting errors "ERROR: GetWork: 500 Sleep and retry...
"
"
Z
21:36
scott caught up. he is about to take the lead. Which means the rest of us will be on a dead fork.
MH
21:40
Mandel Hoff
Yes, my node died. Doing and update and restart now. Should be back soon.
Z
21:40
Zack
great. thanks Mandel
21:41
scott is one ahead. lets see what happens when Mandel comes back online
21:41
maybe he will join scott's fork
MH
21:42
Mandel Hoff
how many blogs ago did he fork?
21:42
*blocks ago
G
21:45
Gonzalo
Just absorbed block 9041 on one node
21:46
stuck at 9037 on another one
MH
21:46
Mandel Hoff
Nice - I just went 9041 too. That was propagation in seconds. Nice and fast.
G
21:46
Gonzalo
and syncing the third one, will see where stops at
MH
21:47
Mandel Hoff
I have miners on now. Let me know if it's a better test for me to take them down.
G
MH
21:48
Mandel Hoff
Yes, I kicked on miners and found blocks pretty fast. Difficulty is still pretty low.
21:49
Zack's node is at 9039 still.
Zbigniew Pekala joined group by link from Group
Z
21:57
Zack
It looks like a block was propagated to me, and then I tried propagating it to others. this is a good sign
22:00
now it looks like they are not propagating
22:03
now I got them. so it seems like it is propagating infrequently.
MH
22:21
Mandel Hoff
I was mining pretty hard, but my node was also pushing out data pretty hard in the last hour. Here's some details:
22:21
Z
22:30
Zack
is that in mb/s ??
22:31
can you send me the crash.log file?
_build/prod/rel/amoveo_core/log/crash.log
22:33
Deleted Account
does it mean that if I don't change anything but only pubkey, I can mine in the public mining pool?
Z
22:33
Zack
I think I get the chart now. 500 mb in only 2 hours is too much.
Deleted joined group by link from Group
Z
MH
22:35
Mandel Hoff
I think it's mb/minute. It was ~500mb output in ~45minutes.
22:35
It didn't crash. Do you still want the crash log?
Z
22:36
Zack
something is likely crashing if it is using up that much data
22:36
Deleted Account
MH
22:36
Mandel Hoff
ok
22:36
Deleted Account
Just like this? just change the pubkey only?
Z
MH
22:37
Mandel Hoff
2018-02-28 14:09:59 =ERROR REPORT====
Error in process <0.4257.0> on node amoveo_core_prod@litepro2 with exit value:
{{badmatch,false},[{base64,decode_binary,2,[{file,"base64.erl"},{line,212}]},{lists,map,2,[{file,"lists.erl"},{line,1238}]},{packer,unpack_helper,1,[{file,"/home/litepro2/amoveo/_build/default/lib/encrypter/src/packer.erl"},{line,31}]},{sync,remote_peer,2,[{file,"/home/litepro2/amoveo/_build/prod/lib/amoveo_core/src/consensus/sync.erl"},{line,138}]},{sync,push_new_block_helper,4,[{file,"/home/litepro2/amoveo/_build/prod/lib/amoveo_core/src/consensus/sync.erl"},{line,288}]}]}
2018-02-28 14:10:53 =ERROR REPORT====
Error in process <0.4270.0> on node amoveo_core_prod@litepro2 with exit value:
{{badmatch,false},[{base64,decode_binary,2,[{file,"base64.erl"},{line,212}]},{lists,map,2,[{file,"lists.erl"},{line,1238}]},{packer,unpack_helper,1,[{file,"/home/litepro2/amoveo/_build/default/lib/encrypter/src/packer.erl"},{line,31}]},{sync,remote_peer,2,[{file,"/home/litepro2/amoveo/_build/prod/lib/amoveo_core/src/consensus/sync.erl"},{line,138}]},{sync,push_new_block_helper,4,[{file,"/home/litepro2/amoveo/_build/prod/lib/amoveo_core/src/consensus/sync.erl"},{line,288}]}]}
2018-02-28 14:11:10 =ERROR REPORT====
Error in process <0.4277.0> on node amoveo_core_prod@litepro2 with exit value:
{{badmatch,false},[{base64,decode_binary,2,[{file,"base64.erl"},{line,212}]},{lists,map,2,[{file,"lists.erl"},{line,1238}]},{packer,unpack_helper,1,[{file,"/home/litepro2/amoveo/_build/default/lib/encrypter/src/packer.erl"},{line,31}]},{sync,remote_peer,2,[{file,"/home/litepro2/amoveo/_build/prod/lib/amoveo_core/src/consensus/sync.erl"},{line,138}]},{sync,push_new_block_helper,4,[{file,"/home/litepro2/amoveo/_build/prod/lib/amoveo_core/src/consensus/sync.erl"},{line,288}]}]}
2018-02-28 14:11:50 =ERROR REPORT====
** Generic server block_absorber terminating
Error in process <0.4257.0> on node amoveo_core_prod@litepro2 with exit value:
{{badmatch,false},[{base64,decode_binary,2,[{file,"base64.erl"},{line,212}]},{lists,map,2,[{file,"lists.erl"},{line,1238}]},{packer,unpack_helper,1,[{file,"/home/litepro2/amoveo/_build/default/lib/encrypter/src/packer.erl"},{line,31}]},{sync,remote_peer,2,[{file,"/home/litepro2/amoveo/_build/prod/lib/amoveo_core/src/consensus/sync.erl"},{line,138}]},{sync,push_new_block_helper,4,[{file,"/home/litepro2/amoveo/_build/prod/lib/amoveo_core/src/consensus/sync.erl"},{line,288}]}]}
2018-02-28 14:10:53 =ERROR REPORT====
Error in process <0.4270.0> on node amoveo_core_prod@litepro2 with exit value:
{{badmatch,false},[{base64,decode_binary,2,[{file,"base64.erl"},{line,212}]},{lists,map,2,[{file,"lists.erl"},{line,1238}]},{packer,unpack_helper,1,[{file,"/home/litepro2/amoveo/_build/default/lib/encrypter/src/packer.erl"},{line,31}]},{sync,remote_peer,2,[{file,"/home/litepro2/amoveo/_build/prod/lib/amoveo_core/src/consensus/sync.erl"},{line,138}]},{sync,push_new_block_helper,4,[{file,"/home/litepro2/amoveo/_build/prod/lib/amoveo_core/src/consensus/sync.erl"},{line,288}]}]}
2018-02-28 14:11:10 =ERROR REPORT====
Error in process <0.4277.0> on node amoveo_core_prod@litepro2 with exit value:
{{badmatch,false},[{base64,decode_binary,2,[{file,"base64.erl"},{line,212}]},{lists,map,2,[{file,"lists.erl"},{line,1238}]},{packer,unpack_helper,1,[{file,"/home/litepro2/amoveo/_build/default/lib/encrypter/src/packer.erl"},{line,31}]},{sync,remote_peer,2,[{file,"/home/litepro2/amoveo/_build/prod/lib/amoveo_core/src/consensus/sync.erl"},{line,138}]},{sync,push_new_block_helper,4,[{file,"/home/litepro2/amoveo/_build/prod/lib/amoveo_core/src/consensus/sync.erl"},{line,288}]}]}
2018-02-28 14:11:50 =ERROR REPORT====
** Generic server block_absorber terminating
22:37
Deleted Account
one more question, can I mine in several computers with just one pubkey?
Z
Deleted joined group by link from Group
22:43
Deleted Account
22:43
is that warning normal?
Z
22:45
I think I know the bandwidth problem.
When syncing, it is pushing an extra 20 blocks to make up for any possible fork.
I will fix it so it handles forks with headers instead. Then downloads the blocks for the winning headers.
When syncing, it is pushing an extra 20 blocks to make up for any possible fork.
I will fix it so it handles forks with headers instead. Then downloads the blocks for the winning headers.
23:02
Deleted Account
I ran miner 30min , and get nothing. is that normal?
Z
23:05
Zack
In reply to this message
Yes. A 1 megahashe per second miner would take about 2 hours to find a block.
My computer needs more than 6 hours.
My computer needs more than 6 hours.
23:07
Deleted Account
only 0.31 megahash per second
23:08
anybody knows the hashrate of the most fast AMD ryzen CPU?
Z
23:10
Zack
Wikipedia has a chart for bitcoin hash rates on different hardware.
The cpu code I wrote is about 6x slower than would be optimal.
The cpu code I wrote is about 6x slower than would be optimal.
23:21
Deleted Account
will there be more upgrades of mining software before the final launch?
Z
23:22
Zack
probably not.
23:23
Deleted Account
and do we need to restart the miner after the launch? or can I start the miner hours before launch and go to sleep?
Z
23:25
Zack
you will need to reinstall the amoveo full node at launch. the miner will probably stay the same.
23:25
Deleted Account
what if I link to the public mining pool.
MH
23:25
Mandel Hoff
I may update my miner, but it won't be speed or critical bugs. I have some logging issues. I think my miner may be fine to run overnight on launch. It continuously polls the pool for work, and it should just start working once the pool is up on main net. It'll just sit in that "Get work failed..." loop when the pool is down.
Z
23:26
Zack
In reply to this message
When I reboot for main net, it might cause your miner to turn off. so just turn it back on.
MH
23:29
Mandel Hoff
I estimate 20% chance I don't wake up for main net launch. 3am is sub-optimal. 🙈
23:31
Deleted Account
ok.. so is now a good time to update my node?
23:32
not sure if I won the fork war, but mandel is 3 ahead of me right now.
23:33
Deleted Account
23:33
found two blocks?
23:33
the balance is only 0.7
MH
23:33
Mandel Hoff
Scott, I saw your explorer and wallet height were different from each other by ~40 blocks. Not sure why or which would be more correct.
Z
23:34
Zack
In reply to this message
I think you won the fork war, and then afterwards started a second war. and you lost the second war.
23:36
Deleted Account
so.. my node says i got [8953,8954,8955,9031,9032,9033,9034,9035,9036,9037,9038,
9039,9040,9041,9042,9043,9044]
9039,9040,9041,9042,9043,9044]
23:37
i'll update and restart
23:40
looks like i'm 1 behind
23:41
i just restarted and synch:start() to make sure i tried to sync
23:43
api:height().
9088
(amoveo_core_prod@anode)5> block:height().
9045
9088
(amoveo_core_prod@anode)5> block:height().
9045
MH
23:44
Mandel Hoff
Yes, that's what I was seeing on your wallet versus explorer pages.
G
23:44
Gonzalo
My report 2 hours ago was: 9041 / syncing / 9037
23:45
Deleted Account
yah.. so my question is how do i fix it?... without reinstalling database
G
23:45
Gonzalo
My report now is: 9076 / 9087 / 9037
Z
23:48
Zack
11 AM GMT time. That is the time in England.
I think west coast USA is around 3 AM
I think west coast USA is around 3 AM
G
23:49
Gonzalo
great, so 12PM CET 👍
23:50
Deleted Account
api:height().
9088
(amoveo_core_prod@anode)5> block:height().
9045
Zack any recommended way to fix that isn't reinstalling database?
9088
(amoveo_core_prod@anode)5> block:height().
9045
Zack any recommended way to fix that isn't reinstalling database?
Z
23:51
Zack
The fork is pretty small. If you stop mining and wait for the next software update, you might recover then.
MH
Z
23:52
Zack
It will be a couple hours at least
23:59
Deleted Account
ok I updated my software just now. and see if i recover.. I can't mine right now anyway.. miner says i'm not sync'ed and no argument there lol
1 March 2018
00:00
Deleted Account
but it had all night to sync, so I have very low expectations I'll get to top height without a full database restore, but let's find out
00:36
Deleted Account
ok.. so prod-clean and sync:start(). fixed my issue
00:36
mining again
00:39
so fyi after my restart [8953,8954,8955] are the only block i got 😢
00:40
solved that question.. my fork wasn't adopted lol
Z
Laur joined group by link from Group
F
01:16
Francesco @ Simply
Is there any difference between connecting to the default mining pool vs Mandel's, apart from Mandel's higher fee?
Z
01:18
Zack
In reply to this message
Mandel s fee is lower.
Mandel has a binary for easy installation on Windows.
Zack s can be mined from javascript.
Mandel has a binary for easy installation on Windows.
Zack s can be mined from javascript.
F
01:20
Francesco @ Simply
In reply to this message
Oh ok. Mandel is 9.9% and yours is 1/650 of total reward, right?
Z
01:21
Zack
No. 1/650 is the transaction fee size.
My pool is currently charging 30% as a mining pool fee.
My pool is currently charging 30% as a mining pool fee.
F
01:43
Deleted Account
still not staying up to top height.. 7 behind
01:44
always creating dead fork
Z
01:58
Deleted Account
You’re right. it wasn’t sync’d before but it eventually got synced up. the block times are really fast
02:33
Deleted Account
block:height().
9108
(amoveo_core_prod@anode)10> api:height().
9108
pool is at 9115, and once again my mining won't count 😂
9108
(amoveo_core_prod@anode)10> api:height().
9108
pool is at 9115, and once again my mining won't count 😂
Z
02:48
Zack
It seems like pushing full blocks is too hard to do right.
So instead I think we should push headers, and only pull blocks.
So instead I think we should push headers, and only pull blocks.
03:04
Deleted Account
Is it possible to run a node in a raspberry pi?
Z
03:04
Zack
probably it is possible. I have not tried.
03:09
Deleted Account
I'll give it a shot and report back.
Z
03:10
Zack
cool
OK
03:47
O K
In reply to this message
I configured to point to mining pool and someone on here's public key just to experiment, and I have it reporting (the OpenCL miner) "did not find a block in that period" consistently, does that mean I succeeded in getting it to build?
03:49
I used this as opencl dependency: "sudo apt install mesa-opencl-icd"
03:57
Deleted Account
check your cpu usage.. i can get opencl to look like it's mining, but the cpu isn't doing anything..
03:57
Deleted Account
@ok i instaled this dependency and other ones and i get a strange log. it is contiually found blocks , several per second...i guess it is somthing wrong:
03:57
found work
42289484516997761935782156674787089608597309835103573969372526092286270581571
Found a block. 2
found work
71689819674929700952110969854228741276651396787695161507351088633516701461315
Found a block. 2
found work
19221529239211783629443838049964166735628280474445489793509596194422995495747
Found a block. 2
found work
85711517981037309562493895530933789053700174575516532939911727941705314020163
Found a block. 2
found work
26006221968006694157186617800889575439134275902525351268018176448003142527811
Found a block. 2
found work
101994780529988852760266448304517850008423402820880539958311489133278485228355
Found a block. 2
found work
63548188400397941372006085507028718744564909586650310733242417234146151312195
Found a block. 2
42289484516997761935782156674787089608597309835103573969372526092286270581571
Found a block. 2
found work
71689819674929700952110969854228741276651396787695161507351088633516701461315
Found a block. 2
found work
19221529239211783629443838049964166735628280474445489793509596194422995495747
Found a block. 2
found work
85711517981037309562493895530933789053700174575516532939911727941705314020163
Found a block. 2
found work
26006221968006694157186617800889575439134275902525351268018176448003142527811
Found a block. 2
found work
101994780529988852760266448304517850008423402820880539958311489133278485228355
Found a block. 2
found work
63548188400397941372006085507028718744564909586650310733242417234146151312195
Found a block. 2
Z
OK
04:09
for speed test
Z
04:09
Zack
so I guess it isn't working then
04:12
Deleted Account
Zack , the speed test is good, almos inmediatly (1 second more or less) with a 2mgh-2,5mgh but the log is like i show before. It is normal so many "found work" per second and no increasing the balance?
Z
04:13
Deleted Account
no, the openCL
Z
04:14
Zack
If you get it working, please write down the steps to help the rest of us.
04:14
I got it working on my mac, but it seems like it came already installed
04:16
Deleted Account
yes, is what i am looking for, but i dont know if i got working. I have made lot for installations and this is the final result. it seems to be ok? is what i ask for to tell what i have done
Z
04:31
Zack
2 mh/s would find a block once every 4000 seconds or so.
It is mining too fast, there is something wrong.
It is mining too fast, there is something wrong.
04:34
Deleted Account
the previous installation always shown the same work number like a loop. this try changes the work number but i guess is still somenthing wrong.. I will try again. I can give my apt list —installed to anyone who wants it but i would wait until it is working (i advice it is very long bc i have made lot of tries)
Z
04:34
Zack
it is only a cpu miner for now.
Eventually it will be upgraded to being a gpu miner, and then installation instructions will probably change again
Eventually it will be upgraded to being a gpu miner, and then installation instructions will probably change again
04:36
Deleted Account
Yes but the cminer is not working properly for me, only 0.24 mhs
Z
04:37
Zack
it is 0.33 mh on my laptop
Kenny joined group by link from Group
05:33
Deleted Account
last try with openCL : 3.3mhs in test but is always thowing the same as @potat_o
MH
06:02
Mandel Hoff
I made some amoveopool.com video tutorials. It's all very obvious stuff, but not a terrible place for new users to get started:
https://www.reddit.com/r/Amoveo/comments/8101ba/amoveopoolcom_video_tutorials/
https://www.reddit.com/r/Amoveo/comments/8101ba/amoveopoolcom_video_tutorials/
Z
06:02
Zack
cool
MH
06:02
Mandel Hoff
Has some basic "new wallet" and "mining tool" kick off examples.
06:27
Deleted Account
my miner died.. ** exception error: bad argument
in function list_to_binary/1
called as list_to_binary(ok)
in call from miner:unpack_mining_data/1 (miner.erl, line 20)
in call from miner:start_c_miners/1 (miner.erl, line 61)
in function list_to_binary/1
called as list_to_binary(ok)
in call from miner:unpack_mining_data/1 (miner.erl, line 20)
in call from miner:start_c_miners/1 (miner.erl, line 61)
06:30
restarting
06:42
ok back up to top height
I
07:36
Iridescence
Would anybody here be interested in a CUDA GPU miner for Amoveo?
Z
I
07:47
Iridescence
I can take a stab at it
Z
07:48
Zack
cool
G
I
07:49
Iridescence
I was thinking that it might be cool to work on GPU mining in the browser as well using WebGL
G
07:49
Gonzalo
My report, right now nodes at height 9076 / 9103 / 9100
08:03
Deleted Account
In reply to this message
Yes. I have cuda on my ubuntu machine with a gtx 1050 gpu and can’t get the opencl miner to work either
09:12
Deleted Account
how do i create a new public address from a private key? Or maybe I just need some clarification as I noticed using keys:new() produces a different address even with the same password
Z
09:14
Zack
In reply to this message
The password is for encrypting the key, not generating it.
The javascript light node allows you to generate keys deterministicly from a brain wallet. So it is using the code you want.
The javascript light node allows you to generate keys deterministicly from a brain wallet. So it is using the code you want.
09:14
The erlang crypto library does allow for what you are asking for.
09:17
Deleted Account
ah okay
lw
Z
09:21
I wrote the code to change how syncing work.
I put it into a different branch because this is a big change and I don't want to break it right before we launch.
https://github.com/zack-bitcoin/amoveo/tree/push_headers
I think this change will make block propagation better, and it will decrease bandwidth requirements.
I put it into a different branch because this is a big change and I don't want to break it right before we launch.
https://github.com/zack-bitcoin/amoveo/tree/push_headers
I think this change will make block propagation better, and it will decrease bandwidth requirements.
lw
09:21
lijun wang
What else to do for made pool??
G
09:21
Gonzalo
How do we update the nodes?
MH
09:23
Mandel Hoff
Would you like me to update? I'm fine with testing whatever you think is helpful.
Z
09:24
Zack
In reply to this message
Feel free to try out the other branch. We still aren't certain it will be better.
There are many different ways to switch branches. Use google to find a way that is comfortable for you.
I like to do
There are many different ways to switch branches. Use google to find a way that is comfortable for you.
I like to do
git pull --branch other_branch url-location .
MH
09:25
Mandel Hoff
If you want my pool on the master branch, that might make sense too. I'm open to suggestions.
Z
09:25
Zack
git clone --branch push_headers https://github.com/zack-bitcoin/amoveo.git .
09:26
In reply to this message
It would be ideal if we could test out the different code for the next hour or two, but be ready to switch back if it is broken
G
09:27
Gonzalo
thanks. Do we have to delete the amoveo folder before?
Z
09:27
Zack
I am making a second folder, and keeping the old folder as it is.
09:27
it is also possible to have both version installed in the same folder, and use git to switch branches, but I am not good at doing that.
G
09:27
Gonzalo
nice, Im waiting for you
Z
09:27
Zack
you are waiting for what?
09:28
I already published it.
MH
09:28
Mandel Hoff
Ok, I'll try to run the new branch update in about 15 minutes.
Z
09:30
Zack
https://github.com/zack-bitcoin/amoveo/blob/push_headers/docs/getting-started/sync.md
It comes with different instructions on syncing the blockchain
It comes with different instructions on syncing the blockchain
G
Z
G
09:37
Gonzalo
Im running it now, only repeats "sync cron"
Z
09:38
sync:start().
G
09:39
Gonzalo
sure thx
MH
09:47
Mandel Hoff
Sync in progress on branch version.
Z
09:48
Zack
cool
09:48
somehow someone forwarded a header to me, and my node is staying in sync
MH
10:01
Mandel Hoff
Sync stopped at 8623. I tried to get_headers from your node but this:
10:01
G
10:01
Gonzalo
mine stoped at 4559
Z
10:01
Zack
sync:start().
MH
10:01
Mandel Hoff
Your documentation has this, which has an extra {
10:01
sync:get_headers({{1,2,3,4}, 8080).
Z
10:01
Zack
oh, thank you for noticing
MH
10:01
Mandel Hoff
I've done sync:start(). about 8 times. Still trying
Z
10:04
Zack
it seems pretty stuck. I guess the new code is worse.
MH
10:06
Mandel Hoff
Ok, where? After the 8080?
Z
10:06
Zack
yes
10:07
sync:get_headers({{159,89,106,253}, 8080}).
10:07
If you are further behind than fork_tolerance (which is about 20 right now), then I can't push the headers to you
MH
10:08
Mandel Hoff
That get_headers command was accepted, but didn't advance my sync.
10:08
10:09
Sure - try to push to me. I'm still at that 52.something IP address. I can find it if needed.
10:09
10:09
... so lazy.
10:10
10:10
Pretty sure my branch node is behind you by >20 blocks.
Z
10:11
Zack
yes, im on 9197
G
10:11
Gonzalo
absorb block 9100
absorb block 9110
sync cron
sync cron
sync cron
sync cron
sync cron
could not get block 9329 from peer [-7,[-7,34,229,146,193],8080]sync cron
sync cron
sync cron
10:11
Now at height 9117
Z
10:11
Zack
looks like Gonzalo is almost synced up
10:12
I wonder why Mandel is so stuck. Maybe send me the crash.log file so I can learn what is wrong
MH
10:14
Mandel Hoff
2018-03-01 01:46:54 =ERROR REPORT====
Error in process <0.999.0> on node amoveo_core_prod@litepro2 with exit value:
{[{reason,{badrecord,block}},{mfa,{int_handler,handle,2}},{stacktrace,[{api,work,2,[{file,"/home/litepro2/amoveo/_build/prod/lib/amoveo_http/src/api.erl"},{line,457}]},{int_handler,doit,1,[{file,"/home/litepro2/amoveo/_build/prod/lib/amoveo_http/src/int_handler.erl"},{line,29}]},{int_handler,handle,2,[{file,"/home/litepro2/amoveo/_build/prod/lib/amoveo_http/src/int_handler.erl"},{line,16}]},{cowboy_handler,handler_handle,4,[{file,"/home/litepro2/amoveo/_build/default/lib/cowboy/src/cowboy_handler.erl"},{line,111}]},{cowboy_protocol,execute,4,[{file,"/home/litepro2/amoveo/_build/default/lib/cowboy/src/cowboy_protocol.erl"},{line,442}]}]},{req,[{socket,#Port<0.1773>},{transport,ranch_tcp},{connection,keepalive},{pid,<0.999.0>},{method,<<"POST">>},{version,'HTTP/1.1'},{peer,{{127,0,0,1},34005}},{host,<<"localhost">>},{host_info,undefined},{port,8081},{path,<<"/">>},{path_info,undefined},{qs,<<>>},{qs_vals,undefined},{bindings,[]},{headers,[{<<"content-type">>,<<"application/octet-stream">>},{<<"content-length">>,<<"57">>},{<<"te">>,<<>>},{<<"host">>,<<"localhost:8081">>},{<<"connection">>,<<"keep-alive">>}]},{p_headers,[{<<"connection">>,[<<"keep-alive">>]}]},{cookies,undefined},{meta,[]},{body_state,waiting},{buffer,<<"[\"work\",\"TiLwqM1FYW7ggNnqvEa5QOJvTLl8hI90lmfgyrsSRmI=\",0]">>},{multipart,undefined},{resp_compress,false},{resp_state,waiting},{resp_headers,[]},{resp_body,<<>>},{onresponse,undefined}]},{state,no_state}],[{cowboy_protocol,execute,4,[{file,"/home/litepro2/amoveo/_build/default/lib/cowboy/src/cowboy_protocol.erl"},{line,442}]}]}
2018-03-01 01:46:54 =ERROR REPORT====
Ranch listener http_internal had connection process started with cowboy_protocol:start_link/4 at <0.999.0> exit with reason: {[{reason,{badrecord,block}},{mfa,{int_handler,handle,2}},{stacktrace,[{api,work,2,[{file,"/home/litepro2/amoveo/_build/prod/lib/amoveo_http/src/api.erl"},{line,457}]},{int_handler,doit,1,[{file,"/home/litepro2/amoveo/_build/prod/lib/amoveo_http/src/int_handler.erl"},{line,29}]},{int_handler,handle,2,[{file,"/home/litepro2/amoveo/_build/prod/lib/amoveo_http/src/int_handler.erl"},{line,16}]},{cowboy_handler,handler_handle,4,[{file,"/home/litepro2/amoveo/_build/default/lib/cowboy/src/cowboy_handler.erl"},{line,111}]},{cowboy_protocol,execute,4,[{file,"/home/litepro2/amoveo/_build/default/lib/cowboy/src/cowboy_protocol.erl"},{line,442}]}]},{req,[{socket,#Port<0.1773>},{transport,ranch_tcp},{connection,keepalive},{pid,<0.999.0>},{method,<<"POST">>},{version,'HTTP/1.1'},{peer,{{127,0,0,1},34005}},{host,<<"localhost">>},{host_info,undefined},{port,8081},{path,<<"/">>},{path_info,undefined},{qs,<<>>},{qs_vals,undefined},{bindings,[]},{headers,[{<<"content-type">>,<<"application/octet-stream">>},{<<"content-length">>,<<"57">>},{<<"te">>,<<>>},{<<"host">>,<<"localhost:8081">>},{<<"connection">>,<<"keep-alive">>}]},{p_headers,[{<<"connection">>,[<<"keep-alive">>]}]},{cookies,undefined},{meta,[]},{body_state,waiting},{buffer,<<"[\"work\",\"TiLwqM1FYW7ggNnqvEa5QOJvTLl8hI90lmfgyrsSRmI=\",0]">>},{multipart,undefined},{resp_compress,false},{resp_state,waiting},{resp_headers,[]},{resp_body,<<>>},{onresponse,undefined}]},{state,no_state}],[{cowboy_protocol,execute,4,[{file,"/home/litepro2/amoveo/_build/default/lib/cowboy/src/cowboy_protocol.erl"},{line,442}]}]}
Error in process <0.999.0> on node amoveo_core_prod@litepro2 with exit value:
{[{reason,{badrecord,block}},{mfa,{int_handler,handle,2}},{stacktrace,[{api,work,2,[{file,"/home/litepro2/amoveo/_build/prod/lib/amoveo_http/src/api.erl"},{line,457}]},{int_handler,doit,1,[{file,"/home/litepro2/amoveo/_build/prod/lib/amoveo_http/src/int_handler.erl"},{line,29}]},{int_handler,handle,2,[{file,"/home/litepro2/amoveo/_build/prod/lib/amoveo_http/src/int_handler.erl"},{line,16}]},{cowboy_handler,handler_handle,4,[{file,"/home/litepro2/amoveo/_build/default/lib/cowboy/src/cowboy_handler.erl"},{line,111}]},{cowboy_protocol,execute,4,[{file,"/home/litepro2/amoveo/_build/default/lib/cowboy/src/cowboy_protocol.erl"},{line,442}]}]},{req,[{socket,#Port<0.1773>},{transport,ranch_tcp},{connection,keepalive},{pid,<0.999.0>},{method,<<"POST">>},{version,'HTTP/1.1'},{peer,{{127,0,0,1},34005}},{host,<<"localhost">>},{host_info,undefined},{port,8081},{path,<<"/">>},{path_info,undefined},{qs,<<>>},{qs_vals,undefined},{bindings,[]},{headers,[{<<"content-type">>,<<"application/octet-stream">>},{<<"content-length">>,<<"57">>},{<<"te">>,<<>>},{<<"host">>,<<"localhost:8081">>},{<<"connection">>,<<"keep-alive">>}]},{p_headers,[{<<"connection">>,[<<"keep-alive">>]}]},{cookies,undefined},{meta,[]},{body_state,waiting},{buffer,<<"[\"work\",\"TiLwqM1FYW7ggNnqvEa5QOJvTLl8hI90lmfgyrsSRmI=\",0]">>},{multipart,undefined},{resp_compress,false},{resp_state,waiting},{resp_headers,[]},{resp_body,<<>>},{onresponse,undefined}]},{state,no_state}],[{cowboy_protocol,execute,4,[{file,"/home/litepro2/amoveo/_build/default/lib/cowboy/src/cowboy_protocol.erl"},{line,442}]}]}
2018-03-01 01:46:54 =ERROR REPORT====
Ranch listener http_internal had connection process started with cowboy_protocol:start_link/4 at <0.999.0> exit with reason: {[{reason,{badrecord,block}},{mfa,{int_handler,handle,2}},{stacktrace,[{api,work,2,[{file,"/home/litepro2/amoveo/_build/prod/lib/amoveo_http/src/api.erl"},{line,457}]},{int_handler,doit,1,[{file,"/home/litepro2/amoveo/_build/prod/lib/amoveo_http/src/int_handler.erl"},{line,29}]},{int_handler,handle,2,[{file,"/home/litepro2/amoveo/_build/prod/lib/amoveo_http/src/int_handler.erl"},{line,16}]},{cowboy_handler,handler_handle,4,[{file,"/home/litepro2/amoveo/_build/default/lib/cowboy/src/cowboy_handler.erl"},{line,111}]},{cowboy_protocol,execute,4,[{file,"/home/litepro2/amoveo/_build/default/lib/cowboy/src/cowboy_protocol.erl"},{line,442}]}]},{req,[{socket,#Port<0.1773>},{transport,ranch_tcp},{connection,keepalive},{pid,<0.999.0>},{method,<<"POST">>},{version,'HTTP/1.1'},{peer,{{127,0,0,1},34005}},{host,<<"localhost">>},{host_info,undefined},{port,8081},{path,<<"/">>},{path_info,undefined},{qs,<<>>},{qs_vals,undefined},{bindings,[]},{headers,[{<<"content-type">>,<<"application/octet-stream">>},{<<"content-length">>,<<"57">>},{<<"te">>,<<>>},{<<"host">>,<<"localhost:8081">>},{<<"connection">>,<<"keep-alive">>}]},{p_headers,[{<<"connection">>,[<<"keep-alive">>]}]},{cookies,undefined},{meta,[]},{body_state,waiting},{buffer,<<"[\"work\",\"TiLwqM1FYW7ggNnqvEa5QOJvTLl8hI90lmfgyrsSRmI=\",0]">>},{multipart,undefined},{resp_compress,false},{resp_state,waiting},{resp_headers,[]},{resp_body,<<>>},{onresponse,undefined}]},{state,no_state}],[{cowboy_protocol,execute,4,[{file,"/home/litepro2/amoveo/_build/default/lib/cowboy/src/cowboy_protocol.erl"},{line,442}]}]}
Z
10:15
Zack
is your time zone 30 minutes off?
10:15
this looks like an error related to the connection to your mining pool
10:16
api:work is for the mining pool.
G
10:17
but getting this:
10:17
could not get block 9347 from peer [-7,[-7,34,229,146,193],8080]sync cron
Z
10:18
Zack
you are 34.229?
So it is failing to download new blocks from yourself?
So it is failing to download new blocks from yourself?
MH
10:18
Mandel Hoff
Good catch. My crash.log is super long.
10:18
2018-03-01 02:15:31 =ERROR REPORT====
Error in process <0.3464.0> on node amoveo_core_prod@litepro2 with exit value:
{[{reason,{badrecord,block}},{mfa,{int_handler,handle,2}},{stacktrace,[{api,work,2,[{file,"/home/litepro2/amoveo/_build/prod/lib/amoveo_http/src/api.erl"},{line,457}]},{int_handler,doit,1,[{file,"/home/litepro2/amoveo/_build/prod/lib/amoveo_http/src/int_handler.erl"},{line,29}]},{int_handler,handle,2,[{file,"/home/litepro2/amoveo/_build/prod/lib/amoveo_http/src/int_handler.erl"},{line,16}]},{cowboy_handler,handler_handle,4,[{file,"/home/litepro2/amoveo/_build/default/lib/cowboy/src/cowboy_handler.erl"},{line,111}]},{cowboy_protocol,execute,4,[{file,"/home/litepro2/amoveo/_build/default/lib/cowboy/src/cowboy_protocol.erl"},{line,442}]}]},{req,[{socket,#Port<0.162747>},{transport,ranch_tcp},{connection,keepalive},{pid,<0.3464.0>},{method,<<"POST">>},{version,'HTTP/1.1'},{peer,{{127,0,0,1},40727}},{host,<<"localhost">>},{host_info,undefined},{port,8081},{path,<<"/">>},{path_info,undefined},{qs,<<>>},{qs_vals,undefined},{bindings,[]},{headers,[{<<"content-type">>,<<"application/octet-stream">>},{<<"content-length">>,<<"57">>},{<<"te">>,<<>>},{<<"host">>,<<"localhost:8081">>},{<<"connection">>,<<"keep-alive">>}]},{p_headers,[{<<"connection">>,[<<"keep-alive">>]}]},{cookies,undefined},{meta,[]},{body_state,waiting},{buffer,<<"[\"work\",\"TiLwqM1FYW7ggNnqvEa5QOJvTLl8hI90lmfgyrsSRmI=\",0]">>},{multipart,undefined},{resp_compress,false},{resp_state,waiting},{resp_headers,[]},{resp_body,<<>>},{onresponse,undefined}]},{state,no_state}],[{cowboy_protocol,execute,4,[{file,"/home/litepro2/amoveo/_build/default/lib/cowboy/src/cowboy_protocol.erl"},{line,442}]}]}
2018-03-01 02:15:31 =ERROR REPORT====
Ranch listener http_internal had connection process started with cowboy_protocol:start_link/4 at <0.3464.0> exit with reason: {[{reason,{badrecord,block}},{mfa,{int_handler,handle,2}},{stacktrace,[{api,work,2,[{file,"/home/litepro2/amoveo/_build/prod/lib/amoveo_http/src/api.erl"},{line,457}]},{int_handler,doit,1,[{file,"/home/litepro2/amoveo/_build/prod/lib/amoveo_http/src/int_handler.erl"},{line,29}]},{int_handler,handle,2,[{file,"/home/litepro2/amoveo/_build/prod/lib/amoveo_http/src/int_handler.erl"},{line,16}]},{cowboy_handler,handler_handle,4,[{file,"/home/litepro2/amoveo/_build/default/lib/cowboy/src/cowboy_handler.erl"},{line,111}]},{cowboy_protocol,execute,4,[{file,"/home/litepro2/amoveo/_build/default/lib/cowboy/src/cowboy_protocol.erl"},{line,442}]}]},{req,[{socket,#Port<0.162747>},{transport,ranch_tcp},{connection,keepalive},{pid,<0.3464.0>},{method,<<"POST">>},{version,'HTTP/1.1'},{peer,{{127,0,0,1},40727}},{host,<<"localhost">>},{host_info,undefined},{port,8081},{path,<<"/">>},{path_info,undefined},{qs,<<>>},{qs_vals,undefined},{bindings,[]},{headers,[{<<"content-type">>,<<"application/octet-stream">>},{<<"content-length">>,<<"57">>},{<<"te">>,<<>>},{<<"host">>,<<"localhost:8081">>},{<<"connection">>,<<"keep-alive">>}]},{p_headers,[{<<"connection">>,[<<"keep-alive">>]}]},{cookies,undefined},{meta,[]},{body_state,waiting},{buffer,<<"[\"work\",\"TiLwqM1FYW7ggNnqvEa5QOJvTLl8hI90lmfgyrsSRmI=\",0]">>},{multipart,undefined},{resp_compress,false},{resp_state,waiting},{resp_headers,[]},{resp_body,<<>>},{onresponse,undefined}]},{state,no_state}],[{cowboy_protocol,execute,4,[{file,"/home/litepro2/amoveo/_build/default/lib/cowboy/src/cowboy_protocol.erl"},{line,442}]}]}
Error in process <0.3464.0> on node amoveo_core_prod@litepro2 with exit value:
{[{reason,{badrecord,block}},{mfa,{int_handler,handle,2}},{stacktrace,[{api,work,2,[{file,"/home/litepro2/amoveo/_build/prod/lib/amoveo_http/src/api.erl"},{line,457}]},{int_handler,doit,1,[{file,"/home/litepro2/amoveo/_build/prod/lib/amoveo_http/src/int_handler.erl"},{line,29}]},{int_handler,handle,2,[{file,"/home/litepro2/amoveo/_build/prod/lib/amoveo_http/src/int_handler.erl"},{line,16}]},{cowboy_handler,handler_handle,4,[{file,"/home/litepro2/amoveo/_build/default/lib/cowboy/src/cowboy_handler.erl"},{line,111}]},{cowboy_protocol,execute,4,[{file,"/home/litepro2/amoveo/_build/default/lib/cowboy/src/cowboy_protocol.erl"},{line,442}]}]},{req,[{socket,#Port<0.162747>},{transport,ranch_tcp},{connection,keepalive},{pid,<0.3464.0>},{method,<<"POST">>},{version,'HTTP/1.1'},{peer,{{127,0,0,1},40727}},{host,<<"localhost">>},{host_info,undefined},{port,8081},{path,<<"/">>},{path_info,undefined},{qs,<<>>},{qs_vals,undefined},{bindings,[]},{headers,[{<<"content-type">>,<<"application/octet-stream">>},{<<"content-length">>,<<"57">>},{<<"te">>,<<>>},{<<"host">>,<<"localhost:8081">>},{<<"connection">>,<<"keep-alive">>}]},{p_headers,[{<<"connection">>,[<<"keep-alive">>]}]},{cookies,undefined},{meta,[]},{body_state,waiting},{buffer,<<"[\"work\",\"TiLwqM1FYW7ggNnqvEa5QOJvTLl8hI90lmfgyrsSRmI=\",0]">>},{multipart,undefined},{resp_compress,false},{resp_state,waiting},{resp_headers,[]},{resp_body,<<>>},{onresponse,undefined}]},{state,no_state}],[{cowboy_protocol,execute,4,[{file,"/home/litepro2/amoveo/_build/default/lib/cowboy/src/cowboy_protocol.erl"},{line,442}]}]}
2018-03-01 02:15:31 =ERROR REPORT====
Ranch listener http_internal had connection process started with cowboy_protocol:start_link/4 at <0.3464.0> exit with reason: {[{reason,{badrecord,block}},{mfa,{int_handler,handle,2}},{stacktrace,[{api,work,2,[{file,"/home/litepro2/amoveo/_build/prod/lib/amoveo_http/src/api.erl"},{line,457}]},{int_handler,doit,1,[{file,"/home/litepro2/amoveo/_build/prod/lib/amoveo_http/src/int_handler.erl"},{line,29}]},{int_handler,handle,2,[{file,"/home/litepro2/amoveo/_build/prod/lib/amoveo_http/src/int_handler.erl"},{line,16}]},{cowboy_handler,handler_handle,4,[{file,"/home/litepro2/amoveo/_build/default/lib/cowboy/src/cowboy_handler.erl"},{line,111}]},{cowboy_protocol,execute,4,[{file,"/home/litepro2/amoveo/_build/default/lib/cowboy/src/cowboy_protocol.erl"},{line,442}]}]},{req,[{socket,#Port<0.162747>},{transport,ranch_tcp},{connection,keepalive},{pid,<0.3464.0>},{method,<<"POST">>},{version,'HTTP/1.1'},{peer,{{127,0,0,1},40727}},{host,<<"localhost">>},{host_info,undefined},{port,8081},{path,<<"/">>},{path_info,undefined},{qs,<<>>},{qs_vals,undefined},{bindings,[]},{headers,[{<<"content-type">>,<<"application/octet-stream">>},{<<"content-length">>,<<"57">>},{<<"te">>,<<>>},{<<"host">>,<<"localhost:8081">>},{<<"connection">>,<<"keep-alive">>}]},{p_headers,[{<<"connection">>,[<<"keep-alive">>]}]},{cookies,undefined},{meta,[]},{body_state,waiting},{buffer,<<"[\"work\",\"TiLwqM1FYW7ggNnqvEa5QOJvTLl8hI90lmfgyrsSRmI=\",0]">>},{multipart,undefined},{resp_compress,false},{resp_state,waiting},{resp_headers,[]},{resp_body,<<>>},{onresponse,undefined}]},{state,no_state}],[{cowboy_protocol,execute,4,[{file,"/home/litepro2/amoveo/_build/default/lib/cowboy/src/cowboy_protocol.erl"},{line,442}]}]}
Z
10:18
Zack
In reply to this message
yeah, it used to delete itself when you restarted. I must have messed up something in the Makefile.
10:19
this is still just an error message from the connection to the mining pool. it doesn't explain why it wont sync.
MH
10:19
Mandel Hoff
I didn't restart. I did a mv on the old folder, and a new git clone for you branch. The build was a make prod-build on the fresh cloned branch.
Z
10:19
Zack
cool
MH
10:20
Mandel Hoff
Eww. Ok. I can try rm -rf and try again.
G
Z
10:23
Zack
ill try pushing blocks to Gonzalo
10:24
it worked.
10:24
now ill push to Mandel, if he is still up.