Looks like it's fixed now. Big tx gone into blockchain. You can see blocks in the network at normal speed.
1. Sorry for inconvenience.
2. I'll post about git changes soon.
Git updated. BUT: I don't recomment to update all nodes now due to following reasons: - this patch isn't tested properly (=> can cause some other unknown problems) - network operates normally without this patch (it doesn't change any protocol logic) Let's wait 1-2 days before updating all nodes. Old code works the right way in most cases except transactions bigger than 20Kb. In case such big (>20Kb) transaction will appear again it will be included by patched nodes and this will not influence network very much. |
|
|
|
The problem is in block generation code. In one of last updates in Bytecoin there was a bug introduced: it calculates extra-size penalty the wrong way. As a result we see that a mined block isn't accepted by the network. I will consume the big transaction now into correct block. As soon as network accepts this block I will release new mining code to git.
Here is the tx that caused the problem:
id: <f1d8e3391161e4e98566c746d605f97cf432cbd19c83d8b0444e02748f54117e>
blob_size: 20534
Funnily this is my tx Hope to see the commit soon! edit: looks like your patch worked, as the tx now exists in the main chain. Thank you for this problem. This is the way software becomes better. |
|
|
|
|
Looks like it's fixed now. Big tx gone into blockchain. You can see blocks in the network at normal speed.
1. Sorry for inconvenience.
2. I'll post about git changes soon.
|
|
|
|
I'm seeing a ton of red in bitmonerod - presumably this is the issue displaying itself.
Do I need to re-download the blockchain? Download a new wallet or bitmonerod? Just leave it mining and it will fix itself?
Thanks.
It's a soft fork so prior blocks should be OK, just need to recompile Yes. No actions from node operators is needed just now. As soon a fix will be pushed to repo you need to replace old binaries to new ones. But in any way this will not be an urgent issue. The problem now is that nobody can include that transaction in block  As soon as it will be accepted network will continue normal operations. |
|
|
|
fix coming soon, it looks like get_block_reward doesn't work as intended.
i will pm thankful_for_today with some c code to disable adaptive block sizing and set blocksize limits to those similar in bitcoin, then we should be back on track with a hardfork i hope.
Hello! It's allright  I have a fix and I will deploy it now. Hardfork is not required. The problem is in mining code not in protocol rules. 10 minutes, please cool, sounds good The problem is in block generation code. In one of last updates in Bytecoin there was a bug introduced: it calculates extra-size penalty the wrong way. As a result we see that a mined block isn't accepted by the network. I will consume the big transaction now into correct block. As soon as network accepts this block I will release new mining code to git. Here is the tx that caused the problem: id: <f1d8e3391161e4e98566c746d605f97cf432cbd19c83d8b0444e02748f54117e> blob_size: 20534 |
|
|
|
fix coming soon, it looks like get_block_reward doesn't work as intended.
i will pm thankful_for_today with some c code to disable adaptive block sizing and set blocksize limits to those similar in bitcoin, then we should be back on track with a hardfork i hope.
Hello! It's allright I have a fix and I will deploy it now. Hardfork is not required. The problem is in mining code not in protocol rules. 10 minutes, please |
|
|
|
|
There is a lot of issues with GUI to talk about. I propose to meet in Irc at 20GMT today. Is this time good?
I have some budget we can spend to motivate GUI developers:
1.000.000 BCN and 400 BMR.
Anybody can contribute some coins also for this purpose.
|
|
|
|
Do you get "Error: refresh failed: daemon is busy. Please try later. Blocks received: 0" all the time? It was not the case some hours ago. I restarted the daemon and the wallet many times.
Say "save" to bitmonerod console. This is a small bug in rpc handling. |
|
|
|
Twice I've seen stuff about alternate blockchains and successful "reorganizations" in the daemon. Is this common in all cryptocurrencies but simply hidden behind the GUI? Or is this coin particular prone to forking?
Am I suffering a similar problem, if it is a problem? I was getting blocks ok, but now all I see is "Block added as alternative" messages. What does this mean? As usual, nothing about this on google. This isn't a problem and you aren't suffering from this unless you have mined block that gone to alternative branch. In the later case (you mined block but somebody else mined two blocks in the different branch) you loose your block reward. This logic is the same in all currencies and in Bitcoin also. 10 minutes were choosen 5 years ago. Now 1 minute is a reasonable minimum. It makes chain to react faster on any changes and gives more chances to solo miners. In currencies with gui wallets you don't read logs normally. If you will you can find reorganize events and lternative chains. |
|
|
|
"blocks recieved" is just the new blocks in the blockchain since your last refresh. My question though, 3 blocks found... Balance 52, unlocked balance 35, why different? I haven't done a save, haven't locked it... and its been a while so its not waiting for confirmation.
The +#define CRYPTONOTE_MINED_MONEY_UNLOCK_WINDOW 60 change in the github indicates that it requires 60 minutes for your coins to be unlocked. In BCN this is 10. I'm not sure if these values refer to minutes though. 60 blocks unlock delay. This is much safer. |
|
|
|
So it looks like there willbe a total supply of ~18.5m, block reward is ~17 and we are currently at block 271.
Total coins willbe a factor 1000 of bytecoin and it has a flatter reward schedule. So after all it's not as bad as we thought it was!!
thankfull_for_today, can you add the channel #bitmonero on freenode in the OP?
done |
|
|
|
hi,
first time for solomining, and i have a noob question
is it ok if in bitmonerod said block successfully added and have block reward around 17,6 coins, but when i check in my wallet is still zero?
It isn't ok. Say "refresh" to wallet. |
|
|
|
Starting minning, waiting for merged with BCN!
I'm working on this together with a friend of mine. Merged mining will be released next week. |
|
|
|
I keep getting connect failed errors.
Please copy what print_cn commands tells you? |
|
|
|
someone can explain how to mine from different pc to one wallet?(run server and connect clients)
Just say start_mining address nthreads to all your daemons. It works more straitforward way than in bitcoin. |
|
|
|
IRC might be helpful for a launch ..
Reschedule for later date?
IRC is good, yes. Looks like there is no so much mac-only users here. We will start in few minutes. As far as I see on my mac it isn't very easy to build this for mac: there is a lot of things to fix in code. OK . . what should we expect? Are you going to update the OP, post at the end, new thread, or direct to a website? I've updated an OP: sources are on git, binaries are on MEGA. Height is 5, difficulty is 27908. This is a good start. This is bullshit. Does not compile on OSX. Though I can fix the malloc error (and the following error), the errors get increasing complex afterwards. mkdir -p build/release
cd build/release && cmake -D CMAKE_BUILD_TYPE=Release ../..
-- The C compiler identification is Clang 5.1.0
-- The CXX compiler identification is Clang 5.1.0
-- Check for working C compiler: /usr/bin/cc
-- Check for working C compiler: /usr/bin/cc -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Check for working CXX compiler: /usr/bin/c++
-- Check for working CXX compiler: /usr/bin/c++ -- works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Boost version: 1.55.0
-- Found the following Boost libraries:
-- system
-- filesystem
-- thread
-- date_time
-- chrono
-- regex
-- serialization
-- atomic
-- program_options
-- Found PythonInterp: /usr/bin/python (found version "2.7.5")
-- Looking for include file pthread.h
-- Looking for include file pthread.h - found
-- Looking for pthread_create
-- Looking for pthread_create - found
-- Found Threads: TRUE
-- Configuring done
-- Generating done
-- Build files have been written to: /Users/lunokhod/Coin/bitmonero-master/build/release
cd build/release && /Applications/Xcode.app/Contents/Developer/usr/bin/make
Scanning dependencies of target version
[ 0%] Built target version
Scanning dependencies of target upnpc-static
[ 1%] Building C object external/miniupnpc/CMakeFiles/upnpc-static.dir/igd_desc_parse.c.o
[ 2%] Building C object external/miniupnpc/CMakeFiles/upnpc-static.dir/miniupnpc.c.o
[ 3%] Building C object external/miniupnpc/CMakeFiles/upnpc-static.dir/minixml.c.o
[ 4%] Building C object external/miniupnpc/CMakeFiles/upnpc-static.dir/minisoap.c.o
[ 5%] Building C object external/miniupnpc/CMakeFiles/upnpc-static.dir/miniwget.c.o
[ 6%] Building C object external/miniupnpc/CMakeFiles/upnpc-static.dir/upnpc.c.o
[ 7%] Building C object external/miniupnpc/CMakeFiles/upnpc-static.dir/upnpcommands.c.o
[ 8%] Building C object external/miniupnpc/CMakeFiles/upnpc-static.dir/upnpreplyparse.c.o
[ 9%] Building C object external/miniupnpc/CMakeFiles/upnpc-static.dir/upnperrors.c.o
[ 10%] Building C object external/miniupnpc/CMakeFiles/upnpc-static.dir/connecthostport.c.o
[ 11%] Building C object external/miniupnpc/CMakeFiles/upnpc-static.dir/portlistingparse.c.o
[ 12%] Building C object external/miniupnpc/CMakeFiles/upnpc-static.dir/receivedata.c.o
[ 13%] Building C object external/miniupnpc/CMakeFiles/upnpc-static.dir/minissdpc.c.o
Linking C static library libminiupnpc.a
[ 13%] Built target upnpc-static
Scanning dependencies of target common
[ 14%] Building CXX object src/CMakeFiles/common.dir/common/base58.cpp.o
In file included from /Users/lunokhod/Coin/bitmonero-master/src/common/base58.cpp:14:
In file included from /Users/lunokhod/Coin/bitmonero-master/src/common/util.h:11:
/Users/lunokhod/Coin/bitmonero-master/src/crypto/crypto.h:25:10: warning: private field 'data' is not used [-Wunused-private-field]
char data[32];
^
/Users/lunokhod/Coin/bitmonero-master/src/crypto/crypto.h:29:10: warning: private field 'data' is not used [-Wunused-private-field]
char data[32];
^
2 warnings generated.
[ 15%] Building CXX object src/CMakeFiles/common.dir/common/command_line.cpp.o
[ 16%] Building CXX object src/CMakeFiles/common.dir/common/util.cpp.o
In file included from /Users/lunokhod/Coin/bitmonero-master/src/common/util.cpp:10:
In file included from /Users/lunokhod/Coin/bitmonero-master/src/common/util.h:11:
/Users/lunokhod/Coin/bitmonero-master/src/crypto/crypto.h:25:10: warning: private field 'data' is not used [-Wunused-private-field]
char data[32];
^
/Users/lunokhod/Coin/bitmonero-master/src/crypto/crypto.h:29:10: warning: private field 'data' is not used [-Wunused-private-field]
char data[32];
^
2 warnings generated.
Linking CXX static library libcommon.a
[ 16%] Built target common
Scanning dependencies of target crypto
[ 17%] Building C object src/CMakeFiles/crypto.dir/crypto/blake256.c.o
[ 18%] Building C object src/CMakeFiles/crypto.dir/crypto/chacha8.c.o
[ 20%] Building C object src/CMakeFiles/crypto.dir/crypto/crypto-ops-data.c.o
[ 21%] Building C object src/CMakeFiles/crypto.dir/crypto/crypto-ops.c.o
[ 22%] Building CXX object src/CMakeFiles/crypto.dir/crypto/crypto.cpp.o
In file included from /Users/lunokhod/Coin/bitmonero-master/src/crypto/crypto.cpp:16:
/Users/lunokhod/Coin/bitmonero-master/src/crypto/crypto.h:29:10: warning: private field 'data' is not used [-Wunused-private-field]
char data[32];
^
1 warning generated.
[ 23%] Building C object src/CMakeFiles/crypto.dir/crypto/groestl.c.o
/Users/lunokhod/Coin/bitmonero-master/src/crypto/groestl.c:210:9: warning: comparison of integers of different signs: 'int' and
'unsigned long' [-Wsign-compare]
for(;i<(SIZE512/sizeof(uint32_t));i++)
~^ ~~~~~~~~~~~~~~~~~~~~~~~~
1 warning generated.
[ 24%] Building C object src/CMakeFiles/crypto.dir/crypto/hash-extra-blake.c.o
[ 25%] Building C object src/CMakeFiles/crypto.dir/crypto/hash-extra-groestl.c.o
[ 26%] Building C object src/CMakeFiles/crypto.dir/crypto/hash-extra-jh.c.o
[ 27%] Building C object src/CMakeFiles/crypto.dir/crypto/hash-extra-skein.c.o
[ 28%] Building C object src/CMakeFiles/crypto.dir/crypto/hash.c.o
[ 29%] Building C object src/CMakeFiles/crypto.dir/crypto/jh.c.o
[ 30%] Building C object src/CMakeFiles/crypto.dir/crypto/keccak.c.o
[ 31%] Building C object src/CMakeFiles/crypto.dir/crypto/oaes_lib.c.o
/Users/lunokhod/Coin/bitmonero-master/src/crypto/oaes_lib.c:37:10: fatal error: 'malloc.h' file not found
#include <malloc.h>
^
1 error generated.
make[3]: *** [src/CMakeFiles/crypto.dir/crypto/oaes_lib.c.o] Error 1
make[2]: *** [src/CMakeFiles/crypto.dir/all] Error 2
make[1]: *** [all] Error 2
make: *** [build-release] Error 2
Looks like this is a known problem with Cryptonote. Anyway I will accept patch for OsX into the repo as soon as somebody will fix this. |
|
|
|
IRC might be helpful for a launch ..
Reschedule for later date?
IRC is good, yes. Looks like there is no so much mac-only users here. We will start in few minutes. As far as I see on my mac it isn't very easy to build this for mac: there is a lot of things to fix in code. OK . . what should we expect? Are you going to update the OP, post at the end, new thread, or direct to a website? I've updated an OP: sources are on git, binaries are on MEGA. Height is 5, difficulty is 27908. This is a good start. |
|
|
|
IRC might be helpful for a launch ..
Reschedule for later date?
IRC is good, yes. Looks like there is no so much mac-only users here. We will start in few minutes. As far as I see on my mac it isn't very easy to build this for mac: there is a lot of things to fix in code. |
|
|
|
|
Windows build is ready. Mac build isn't. Anybody can build for mac?
|
|
|
|
|
Show Posts
