back to creating new alt coin | Bitcointalksearch.org

BlackHatCoiner

legendary

Activity: 1512

Merit: 7340

Farewell, Leo

I can't help you with every error that is presented into your machine as I don't have an answer to everything (and I honestly hardly make much sense from your writings). You ought to use your best friend: Google.

mironkraft

jr. member

Activity: 78

Merit: 4

mironkraft

jr. member

Activity: 78

Merit: 4

Detailed comands:

Code:

mironkraft@DESKTOP-Q44IAMD:~/XXXXXXCoin/depends$ make HOST=x86_64-w64-mingw32

Building boost...
warning: failed to open log file bin.v2/config.log for writing
...found 1 target...
Performing configuration checks

    - default address-model    : none (cached)
    - default architecture     : none (cached)
    - BOOST_COMP_GNUC >= 4.3.0 : no  (cached)
...found 1 target...
...updating 1 target...

file /tmp/jam146d9b56.000
# Automatically generated by Boost.Build.
# Do not edit.

module config-cache {
  set "default address-model-32-bit-64-bit-windows-7.3-gcc" : "none" ;
  set "default architecture-arm-mips1-power-sparc-x86-combined-windows-7.3-gcc" : "none" ;
  set "BOOST_COMP_GNUC >= 4.3.0-64-x86-windows-7.3-gcc" : "false" ;
}

config-cache.write bin.v2/project-cache.jam

    cat "/tmp/jam146d9b56.000" > "bin.v2/project-cache.jam"

/bin/sh: 2: cannot create bin.v2/project-cache.jam: Permission denied
...failed config-cache.write bin.v2/project-cache.jam...
...failed updating 1 target...

Component configuration:

    - atomic                   : not building
    - chrono                   : not building
    - container                : not building
    - context                  : not building
    - contract                 : not building
    - coroutine                : not building
    - date_time                : not building
    - exception                : not building
    - fiber                    : not building
    - filesystem               : building
    - graph                    : not building
    - graph_parallel           : not building
    - headers                  : not building
    - iostreams                : not building
    - locale                   : not building
    - log                      : not building
    - math                     : not building
    - mpi                      : not building
    - program_options          : not building
    - python                   : not building
    - random                   : not building
    - regex                    : not building
    - serialization            : not building
    - stacktrace               : not building
    - system                   : building
    - test                     : building
    - thread                   : not building
    - timer                    : not building
    - type_erasure             : not building
    - wave                     : not building

...patience...
...found 1162 targets...
...updating 45 targets...
gcc.compile.c++ bin.v2/libs/filesystem/build/gcc-7.3/release/address-model-64/architecture-x86/link-static/target-os-windows/threading-multi/visibility-hidden/codecvt_error_category.o

    "x86_64-w64-mingw32-g++"   -fvisibility-inlines-hidden -pipe -O2 -std=c++17   -fcf-protection=full   -m64 -mthreads -O3 -finline-functions -Wno-inline -Wall -fvisibility=hidden   -I/home/mironkraft/XXXXXXCoin/depends/x86_64-w64-mingw32/include      -DBOOST_ALL_NO_LIB=1 -DBOOST_FILESYSTEM_STATIC_LINK=1 -DNDEBUG  -I"." -c -o "bin.v2/libs/filesystem/build/gcc-7.3/release/address-model-64/architecture-x86/link-static/target-os-windows/threading-multi/visibility-hidden/codecvt_error_category.o" "libs/filesystem/src/codecvt_error_category.cpp"

x86_64-w64-mingw32-g++: error: unrecognized command line option ‘-fcf-protection=full’; did you mean ‘-fstack-protector-all’?
...failed gcc.compile.c++ bin.v2/libs/filesystem/build/gcc-7.3/release/address-model-64/architecture-x86/link-static/target-os-windows/threading-multi/visibility-hidden/codecvt_error_category.o...
gcc.compile.c++ bin.v2/libs/filesystem/build/gcc-7.3/release/address-model-64/architecture-x86/link-static/target-os-windows/threading-multi/visibility-hidden/operations.o

    "x86_64-w64-mingw32-g++"   -fvisibility-inlines-hidden -pipe -O2 -std=c++17   -fcf-protection=full   -m64 -mthreads -O3 -finline-functions -Wno-inline -Wall -fvisibility=hidden   -I/home/mironkraft/XXXXXXCoin/depends/x86_64-w64-mingw32/include      -DBOOST_ALL_NO_LIB=1 -DBOOST_FILESYSTEM_STATIC_LINK=1 -DNDEBUG  -I"." -c -o "bin.v2/libs/filesystem/build/gcc-7.3/release/address-model-64/architecture-x86/link-static/target-os-windows/threading-multi/visibility-hidden/operations.o" "libs/filesystem/src/operations.cpp"

x86_64-w64-mingw32-g++: error: unrecognized command line option ‘-fcf-protection=full’; did you mean ‘-fstack-protector-all’?
...failed gcc.compile.c++ bin.v2/libs/filesystem/build/gcc-7.3/release/address-model-64/architecture-x86/link-static/target-os-windows/threading-multi/visibility-hidden/operations.o...
gcc.compile.c++ bin.v2/libs/filesystem/build/gcc-7.3/release/address-model-64/architecture-x86/link-static/target-os-windows/threading-multi/visibility-hidden/path.o

    "x86_64-w64-mingw32-g++"   -fvisibility-inlines-hidden -pipe -O2 -std=c++17   -fcf-protection=full   -m64 -mthreads -O3 -finline-functions -Wno-inline -Wall -fvisibility=hidden   -I/home/mironkraft/XXXXXXCoin/depends/x86_64-w64-mingw32/include      -DBOOST_ALL_NO_LIB=1 -DBOOST_FILESYSTEM_STATIC_LINK=1 -DNDEBUG  -I"." -c -o "bin.v2/libs/filesystem/build/gcc-7.3/release/address-model-64/architecture-x86/link-static/target-os-windows/threading-multi/visibility-hidden/path.o" "libs/filesystem/src/path.cpp"

x86_64-w64-mingw32-g++: error: unrecognized command line option ‘-fcf-protection=full’; did you mean ‘-fstack-protector-all’?
...failed gcc.compile.c++ bin.v2/libs/filesystem/build/gcc-7.3/release/address-model-64/architecture-x86/link-static/target-os-windows/threading-multi/visibility-hidden/path.o...
gcc.compile.c++ bin.v2/libs/filesystem/build/gcc-7.3/release/address-model-64/architecture-x86/link-static/target-os-windows/threading-multi/visibility-hidden/path_traits.o

    "x86_64-w64-mingw32-g++"   -fvisibility-inlines-hidden -pipe -O2 -std=c++17   -fcf-protection=full   -m64 -mthreads -O3 -finline-functions -Wno-inline -Wall -fvisibility=hidden   -I/home/mironkraft/XXXXXXCoin/depends/x86_64-w64-mingw32/include      -DBOOST_ALL_NO_LIB=1 -DBOOST_FILESYSTEM_STATIC_LINK=1 -DNDEBUG  -I"." -c -o "bin.v2/libs/filesystem/build/gcc-7.3/release/address-model-64/architecture-x86/link-static/target-os-windows/threading-multi/visibility-hidden/path_traits.o" "libs/filesystem/src/path_traits.cpp"

x86_64-w64-mingw32-g++: error: unrecognized command line option ‘-fcf-protection=full’; did you mean ‘-fstack-protector-all’?
...failed gcc.compile.c++ bin.v2/libs/filesystem/build/gcc-7.3/release/address-model-64/architecture-x86/link-static/target-os-windows/threading-multi/visibility-hidden/path_traits.o...
gcc.compile.c++ bin.v2/libs/filesystem/build/gcc-7.3/release/address-model-64/architecture-x86/link-static/target-os-windows/threading-multi/visibility-hidden/portability.o

    "x86_64-w64-mingw32-g++"   -fvisibility-inlines-hidden -pipe -O2 -std=c++17   -fcf-protection=full   -m64 -mthreads -O3 -finline-functions -Wno-inline -Wall -fvisibility=hidden   -I/home/mironkraft/XXXXXXCoin/depends/x86_64-w64-mingw32/include      -DBOOST_ALL_NO_LIB=1 -DBOOST_FILESYSTEM_STATIC_LINK=1 -DNDEBUG  -I"." -c -o "bin.v2/libs/filesystem/build/gcc-7.3/release/address-model-64/architecture-x86/link-static/target-os-windows/threading-multi/visibility-hidden/portability.o" "libs/filesystem/src/portability.cpp"

x86_64-w64-mingw32-g++: error: unrecognized command line option ‘-fcf-protection=full’; did you mean ‘-fstack-protector-all’?
...failed gcc.compile.c++ bin.v2/libs/filesystem/build/gcc-7.3/release/address-model-64/architecture-x86/link-static/target-os-windows/threading-multi/visibility-hidden/portability.o...
gcc.compile.c++ bin.v2/libs/filesystem/build/gcc-7.3/release/address-model-64/architecture-x86/link-static/target-os-windows/threading-multi/visibility-hidden/unique_path.o

    "x86_64-w64-mingw32-g++"   -fvisibility-inlines-hidden -pipe -O2 -std=c++17   -fcf-protection=full   -m64 -mthreads -O3 -finline-functions -Wno-inline -Wall -fvisibility=hidden   -I/home/mironkraft/XXXXXXCoin/depends/x86_64-w64-mingw32/include      -DBOOST_ALL_NO_LIB=1 -DBOOST_FILESYSTEM_STATIC_LINK=1 -DNDEBUG  -I"." -c -o "bin.v2/libs/filesystem/build/gcc-7.3/release/address-model-64/architecture-x86/link-static/target-os-windows/threading-multi/visibility-hidden/unique_path.o" "libs/filesystem/src/unique_path.cpp"

x86_64-w64-mingw32-g++: error: unrecognized command line option ‘-fcf-protection=full’; did you mean ‘-fstack-protector-all’?
...failed gcc.compile.c++ bin.v2/libs/filesystem/build/gcc-7.3/release/address-model-64/architecture-x86/link-static/target-os-windows/threading-multi/visibility-hidden/unique_path.o...
gcc.compile.c++ bin.v2/libs/filesystem/build/gcc-7.3/release/address-model-64/architecture-x86/link-static/target-os-windows/threading-multi/visibility-hidden/utf8_codecvt_facet.o

    "x86_64-w64-mingw32-g++"   -fvisibility-inlines-hidden -pipe -O2 -std=c++17   -fcf-protection=full   -m64 -mthreads -O3 -finline-functions -Wno-inline -Wall -fvisibility=hidden   -I/home/mironkraft/XXXXXXCoin/depends/x86_64-w64-mingw32/include      -DBOOST_ALL_NO_LIB=1 -DBOOST_FILESYSTEM_STATIC_LINK=1 -DNDEBUG  -I"." -c -o "bin.v2/libs/filesystem/build/gcc-7.3/release/address-model-64/architecture-x86/link-static/target-os-windows/threading-multi/visibility-hidden/utf8_codecvt_facet.o" "libs/filesystem/src/utf8_codecvt_facet.cpp"

x86_64-w64-mingw32-g++: error: unrecognized command line option ‘-fcf-protection=full’; did you mean ‘-fstack-protector-all’?
...failed gcc.compile.c++ bin.v2/libs/filesystem/build/gcc-7.3/release/address-model-64/architecture-x86/link-static/target-os-windows/threading-multi/visibility-hidden/utf8_codecvt_facet.o...
gcc.compile.c++ bin.v2/libs/filesystem/build/gcc-7.3/release/address-model-64/architecture-x86/link-static/target-os-windows/threading-multi/visibility-hidden/windows_file_codecvt.o

    "x86_64-w64-mingw32-g++"   -fvisibility-inlines-hidden -pipe -O2 -std=c++17   -fcf-protection=full   -m64 -mthreads -O3 -finline-functions -Wno-inline -Wall -fvisibility=hidden   -I/home/mironkraft/XXXXXXCoin/depends/x86_64-w64-mingw32/include      -DBOOST_ALL_NO_LIB=1 -DBOOST_FILESYSTEM_STATIC_LINK=1 -DNDEBUG  -I"." -c -o "bin.v2/libs/filesystem/build/gcc-7.3/release/address-model-64/architecture-x86/link-static/target-os-windows/threading-multi/visibility-hidden/windows_file_codecvt.o" "libs/filesystem/src/windows_file_codecvt.cpp"

x86_64-w64-mingw32-g++: error: unrecognized command line option ‘-fcf-protection=full’; did you mean ‘-fstack-protector-all’?
...failed gcc.compile.c++ bin.v2/libs/filesystem/build/gcc-7.3/release/address-model-64/architecture-x86/link-static/target-os-windows/threading-multi/visibility-hidden/windows_file_codecvt.o...
...skipped libboost_filesystem-mt-s-x64.a(clean) for lack of codecvt_error_category.o...
...skipped libboost_filesystem-mt-s-x64.a for lack of codecvt_error_category.o...
...skipped libboost_filesystem-mt-s-x64.a for lack of libboost_filesystem-mt-s-x64.a...
gcc.compile.c++ bin.v2/libs/system/build/gcc-7.3/release/address-model-64/architecture-x86/link-static/target-os-windows/threading-multi/visibility-hidden/error_code.o

    "x86_64-w64-mingw32-g++"   -fvisibility-inlines-hidden -pipe -O2 -std=c++17   -fcf-protection=full   -m64 -mthreads -O3 -finline-functions -Wno-inline -Wall -fvisibility=hidden   -I/home/mironkraft/XXXXXXCoin/depends/x86_64-w64-mingw32/include      -DBOOST_ALL_NO_LIB=1 -DBOOST_SYSTEM_STATIC_LINK=1 -DNDEBUG  -I"." -c -o "bin.v2/libs/system/build/gcc-7.3/release/address-model-64/architecture-x86/link-static/target-os-windows/threading-multi/visibility-hidden/error_code.o" "libs/system/src/error_code.cpp"

x86_64-w64-mingw32-g++: error: unrecognized command line option ‘-fcf-protection=full’; did you mean ‘-fstack-protector-all’?
...failed gcc.compile.c++ bin.v2/libs/system/build/gcc-7.3/release/address-model-64/architecture-x86/link-static/target-os-windows/threading-multi/visibility-hidden/error_code.o...
...skipped libboost_system-mt-s-x64.a(clean) for lack of error_code.o...
...skipped libboost_system-mt-s-x64.a for lack of error_code.o...
...skipped 
libboost_system-mt-s-x64.a for lack of libboost_system-mt-s-x64.a...
gcc.compile.c++ bin.v2/libs/test/build/gcc-7.3/release/address-model-64/architecture-x86/link-static/target-os-windows/threading-multi/visibility-hidden/execution_monitor.o

    "x86_64-w64-mingw32-g++"   -fvisibility-inlines-hidden -pipe -O2 -std=c++17   -fcf-protection=full   -m64 -mthreads -O3 -finline-functions -Wno-inline -Wall -fvisibility=hidden   -I/home/mironkraft/XXXXXXCoin/depends/x86_64-w64-mingw32/include      -DBOOST_ALL_NO_LIB=1 -DNDEBUG  -I"." -c -o "bin.v2/libs/test/build/gcc-7.3/release/address-model-64/architecture-x86/link-static/target-os-windows/threading-multi/visibility-hidden/execution_monitor.o" "libs/test/src/execution_monitor.cpp"

x86_64-w64-mingw32-g++: error: unrecognized command line option ‘-fcf-protection=full’; did you mean ‘-fstack-protector-all’?
...failed gcc.compile.c++ bin.v2/libs/test/build/gcc-7.3/release/address-model-64/architecture-x86/link-static/target-os-windows/threading-multi/visibility-hidden/execution_monitor.o...
gcc.compile.c++ bin.v2/libs/test/build/gcc-7.3/release/address-model-64/architecture-x86/link-static/target-os-windows/threading-multi/visibility-hidden/debug.o

    "x86_64-w64-mingw32-g++"   -fvisibility-inlines-hidden -pipe -O2 -std=c++17   -fcf-protection=full   -m64 -mthreads -O3 -finline-functions -Wno-inline -Wall -fvisibility=hidden   -I/home/mironkraft/XXXXXXCoin/depends/x86_64-w64-mingw32/include      -DBOOST_ALL_NO_LIB=1 -DNDEBUG  -I"." -c -o "bin.v2/libs/test/build/gcc-7.3/release/address-model-64/architecture-x86/link-static/target-os-windows/threading-multi/visibility-hidden/debug.o" "libs/test/src/debug.cpp"

x86_64-w64-mingw32-g++: error: unrecognized command line option ‘-fcf-protection=full’; did you mean ‘-fstack-protector-all’?
...failed gcc.compile.c++ bin.v2/libs/test/build/gcc-7.3/release/address-model-64/architecture-x86/link-static/target-os-windows/threading-multi/visibility-hidden/debug.o...
gcc.compile.c++ bin.v2/libs/test/build/gcc-7.3/release/address-model-64/architecture-x86/link-static/target-os-windows/threading-multi/visibility-hidden/cpp_main.o

    "x86_64-w64-mingw32-g++"   -fvisibility-inlines-hidden -pipe -O2 -std=c++17   -fcf-protection=full   -m64 -mthreads -O3 -finline-functions -Wno-inline -Wall -fvisibility=hidden   -I/home/mironkraft/XXXXXXCoin/depends/x86_64-w64-mingw32/include      -DBOOST_ALL_NO_LIB=1 -DNDEBUG  -I"." -c -o "bin.v2/libs/test/build/gcc-7.3/release/address-model-64/architecture-x86/link-static/target-os-windows/threading-multi/visibility-hidden/cpp_main.o" "libs/test/src/cpp_main.cpp"

x86_64-w64-mingw32-g++: error: unrecognized command line option ‘-fcf-protection=full’; did you mean ‘-fstack-protector-all’?
...failed gcc.compile.c++ bin.v2/libs/test/build/gcc-7.3/release/address-model-64/architecture-x86/link-static/target-os-windows/threading-multi/visibility-hidden/cpp_main.o...
...skipped libboost_prg_exec_monitor-mt-s-x64.a(clean) for lack of execution_monitor.o...
...skipped libboost_prg_exec_monitor-mt-s-x64.a for lack of execution_monitor.o......skipped 
libboost_prg_exec_monitor-mt-s-x64.a for lack of libboost_prg_exec_monitor-mt-s-x64.a...
gcc.compile.c++ bin.v2/libs/test/build/gcc-7.3/release/address-model-64/architecture-x86/link-static/target-os-windows/threading-multi/visibility-hidden/compiler_log_formatter.o

    "x86_64-w64-mingw32-g++"   -fvisibility-inlines-hidden -pipe -O2 -std=c++17   -fcf-protection=full   -m64 -mthreads -O3 -finline-functions -Wno-inline -Wall -fvisibility=hidden   -I/home/mironkraft/XXXXXXCoin/depends/x86_64-w64-mingw32/include      -DBOOST_ALL_NO_LIB=1 -DNDEBUG  -I"." -c -o "bin.v2/libs/test/build/gcc-7.3/release/address-model-64/architecture-x86/link-static/target-os-windows/threading-multi/visibility-hidden/compiler_log_formatter.o" "libs/test/src/compiler_log_formatter.cpp"

x86_64-w64-mingw32-g++: error: unrecognized command line option ‘-fcf-protection=full’; did you mean ‘-fstack-protector-all’?
...failed gcc.compile.c++ bin.v2/libs/test/build/gcc-7.3/release/address-model-64/architecture-x86/link-static/target-os-windows/threading-multi/visibility-hidden/compiler_log_formatter.o...
gcc.compile.c++ bin.v2/libs/test/build/gcc-7.3/release/address-model-64/architecture-x86/link-static/target-os-windows/threading-multi/visibility-hidden/decorator.o

    "x86_64-w64-mingw32-g++"   -fvisibility-inlines-hidden -pipe -O2 -std=c++17   -fcf-protection=full   -m64 -mthreads -O3 -finline-functions -Wno-inline -Wall -fvisibility=hidden   -I/home/mironkraft/XXXXXXCoin/depends/x86_64-w64-mingw32/include      -DBOOST_ALL_NO_LIB=1 -DNDEBUG  -I"." -c -o "bin.v2/libs/test/build/gcc-7.3/release/address-model-64/architecture-x86/link-static/target-os-windows/threading-multi/visibility-hidden/decorator.o" "libs/test/src/decorator.cpp"

x86_64-w64-mingw32-g++: error: unrecognized command line option ‘-fcf-protection=full’; did you mean ‘-fstack-protector-all’?
...failed gcc.compile.c++ bin.v2/libs/test/build/gcc-7.3/release/address-model-64/architecture-x86/link-static/target-os-windows/threading-multi/visibility-hidden/decorator.o...
gcc.compile.c++ bin.v2/libs/test/build/gcc-7.3/release/address-model-64/architecture-x86/link-static/target-os-windows/threading-multi/visibility-hidden/framework.o

    "x86_64-w64-mingw32-g++"   -fvisibility-inlines-hidden -pipe -O2 -std=c++17   -fcf-protection=full   -m64 -mthreads -O3 -finline-functions -Wno-inline -Wall -fvisibility=hidden   -I/home/mironkraft/XXXXXXCoin/depends/x86_64-w64-mingw32/include      -DBOOST_ALL_NO_LIB=1 -DNDEBUG  -I"." -c -o "bin.v2/libs/test/build/gcc-7.3/release/address-model-64/architecture-x86/link-static/target-os-windows/threading-multi/visibility-hidden/framework.o" "libs/test/src/framework.cpp"

x86_64-w64-mingw32-g++: error: unrecognized command line option ‘-fcf-protection=full’; did you mean ‘-fstack-protector-all’?
...failed gcc.compile.c++ bin.v2/libs/test/build/gcc-7.3/release/address-model-64/architecture-x86/link-static/target-os-windows/threading-multi/visibility-hidden/framework.o...
gcc.compile.c++ bin.v2/libs/test/build/gcc-7.3/release/address-model-64/architecture-x86/link-static/target-os-windows/threading-multi/visibility-hidden/plain_report_formatter.o

    "x86_64-w64-mingw32-g++"   -fvisibility-inlines-hidden -pipe -O2 -std=c++17   -fcf-protection=full   -m64 -mthreads -O3 -finline-functions -Wno-inline -Wall -fvisibility=hidden   -I/home/mironkraft/XXXXXXCoin/depends/x86_64-w64-mingw32/include      -DBOOST_ALL_NO_LIB=1 -DNDEBUG  -I"." -c -o "bin.v2/libs/test/build/gcc-7.3/release/address-model-64/architecture-x86/link-static/target-os-windows/threading-multi/visibility-hidden/plain_report_formatter.o" "libs/test/src/plain_report_formatter.cpp"

x86_64-w64-mingw32-g++: error: unrecognized command line option ‘-fcf-protection=full’; did you mean ‘-fstack-protector-all’?
...failed gcc.compile.c++ bin.v2/libs/test/build/gcc-7.3/release/address-model-64/architecture-x86/link-static/target-os-windows/threading-multi/visibility-hidden/plain_report_formatter.o...
gcc.compile.c++ bin.v2/libs/test/build/gcc-7.3/release/address-model-64/architecture-x86/link-static/target-os-windows/threading-multi/visibility-hidden/progress_monitor.o

    "x86_64-w64-mingw32-g++"   -fvisibility-inlines-hidden -pipe -O2 -std=c++17   -fcf-protection=full   -m64 -mthreads -O3 -finline-functions -Wno-inline -Wall -fvisibility=hidden   -I/home/mironkraft/XXXXXXCoin/depends/x86_64-w64-mingw32/include      -DBOOST_ALL_NO_LIB=1 -DNDEBUG  -I"." -c -o "bin.v2/libs/test/build/gcc-7.3/release/address-model-64/architecture-x86/link-static/target-os-windows/threading-multi/visibility-hidden/progress_monitor.o" "libs/test/src/progress_monitor.cpp"

x86_64-w64-mingw32-g++: error: unrecognized command line option ‘-fcf-protection=full’; did you mean ‘-fstack-protector-all’?
...failed gcc.compile.c++ bin.v2/libs/test/build/gcc-7.3/release/address-model-64/architecture-x86/link-static/target-os-windows/threading-multi/visibility-hidden/progress_monitor.o...
gcc.compile.c++ bin.v2/libs/test/build/gcc-7.3/release/address-model-64/architecture-x86/link-static/target-os-windows/threading-multi/visibility-hidden/results_collector.o

    "x86_64-w64-mingw32-g++"   -fvisibility-inlines-hidden -pipe -O2 -std=c++17   -fcf-protection=full   -m64 -mthreads -O3 -finline-functions -Wno-inline -Wall -fvisibility=hidden   -I/home/mironkraft/XXXXXXCoin/depends/x86_64-w64-mingw32/include      -DBOOST_ALL_NO_LIB=1 -DNDEBUG  -I"." -c -o "bin.v2/libs/test/build/gcc-7.3/release/address-model-64/architecture-x86/link-static/target-os-windows/threading-multi/visibility-hidden/results_collector.o" "libs/test/src/results_collector.cpp"

x86_64-w64-mingw32-g++: error: unrecognized command line option ‘-fcf-protection=full’; did you mean ‘-fstack-protector-all’?
...failed gcc.compile.c++ bin.v2/libs/test/build/gcc-7.3/release/address-model-64/architecture-x86/link-static/target-os-windows/threading-multi/visibility-hidden/results_collector.o...
gcc.compile.c++ bin.v2/libs/test/build/gcc-7.3/release/address-model-64/architecture-x86/link-static/target-os-windows/threading-multi/visibility-hidden/results_reporter.o

    "x86_64-w64-mingw32-g++"   -fvisibility-inlines-hidden -pipe -O2 -std=c++17   -fcf-protection=full   -m64 -mthreads -O3 -finline-functions -Wno-inline -Wall -fvisibility=hidden   -I/home/mironkraft/XXXXXXCoin/depends/x86_64-w64-mingw32/include      -DBOOST_ALL_NO_LIB=1 -DNDEBUG  -I"." -c -o "bin.v2/libs/test/build/gcc-7.3/release/address-model-64/architecture-x86/link-static/target-os-windows/threading-multi/visibility-hidden/results_reporter.o" "libs/test/src/results_reporter.cpp"

x86_64-w64-mingw32-g++: error: unrecognized command line option ‘-fcf-protection=full’; did you mean ‘-fstack-protector-all’?
...failed gcc.compile.c++ bin.v2/libs/test/build/gcc-7.3/release/address-model-64/architecture-x86/link-static/target-os-windows/threading-multi/visibility-hidden/results_reporter.o...
gcc.compile.c++ bin.v2/libs/test/build/gcc-7.3/release/address-model-64/architecture-x86/link-static/target-os-windows/threading-multi/visibility-hidden/test_framework_init_observer.o

    "x86_64-w64-mingw32-g++"   -fvisibility-inlines-hidden -pipe -O2 -std=c++17   -fcf-protection=full   -m64 -mthreads -O3 -finline-functions -Wno-inline -Wall -fvisibility=hidden   -I/home/mironkraft/XXXXXXCoin/depends/x86_64-w64-mingw32/include      -DBOOST_ALL_NO_LIB=1 -DNDEBUG  -I"." -c -o "bin.v2/libs/test/build/gcc-7.3/release/address-model-64/architecture-x86/link-static/target-os-windows/threading-multi/visibility-hidden/test_framework_init_observer.o" "libs/test/src/test_framework_init_observer.cpp"

x86_64-w64-mingw32-g++: error: unrecognized command line option ‘-fcf-protection=full’; did you mean ‘-fstack-protector-all’?
...failed gcc.compile.c++ bin.v2/libs/test/build/gcc-7.3/release/address-model-64/architecture-x86/link-static/target-os-windows/threading-multi/visibility-hidden/test_framework_init_observer.o...
gcc.compile.c++ bin.v2/libs/test/build/gcc-7.3/release/address-model-64/architecture-x86/link-static/target-os-windows/threading-multi/visibility-hidden/test_main.o

    "x86_64-w64-mingw32-g++"   -fvisibility-inlines-hidden -pipe -O2 -std=c++17   -fcf-protection=full   -m64 -mthreads -O3 -finline-functions -Wno-inline -Wall -fvisibility=hidden   -I/home/mironkraft/XXXXXXCoin/depends/x86_64-w64-mingw32/include      -DBOOST_ALL_NO_LIB=1 -DNDEBUG  -I"." -c -o "bin.v2/libs/test/build/gcc-7.3/release/address-model-64/architecture-x86/link-static/target-os-windows/threading-multi/visibility-hidden/test_main.o" "libs/test/src/test_main.cpp"

x86_64-w64-mingw32-g++: error: unrecognized command line option ‘-fcf-protection=full’; did you mean ‘-fstack-protector-all’?
...failed gcc.compile.c++ bin.v2/libs/test/build/gcc-7.3/release/address-model-64/architecture-x86/link-static/target-os-windows/threading-multi/visibility-hidden/test_main.o...
gcc.compile.c++ bin.v2/libs/test/build/gcc-7.3/release/address-model-64/architecture-x86/link-static/target-os-windows/threading-multi/visibility-hidden/test_tools.o

    "x86_64-w64-mingw32-g++"   -fvisibility-inlines-hidden -pipe -O2 -std=c++17   -fcf-protection=full   -m64 -mthreads -O3 -finline-functions -Wno-inline -Wall -fvisibility=hidden   -I/home/mironkraft/XXXXXXCoin/depends/x86_64-w64-mingw32/include      -DBOOST_ALL_NO_LIB=1 -DNDEBUG  -I"." -c -o "bin.v2/libs/test/build/gcc-7.3/release/address-model-64/architecture-x86/link-static/target-os-windows/threading-multi/visibility-hidden/test_tools.o" "libs/test/src/test_tools.cpp"

x86_64-w64-mingw32-g++: error: unrecognized command line option ‘-fcf-protection=full’; did you mean ‘-fstack-protector-all’?
...failed gcc.compile.c++ bin.v2/libs/test/build/gcc-7.3/release/address-model-64/architecture-x86/link-static/target-os-windows/threading-multi/visibility-hidden/test_tools.o...
gcc.compile.c++ bin.v2/libs/test/build/gcc-7.3/release/address-model-64/architecture-x86/link-static/target-os-windows/threading-multi/visibility-hidden/test_tree.o

    "x86_64-w64-mingw32-g++"   -fvisibility-inlines-hidden -pipe -O2 -std=c++17   -fcf-protection=full   -m64 -mthreads -O3 -finline-functions -Wno-inline -Wall -fvisibility=hidden   -I/home/mironkraft/XXXXXXCoin/depends/x86_64-w64-mingw32/include      -DBOOST_ALL_NO_LIB=1 -DNDEBUG  -I"." -c -o "bin.v2/libs/test/build/gcc-7.3/release/address-model-64/architecture-x86/link-static/target-os-windows/threading-multi/visibility-hidden/test_tree.o" "libs/test/src/test_tree.cpp"

x86_64-w64-mingw32-g++: error: unrecognized command line option ‘-fcf-protection=full’; did you mean ‘-fstack-protector-all’?
...failed gcc.compile.c++ bin.v2/libs/test/build/gcc-7.3/release/address-model-64/architecture-x86/link-static/target-os-windows/threading-multi/visibility-hidden/test_tree.o...
gcc.compile.c++ bin.v2/libs/test/build/gcc-7.3/release/address-model-64/architecture-x86/link-static/target-os-windows/threading-multi/visibility-hidden/unit_test_log.o

    "x86_64-w64-mingw32-g++"   -fvisibility-inlines-hidden -pipe -O2 -std=c++17   -fcf-protection=full   -m64 -mthreads -O3 -finline-functions -Wno-inline -Wall -fvisibility=hidden   -I/home/mironkraft/XXXXXXCoin/depends/x86_64-w64-mingw32/include      -DBOOST_ALL_NO_LIB=1 -DNDEBUG  -I"." -c -o "bin.v2/libs/test/build/gcc-7.3/release/address-model-64/architecture-x86/link-static/target-os-windows/threading-multi/visibility-hidden/unit_test_log.o" "libs/test/src/unit_test_log.cpp"

x86_64-w64-mingw32-g++: error: unrecognized command line option ‘-fcf-protection=full’; did you mean ‘-fstack-protector-all’?
...failed gcc.compile.c++ bin.v2/libs/test/build/gcc-7.3/release/address-model-64/architecture-x86/link-static/target-os-windows/threading-multi/visibility-hidden/unit_test_log.o...
gcc.compile.c++ bin.v2/libs/test/build/gcc-7.3/release/address-model-64/architecture-x86/link-static/target-os-windows/threading-multi/visibility-hidden/unit_test_main.o

    "x86_64-w64-mingw32-g++"   -fvisibility-inlines-hidden -pipe -O2 -std=c++17   -fcf-protection=full   -m64 -mthreads -O3 -finline-functions -Wno-inline -Wall -fvisibility=hidden   -I/home/mironkraft/XXXXXXCoin/depends/x86_64-w64-mingw32/include      -DBOOST_ALL_NO_LIB=1 -DNDEBUG  -I"." -c -o "bin.v2/libs/test/build/gcc-7.3/release/address-model-64/architecture-x86/link-static/target-os-windows/threading-multi/visibility-hidden/unit_test_main.o" "libs/test/src/unit_test_main.cpp"

x86_64-w64-mingw32-g++: error: unrecognized command line option ‘-fcf-protection=full’; did you mean ‘-fstack-protector-all’?
...failed gcc.compile.c++ bin.v2/libs/test/build/gcc-7.3/release/address-model-64/architecture-x86/link-static/target-os-windows/threading-multi/visibility-hidden/unit_test_main.o...
gcc.compile.c++ bin.v2/libs/test/build/gcc-7.3/release/address-model-64/architecture-x86/link-static/target-os-windows/threading-multi/visibility-hidden/unit_test_monitor.o

    "x86_64-w64-mingw32-g++"   -fvisibility-inlines-hidden -pipe -O2 -std=c++17   -fcf-protection=full   -m64 -mthreads -O3 -finline-functions -Wno-inline -Wall -fvisibility=hidden   -I/home/mironkraft/XXXXXXCoin/depends/x86_64-w64-mingw32/include      -DBOOST_ALL_NO_LIB=1 -DNDEBUG  -I"." -c -o "bin.v2/libs/test/build/gcc-7.3/release/address-model-64/architecture-x86/link-static/target-os-windows/threading-multi/visibility-hidden/unit_test_monitor.o" "libs/test/src/unit_test_monitor.cpp"

x86_64-w64-mingw32-g++: error: unrecognized command line option ‘-fcf-protection=full’; did you mean ‘-fstack-protector-all’?
...failed gcc.compile.c++ bin.v2/libs/test/build/gcc-7.3/release/address-model-64/architecture-x86/link-static/target-os-windows/threading-multi/visibility-hidden/unit_test_monitor.o...
gcc.compile.c++ bin.v2/libs/test/build/gcc-7.3/release/address-model-64/architecture-x86/link-static/target-os-windows/threading-multi/visibility-hidden/unit_test_parameters.o

    "x86_64-w64-mingw32-g++"   -fvisibility-inlines-hidden -pipe -O2 -std=c++17   -fcf-protection=full   -m64 -mthreads -O3 -finline-functions -Wno-inline -Wall -fvisibility=hidden   -I/home/mironkraft/XXXXXXCoin/depends/x86_64-w64-mingw32/include      -DBOOST_ALL_NO_LIB=1 -DNDEBUG  -I"." -c -o "bin.v2/libs/test/build/gcc-7.3/release/address-model-64/architecture-x86/link-static/target-os-windows/threading-multi/visibility-hidden/unit_test_parameters.o" "libs/test/src/unit_test_parameters.cpp"

x86_64-w64-mingw32-g++: error: unrecognized command line option ‘-fcf-protection=full’; did you mean ‘-fstack-protector-all’?
...failed gcc.compile.c++ bin.v2/libs/test/build/gcc-7.3/release/address-model-64/architecture-x86/link-static/target-os-windows/threading-multi/visibility-hidden/unit_test_parameters.o...
gcc.compile.c++ bin.v2/libs/test/build/gcc-7.3/release/address-model-64/architecture-x86/link-static/target-os-windows/threading-multi/visibility-hidden/junit_log_formatter.o

    "x86_64-w64-mingw32-g++"   -fvisibility-inlines-hidden -pipe -O2 -std=c++17   -fcf-protection=full   -m64 -mthreads -O3 -finline-functions -Wno-inline -Wall -fvisibility=hidden   -I/home/mironkraft/XXXXXXCoin/depends/x86_64-w64-mingw32/include      -DBOOST_ALL_NO_LIB=1 -DNDEBUG  -I"." -c -o "bin.v2/libs/test/build/gcc-7.3/release/address-model-64/architecture-x86/link-static/target-os-windows/threading-multi/visibility-hidden/junit_log_formatter.o" "libs/test/src/junit_log_formatter.cpp"

x86_64-w64-mingw32-g++: error: unrecognized command line option ‘-fcf-protection=full’; did you mean ‘-fstack-protector-all’?
...failed gcc.compile.c++ bin.v2/libs/test/build/gcc-7.3/release/address-model-64/architecture-x86/link-static/target-os-windows/threading-multi/visibility-hidden/junit_log_formatter.o...
gcc.compile.c++ bin.v2/libs/test/build/gcc-7.3/release/address-model-64/architecture-x86/link-static/target-os-windows/threading-multi/visibility-hidden/xml_log_formatter.o

    "x86_64-w64-mingw32-g++"   -fvisibility-inlines-hidden -pipe -O2 -std=c++17   -fcf-protection=full   -m64 -mthreads -O3 -finline-functions -Wno-inline -Wall -fvisibility=hidden   -I/home/mironkraft/XXXXXXCoin/depends/x86_64-w64-mingw32/include      -DBOOST_ALL_NO_LIB=1 -DNDEBUG  -I"." -c -o "bin.v2/libs/test/build/gcc-7.3/release/address-model-64/architecture-x86/link-static/target-os-windows/threading-multi/visibility-hidden/xml_log_formatter.o" "libs/test/src/xml_log_formatter.cpp"

x86_64-w64-mingw32-g++: error: unrecognized command line option ‘-fcf-protection=full’; did you mean ‘-fstack-protector-all’?
...failed gcc.compile.c++ bin.v2/libs/test/build/gcc-7.3/release/address-model-64/architecture-x86/link-static/target-os-windows/threading-multi/visibility-hidden/xml_log_formatter.o...
gcc.compile.c++ bin.v2/libs/test/build/gcc-7.3/release/address-model-64/architecture-x86/link-static/target-os-windows/threading-multi/visibility-hidden/xml_report_formatter.o

    "x86_64-w64-mingw32-g++"   -fvisibility-inlines-hidden -pipe -O2 -std=c++17   -fcf-protection=full   -m64 -mthreads -O3 -finline-functions -Wno-inline -Wall -fvisibility=hidden   -I/home/mironkraft/XXXXXXCoin/depends/x86_64-w64-mingw32/include      -DBOOST_ALL_NO_LIB=1 -DNDEBUG  -I"." -c -o "bin.v2/libs/test/build/gcc-7.3/release/address-model-64/architecture-x86/link-static/target-os-windows/threading-multi/visibility-hidden/xml_report_formatter.o" "libs/test/src/xml_report_formatter.cpp"

x86_64-w64-mingw32-g++: error: unrecognized command line option ‘-fcf-protection=full’; did you mean ‘-fstack-protector-all’?
...failed gcc.compile.c++ bin.v2/libs/test/build/gcc-7.3/release/address-model-64/architecture-x86/link-static/target-os-windows/threading-multi/visibility-hidden/xml_report_formatter.o...
...skipped libboost_test_exec_monitor-mt-s-x64.a(clean) for lack of compiler_log_formatter.o...
...skipped libboost_test_exec_monitor-mt-s-x64.a for lack of compiler_log_formatter.o...
...skipped 
libboost_test_exec_monitor-mt-s-x64.a for lack of libboost_test_exec_monitor-mt-s-x64.a...
...skipped libboost_unit_test_framework-mt-s-x64.a(clean) for lack of compiler_log_formatter.o...
...skipped libboost_unit_test_framework-mt-s-x64.a for lack of compiler_log_formatter.o...
...skipped 
libboost_unit_test_framework-mt-s-x64.a for lack of libboost_unit_test_framework-mt-s-x64.a...
...failed updating 30 targets...
...skipped 15 targets...
funcs.mk:280: recipe for target '/home/mironkraft/XXXXXXCoin/depends/work/build/x86_64-w64-mingw32/boost/1_71_0-a4540decc39/./.stamp_built' failed
make: *** [/home/mironkraft/XXXXXXCoin/depends/work/build/x86_64-w64-mingw32/boost/1_71_0-a4540decc39/./.stamp_built] Error 1

mironkraft

jr. member

Activity: 78

Merit: 4

ok, it started to build a while, but it gives me this error:

Code:

funcs.mk:280: recipe for target '/home/mironkraft/xxxxxCoin/depends/work/build/x86_64-w64-mingw32/boost/1_71_0-a4540decc39/./.stamp_built' failed
make: *** [/home/mironkraft/xxxxxCoin/depends/work/build/x86_64-w64-mingw32/boost/1_71_0-a4540decc39/./.stamp_built] Error 1
mironkraft@DESKTOP-Q44IAMD:~/xxxxxCoin/depends$ ./autogen.sh
-bash: ./autogen.sh: No such file or directory
mironkraft@DESKTOP-Q44IAMD:~/xxxxxCoin/depends$ cd ..
mironkraft@DESKTOP-Q44IAMD:~/xxxxxCoin$ ./autogen.sh
autom4te: cannot create autom4te.cache: No such file or directory
aclocal: error: echo failed with exit status: 1
autoreconf: aclocal failed with exit status: 1
mironkraft@DESKTOP-Q44IAMD:~/xxxxxCoin$

im researching on the net, but nothing clear

mironkraft

jr. member

Activity: 78

Merit: 4

Quote from: mironkraft on February 04, 2022, 05:05:01 PM

Quote from: BlackHatCoiner on February 04, 2022, 04:26:37 PM

You still haven't answered to my question, though.

Quote from: BlackHatCoiner on January 30, 2022, 02:18:47 PM

Have you build your altcoin with Satoshi's block, just to see it working?

Ok, I am right now on your tutorial, this step:

Code:

mironkraft@DESKTOP-Q44IAMD:~$ sudo apt install g++-mingw-w64-x86-64
[sudo] password for mironkraft:
Reading package lists... Done
Building dependency tree
Reading state information... Done
g++-mingw-w64-x86-64 is already the newest version (7.3.0-11ubuntu1+20.2build1).
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
mironkraft@DESKTOP-Q44IAMD:~$ PATH=$(echo "$PATH" | sed -e 's/:\/mnt.*//g')
mironkraft@DESKTOP-Q44IAMD:~$ sudo bash -c "echo 0 > /proc/sys/fs/binfmt_misc/status"
mironkraft@DESKTOP-Q44IAMD:~$ cd depends
-bash: cd: depends: No such file or directory
mironkraft@DESKTOP-Q44IAMD:~$

it fails, unless im using the code wrongly

fixed by going first to cd XXXXCoin folder, then again cd depends and keep coding the next lines

mironkraft

jr. member

Activity: 78

Merit: 4

Quote from: BlackHatCoiner on February 04, 2022, 04:26:37 PM

You still haven't answered to my question, though.

Quote from: BlackHatCoiner on January 30, 2022, 02:18:47 PM

Have you build your altcoin with Satoshi's block, just to see it working?

Ok, I am right now on your tutorial, this step:

Code:

mironkraft@DESKTOP-Q44IAMD:~$ sudo apt install g++-mingw-w64-x86-64
[sudo] password for mironkraft:
Reading package lists... Done
Building dependency tree
Reading state information... Done
g++-mingw-w64-x86-64 is already the newest version (7.3.0-11ubuntu1+20.2build1).
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
mironkraft@DESKTOP-Q44IAMD:~$ PATH=$(echo "$PATH" | sed -e 's/:\/mnt.*//g')
mironkraft@DESKTOP-Q44IAMD:~$ sudo bash -c "echo 0 > /proc/sys/fs/binfmt_misc/status"
mironkraft@DESKTOP-Q44IAMD:~$ cd depends
-bash: cd: depends: No such file or directory
mironkraft@DESKTOP-Q44IAMD:~$

it fails, unless im using the code wrongly

mironkraft

jr. member

Activity: 78

Merit: 4

Quote from: BlackHatCoiner on February 04, 2022, 04:26:37 PM

You still haven't answered to my question, though.

Quote from: BlackHatCoiner on January 30, 2022, 02:18:47 PM

Have you build your altcoin with Satoshi's block, just to see it working?

LOL! didnt see this one

nope never did

let me get back to the point of your tutorial and ill feedback you asap

BlackHatCoiner

legendary

Activity: 1512

Merit: 7340

Farewell, Leo

You still haven't answered to my question, though.

Quote from: BlackHatCoiner on January 30, 2022, 02:18:47 PM

Have you build your altcoin with Satoshi's block, just to see it working?

mironkraft

jr. member

Activity: 78

Merit: 4

OMG!!!! Wait a minute!!!!

I have to modify the text inside of genesys.py and execute the mining right?

Modify the genesis text of bitcoin to my coin and then mine the first block... right?

Hi! I have tried this both, I will leave till finish and see what happens

mironkraft

jr. member

Activity: 78

Merit: 4

Quote from: BlackHatCoiner on February 02, 2022, 03:39:44 AM

Quote from: mironkraft on February 01, 2022, 03:59:43 PM

if I want to make my own pubkey i have to:

Code:

python genesis.py -z "XXXXXXXXXXX" -n 2083236893 -t 161XXXXX06

This code is executed when you want to mine the genesis block. The easiest way to generate a public key is by going to this page. It's not the best way, but it's the easiest. For someone like you who just wants to see it working, it's fine.

Quote from: mironkraft on February 01, 2022, 03:59:43 PM

So, when all this done, I gotta do:

I honestly don't know what's this genesis block generator you've brought me. I didn't give you any python scripts. I told you to either run the genesis.exe or build the genesis.c. No, it's not normal to take you 24 hours for a block with difficulty=1.

okay, I will use the pubkey thats given that webpage

well, the scrip finished like this:

Code:

37992.0 hash/s, estimate: 31.4 h^L
109529.0 hash/s, estimate: 10.9 hTraceback (most recent call last):
  File "genesis.py", line 203, in 
    main()
  File "genesis.py", line 20, in main
    genesis_hash, nonce = generate_hash(block_header, algorithm, options.nonce, options.bits)
  File "genesis.py", line 140, in generate_hash
    data_block = data_block[0:len(data_block) - 4] + struct.pack('struct.error: 'I' format requires 0 <= number <= 4294967295

About runing genesis.exe, what I should do exactly?

Thanks, and sorry if im mixing myself

BlackHatCoiner

legendary

Activity: 1512

Merit: 7340

Farewell, Leo

Quote from: mironkraft on February 01, 2022, 03:59:43 PM

if I want to make my own pubkey i have to:

Code:

python genesis.py -z "XXXXXXXXXXX" -n 2083236893 -t 161XXXXX06

This code is executed when you want to mine the genesis block. The easiest way to generate a public key is by going to this page. It's not the best way, but it's the easiest. For someone like you who just wants to see it working, it's fine.

Quote from: mironkraft on February 01, 2022, 03:59:43 PM

So, when all this done, I gotta do:

I honestly don't know what's this genesis block generator you've brought me. I didn't give you any python scripts. I told you to either run the genesis.exe or build the genesis.c. No, it's not normal to take you 24 hours for a block with difficulty=1.

mironkraft

jr. member

Activity: 78

Merit: 4

Quote from: mironkraft on February 01, 2022, 03:59:43 PM

Quote from: BlackHatCoiner on January 30, 2022, 02:18:47 PM

Quote from: mironkraft on January 30, 2022, 12:40:29 PM

how I build the binaries?

It's written in the github link I've given you:

Code:

gcc generator.c -o generator -lcrypto

Quote from: mironkraft on January 30, 2022, 12:40:29 PM

If i go to generate, how or where I get this info:

The pubkey is your public key in uncompressed format. You could leave Satoshi's if you don't care of proving the ownership of your genesis block. In timestamp, just insert any unix timestamp you want. Leave nBits unchanged, it has to do with the difficulty.

Quote from: mironkraft on January 30, 2022, 12:40:29 PM

the zip from zippyshare is not working the link

It works for me. I just uploaded to files.fm, check: https://files.fm/u/8sgp9adw7

Have you build your altcoin with Satoshi's block, just to see it working?

Perfect,

I will create my own pubkey, I followed:

https://github.com/lhartikk/GenesisH0

installed, with some problems till I made the example of block

for those problems, I did:

Code:

install pip
install python (x3)
other dependencies

and if nothing works, with this:
sudo apt-get install python-pip
pip install scrypt construct
pip install construct==2.5.2

finaly:

Quote

root@DESKTOP-Q44IAMD:/home/mironkraft/GenesisH0-master# python genesis.py -z "The Times 03/Jan/2009 Chancellor on brink of second bailout for banks" -n 2083236893 -t 1231006505
04ffff001d0104455468652054696d65732030332f4a616e2f32303039204368616e63656c6c6f7 2206f6e206272696e6b206f66207365636f6e64206261696c6f757420666f722062616e6b73
algorithm: SHA256
merkle hash: 4a5e1e4baab89f3a32518a88c31bc87f618f76673e2cc77ab2127b7afdeda33b
pszTimestamp: The Times 03/Jan/2009 Chancellor on brink of second bailout for banks
pubkey: 04678afdb0fe5548271967f1a67130b7105cd6a828e03909a67962e0ea1f61deb649f6bc3f4cef3 8c4f35504e51ec112de5c384df7ba0b8d578a4c702b6bf11d5f
time: 1231006505
bits: 0x1d00ffff
Searching for genesis hash..
genesis hash found!
nonce: 2083236893
genesis hash: 000000000019d6689c085ae165831e934ff763ae46a2a6c172b3f1b60a8ce26f

wich confirms it works fine

So, my question is:

if I want to make my own pubkey i have to:

Code:

python genesis.py -z "XXXXXXXXXXX" -n 2083236893 -t 161XXXXX06

what means the NONCE, -n 2083236893 ? I mean, what configuration is this for? (it is related with the dificulty? I dont have to change it?)

So, when all this done, I gotta do:

genesis.exe >

Usage: genesisgen [options] ""

genesisgen 04678afdb0fe5548271967f1a67130b7105cd6a828e03909a67962e0ea1f61deb649f6bc3f4cef3 8c4f35504e51ec112de5c384df7ba0b8d578a4c702b6bf11d5f "161XXXXX06" 2083236893

I am right if this are the steps?

thanks!

Also, I am already launched it and...

Code:

root@DESKTOP-Q44IAMD:/home/mironkraft/GenesisH0-master# python genesis.py -z "XXXXX, since 2019, bla bla bla bla " -n 2083236893 -t xxxxxxxx
04ffff001d01044441XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX573732c2046696e616e636520262050656f706c65
algorithm: SHA256
merkle hash: 0d34cb7841c610dXXXXXXXXXXXXXXXXX0262bb850
pszTimestamp: XXXXX, since 2019, bla bla bla bla 
pubkey: 04678XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX02b6bf11d5f
time: 1613XXX206
bits: 0x1d00ffff
Searching for genesis hash..
49802.0 hash/s, estimate: 24.0 h

it is normal to get 24hrs or more of work?... its been executed right now

mironkraft

jr. member

Activity: 78

Merit: 4

Quote from: BlackHatCoiner on January 30, 2022, 02:18:47 PM

Quote from: mironkraft on January 30, 2022, 12:40:29 PM

how I build the binaries?

It's written in the github link I've given you:

Code:

gcc generator.c -o generator -lcrypto

Quote from: mironkraft on January 30, 2022, 12:40:29 PM

If i go to generate, how or where I get this info:

The pubkey is your public key in uncompressed format. You could leave Satoshi's if you don't care of proving the ownership of your genesis block. In timestamp, just insert any unix timestamp you want. Leave nBits unchanged, it has to do with the difficulty.

Quote from: mironkraft on January 30, 2022, 12:40:29 PM

the zip from zippyshare is not working the link

It works for me. I just uploaded to files.fm, check: https://files.fm/u/8sgp9adw7

Have you build your altcoin with Satoshi's block, just to see it working?

Perfect,

I will create my own pubkey, I followed:

https://github.com/lhartikk/GenesisH0

installed, with some problems till I made the example of block

for those problems, I did:

Code:

install pip
install python (x3)
other dependencies

and if nothing works, with this:
sudo apt-get install python-pip
pip install scrypt construct
pip install construct==2.5.2

finaly:

Quote

root@DESKTOP-Q44IAMD:/home/mironkraft/GenesisH0-master# python genesis.py -z "The Times 03/Jan/2009 Chancellor on brink of second bailout for banks" -n 2083236893 -t 1231006505
04ffff001d0104455468652054696d65732030332f4a616e2f32303039204368616e63656c6c6f7 2206f6e206272696e6b206f66207365636f6e64206261696c6f757420666f722062616e6b73
algorithm: SHA256
merkle hash: 4a5e1e4baab89f3a32518a88c31bc87f618f76673e2cc77ab2127b7afdeda33b
pszTimestamp: The Times 03/Jan/2009 Chancellor on brink of second bailout for banks
pubkey: 04678afdb0fe5548271967f1a67130b7105cd6a828e03909a67962e0ea1f61deb649f6bc3f4cef3 8c4f35504e51ec112de5c384df7ba0b8d578a4c702b6bf11d5f
time: 1231006505
bits: 0x1d00ffff
Searching for genesis hash..
genesis hash found!
nonce: 2083236893
genesis hash: 000000000019d6689c085ae165831e934ff763ae46a2a6c172b3f1b60a8ce26f

wich confirms it works fine

So, my question is:

if I want to make my own pubkey i have to:

Code:

python genesis.py -z "XXXXXXXXXXX" -n 2083236893 -t 161XXXXX06

what means the NONCE, -n 2083236893 ? I mean, what configuration is this for? (it is related with the dificulty? I dont have to change it?)

So, when all this done, I gotta do:

genesis.exe >

Usage: genesisgen [options] ""

genesisgen 04678afdb0fe5548271967f1a67130b7105cd6a828e03909a67962e0ea1f61deb649f6bc3f4cef3 8c4f35504e51ec112de5c384df7ba0b8d578a4c702b6bf11d5f "161XXXXX06" 2083236893

I am right if this are the steps?

thanks!

BlackHatCoiner

legendary

Activity: 1512

Merit: 7340

Farewell, Leo

Quote from: mironkraft on January 30, 2022, 12:40:29 PM

how I build the binaries?

It's written in the github link I've given you:

Code:

gcc generator.c -o generator -lcrypto

Quote from: mironkraft on January 30, 2022, 12:40:29 PM

If i go to generate, how or where I get this info:

The pubkey is your public key in uncompressed format. You could leave Satoshi's if you don't care of proving the ownership of your genesis block. In timestamp, just insert any unix timestamp you want. Leave nBits unchanged, it has to do with the difficulty.

Quote from: mironkraft on January 30, 2022, 12:40:29 PM

the zip from zippyshare is not working the link

It works for me. I just uploaded to files.fm, check: https://files.fm/u/8sgp9adw7

Have you build your altcoin with Satoshi's block, just to see it working?

mironkraft

jr. member

Activity: 78

Merit: 4

Quote from: BlackHatCoiner on January 30, 2022, 09:40:54 AM

You don't have to build the genesis block generator in Ubuntu. Just build the binaries to your Windows 10, generate a valid genesis block and replace the values accordingly. You can accomplish the building by having the source code and gcc.

If you don't care about verifying that you're building from source code, I've built it for you: genesis.zip. Unzip it and execute it using your cmd and the proper parameters.

hmmm... I will try but some questions:

how I build the binaries?
how I generate the genesis block?

If i go to generate, how or where I get this info:

the zip from zippyshare is not working the link

ill be back If i achieve it.. if not i will cry so much (xD)

thanks as alwasy for your time, appreciate it

BlackHatCoiner

legendary

Activity: 1512

Merit: 7340

Farewell, Leo

You don't have to build the genesis block generator in Ubuntu. Just build the binaries to your Windows 10, generate a valid genesis block and replace the values accordingly. You can accomplish the building by having the source code and gcc.

If you don't care about verifying that you're building from source code, I've built it for you: genesis.zip. Unzip it and execute it using your cmd and the proper parameters.

mironkraft

jr. member

Activity: 78

Merit: 4

Also, just for testing the coin before getting with the headache of the genesis block

I tried to build as you say here:

Quote

When it is finished, we build with the following commands:

Code:

PATH=$(echo "$PATH" | sed -e 's/:\/mnt.*//g')
sudo bash -c "echo 0 > /proc/sys/fs/binfmt_misc/status"
cd depends
make HOST=x86_64-w64-mingw32
cd ..
./autogen.sh
CONFIG_SITE=$PWD/depends/x86_64-w64-mingw32/share/config.site ./configure --prefix=/
make

(It may take more than an hour)

and when I introduce that code on the ubuntu lts comand prompt nothing happens and it give error:

Code:

root@DESKTOP-Q44IAMD:/home# PATH=$(echo "$PATH" | sed -e 's/:\/mnt.*//g')
root@DESKTOP-Q44IAMD:/home# sudo bash -c "echo 0 > /proc/sys/fs/binfmt_misc/status"
root@DESKTOP-Q44IAMD:/home# cd depends
bash: cd: depends: No such file or directory
root@DESKTOP-Q44IAMD:/home# make HOST=x86_64-w64-mingw32
make: *** No targets specified and no makefile found.  Stop.
root@DESKTOP-Q44IAMD:/home# cd ..
root@DESKTOP-Q44IAMD:/# ./autogen.sh
bash: ./autogen.sh: No such file or directory
root@DESKTOP-Q44IAMD:/# CONFIG_SITE=$PWD/depends/x86_64-w64-mingw32/share/config.site ./configure --prefix=/
bash: ./configure: No such file or directory
root@DESKTOP-Q44IAMD:/# make

mironkraft

jr. member

Activity: 78

Merit: 4

Quote from: BlackHatCoiner on January 29, 2022, 06:19:28 AM

What's your operating system?

I am working in windows 10
Using ubuntu lts comand window (as your guide)

also I have if needed VMW Workstation with windows 11, ubuntu and kali linux

BlackHatCoiner

legendary

Activity: 1512

Merit: 7340

Farewell, Leo

What's your operating system?

mironkraft

jr. member

Activity: 78

Merit: 4

Quote from: BlackHatCoiner on December 24, 2021, 02:37:05 PM

Alright, so here's what you're going to do. Go on genesisgen on github, download genesis.c and build it. Once you have the executable, run name.exe .

In you should add your public key in uncompressed format. In your message. In the target. Leave it on 486604799 (1d00ffff) which is the lowest you can have with a difficulty of 1.

Once you mine the genesis block, the program will return you the coinbase script, the scriptPubKey, the merkle hash, the byteswapped merkle hash, the unix time, the nonce and finally the genesis block's hash.

1. Change the genesisOutputScript to your scriptPubKey from #L54.
2. Change genesis.hashMerkleRoot to the byteswapped merkle hash in #L114.
3. Change consensus.hashGenesisBlock to your block's hash in #L113.
4. Change the first two values from the CreateGenesisBlock function to the unix time and nonce respectively in #L111.
5. Build Bitcoin Core.

I've made a tutorial here: How to create your own altcoin (v0.20.1). It should be the same for the latest version of Bitcoin Core.

Hello blackhat, I am having a tremendous headacke trying to make the genesis block

I am trying to follow up your steps and searching info in the net but nothing that I do it´s right.

I already downloaded the genesis block folder
Opened genesis.c in sublime, but I don´t know how you build it right

I guess, I have to:

Code:

    $ make
    $ ./genesis
    Usage: ./genesis [options]  ""   
    $ ./genesis 04678afdb0fe5548271967f1a67130b7105cd6a828e03909a67962e0ea1f61deb649f6bc3f4cef38c4f35504e51ec112de5c384df7ba0b8d578a4c702b6bf11d5f "The Times 03/Jan/2009 Chancellor on brink of second bailout for banks" 486604799 2083236893 1231006505
    nBits: 0x1d00ffff
    startNonce: 2083236893
    unixtime: 1231006505

I have to make the genesis with the code given in README.md but I donkt know how to make the codes exactly

Also, how I obtain the pubkey? asfar as i read, it should be given somewhere

I am a bit lost about this step... Sad

and it is important to make it right and learn how to, since it is the most important step

Thanks for your time, as always

BlackHatCoiner

legendary

Activity: 1512

Merit: 7340

Farewell, Leo

Quote from: mironkraft on January 27, 2022, 04:37:11 PM

- do Nº 1 step, change the values and build (as told in nº 3)
- do nº 2 step, generate genesis block (as told in nº2)

You can either leave the genesis block unchanged and skip the second step or generate it, do the required changes and then build the binaries. I recommend you to do the former first, just to see it working.

Quote from: mironkraft on January 27, 2022, 04:37:11 PM

ps: about the update thing, I am just asking of how to update when we talked time ago of downloading and changing the new core and upload it again, anyways, let me finish this first and then we see the rest

Okay, do one thing at a time.

mironkraft

jr. member

Activity: 78

Merit: 4

Quote from: BlackHatCoiner on January 27, 2022, 11:36:54 AM

Quote from: mironkraft on January 27, 2022, 10:05:13 AM

if it is ok, or i have to enter some code to reach that to resumen where i was

No, you just enter to that directory.

Quote from: mironkraft on January 27, 2022, 10:05:13 AM

This is mandatory? as far as I understand if I dont have problems with Sublime Text and the files it is not needed right?

I had been using Notepad++ which changes the permissions. I don't know if that's true with Sublime Text, but it's generally true for most Windows notepads.

Quote from: mironkraft on January 27, 2022, 10:05:13 AM

3- before building, how I am suposed to change the genesis block exactly?

You need to change the values I've told you in #2 from chainparams.cpp.

Quote from: mironkraft on January 27, 2022, 10:05:13 AM

1- once finished the genesis block configuration, how i am supossed to build this rightly? wich are the "codes" to enter on terminal for it?

The commands remain the same. Once you've generated a valid genesis block, from the program you've written, you just replace those few values from chainparams.cpp and you're done.

Quote from: mironkraft on January 27, 2022, 10:05:13 AM

2- how to mining the first block? wich steps I should follow?

[ANN] Genesis Block Generator

Quote from: mironkraft on January 27, 2022, 10:05:13 AM

3- how to save the genesis block of the chain in the computer? I mean, for later use if the chain is being mined from diferent clients and I wan to update it?

You can't update the genesis block once there are new blocks mined upon it. Unless I didn't understand your question.

Quote from: mironkraft on January 27, 2022, 10:05:13 AM

4- how I am supossed to update it in the future?

You download the new version of Bitcoin Core and redo those steps.

Quote from: mironkraft on January 27, 2022, 10:05:13 AM

should I upload it to github once is start mining?

Why do you ask me such thing? It depends on what you want to accomplish.

Perfect, I will go working on and be back soon

first steps Il take:
- do Nº 1 step, change the values and build (as told in nº 3)
- do nº 2 step, generate genesis block (as told in nº2)
- start mining my own coin with the steps told back time

ps: about the update thing, I am just asking of how to update when we talked time ago of downloading and changing the new core and upload it again, anyways, let me finish this first and then we see the rest

thanks!!!!!

BlackHatCoiner

legendary

Activity: 1512

Merit: 7340

Farewell, Leo

Quote from: mironkraft on January 27, 2022, 10:05:13 AM

if it is ok, or i have to enter some code to reach that to resumen where i was

No, you just enter to that directory.

Quote from: mironkraft on January 27, 2022, 10:05:13 AM

This is mandatory? as far as I understand if I dont have problems with Sublime Text and the files it is not needed right?

I had been using Notepad++ which changes the permissions. I don't know if that's true with Sublime Text, but it's generally true for most Windows notepads.

Quote from: mironkraft on January 27, 2022, 10:05:13 AM

3- before building, how I am suposed to change the genesis block exactly?

You need to change the values I've told you in #2 from chainparams.cpp.

Quote from: mironkraft on January 27, 2022, 10:05:13 AM

1- once finished the genesis block configuration, how i am supossed to build this rightly? wich are the "codes" to enter on terminal for it?

The commands remain the same. Once you've generated a valid genesis block, from the program you've written, you just replace those few values from chainparams.cpp and you're done.

Quote from: mironkraft on January 27, 2022, 10:05:13 AM

2- how to mining the first block? wich steps I should follow?

[ANN] Genesis Block Generator

Quote from: mironkraft on January 27, 2022, 10:05:13 AM

3- how to save the genesis block of the chain in the computer? I mean, for later use if the chain is being mined from diferent clients and I wan to update it?

You can't update the genesis block once there are new blocks mined upon it. Unless I didn't understand your question.

Quote from: mironkraft on January 27, 2022, 10:05:13 AM

4- how I am supossed to update it in the future?

You download the new version of Bitcoin Core and redo those steps.

Quote from: mironkraft on January 27, 2022, 10:05:13 AM

should I upload it to github once is start mining?

Why do you ask me such thing? It depends on what you want to accomplish.

mironkraft

jr. member

Activity: 78

Merit: 4

Quote from: BlackHatCoiner on January 02, 2022, 08:41:33 AM

Hi, sorry for forgetting to reply.

Quote from: mironkraft on December 29, 2021, 02:52:35 PM

I was meaning that If I change the letters so was "styling" or making it diferent from bitcoin ones, nevermind it, ill keep them from bitcoin, i guess it doesnt matter

Keep them the same yeah. The only downside is that the users of your altcoin can't distinguish the addresses of bitcoin and yours. Again, leave that for later, build your altcoin first.

Quote from: mironkraft on December 29, 2021, 02:52:35 PM

Could youplease tell me how I am supposed to test the coin if I did not managed to finish it? I mean, before building it i guess

You can't test the coin without building the binaries.

Quote from: mironkraft on December 29, 2021, 02:52:35 PM

I was meaning to edit them

Yes you can edit them, but it's not required. The only thing that it is required to change for your altcoin to not be considered bitcoin is the pchMessageStart values. These define if you're following bitcoin's chain or not.

Hello again blackhat! I am back, sorry for this month outside

I am continuing the project and after fixing all the images of the coin with the right ones, I am stucked and also I have some questions:

1- right now in Ubuntu LTS comand (into windows) and my XXXXcoin folder is inside, wich I assume when i log as root on the terminal of ubuntu, it is already opened that folder, (like when we do cd .. C:\Users\ASUS\AppData\Local\Packages\CanonicalGroupLimited.Ubuntu18.04onWindows_79rhkp1fndgsc\LocalState\rootfs\home\mironkraft\XxxxCoin) if it is ok, or i have to enter some code to reach that to resumen where i was, tell me please

2- on your tutorial, you say at:

Quote

Most notepads change permissions when we mess with LTS. That's why you must run the following lines:

Code:

cd src
sudo chmod 640 validation.cpp
sudo chmod 640 chainparams.cpp
sudo chmod 640 chainparamsbase.cpp
cd consensus
sudo chmod 640 consensus.h
cd ..
cd ..

This is mandatory? as far as I understand if I dont have problems with Sublime Text and the files it is not needed right?

3- before building, how I am suposed to change the genesis block exactly? I already know that I have to go to:
https://github.com/liveblockchain/genesisgen

but how I modify every line? where is the archive? where I am suposed to comply inside of the XxxxCoin folder?

this is how i have it right now:

I know that i have to open the archive and edit some lines, the mithycal phrase as other options
(old tutorial where it says: https://medium.com/@jordan.baczuk/how-to-fork-bitcoin-part-2-59b9eddb49a4)

Do you mind to help me to achieve it correctly?

Other later questions in mind:

1- once finished the genesis block configuration, how i am supossed to build this rightly? wich are the "codes" to enter on terminal for it?

Quote

When it is finished, we build with the following commands:

Code:

PATH=$(echo "$PATH" | sed -e 's/:\/mnt.*//g')
sudo bash -c "echo 0 > /proc/sys/fs/binfmt_misc/status"
cd depends
make HOST=x86_64-w64-mingw32
cd ..
./autogen.sh
CONFIG_SITE=$PWD/depends/x86_64-w64-mingw32/share/config.site ./configure --prefix=/
make

(It may take more than an hour)

The files to open the new Altcoin Core are in altcoin/src/qt:

2- how to mining the first block? wich steps I should follow?

3- how to save the genesis block of the chain in the computer? I mean, for later use if the chain is being mined from diferent clients and I wan to update it?

4- how I am supossed to update it in the future? should I upload it to github once is start mining? how?

sorry again for my bad english

Thanks for your time and patience till now, hope you dont let me down!

BlackHatCoiner

legendary

Activity: 1512

Merit: 7340

Farewell, Leo

Hi, sorry for forgetting to reply.

Quote from: mironkraft on December 29, 2021, 02:52:35 PM

I was meaning that If I change the letters so was "styling" or making it diferent from bitcoin ones, nevermind it, ill keep them from bitcoin, i guess it doesnt matter

Keep them the same yeah. The only downside is that the users of your altcoin can't distinguish the addresses of bitcoin and yours. Again, leave that for later, build your altcoin first.

Quote from: mironkraft on December 29, 2021, 02:52:35 PM

Could youplease tell me how I am supposed to test the coin if I did not managed to finish it? I mean, before building it i guess

You can't test the coin without building the binaries.

Quote from: mironkraft on December 29, 2021, 02:52:35 PM

I was meaning to edit them

Yes you can edit them, but it's not required. The only thing that it is required to change for your altcoin to not be considered bitcoin is the pchMessageStart values. These define if you're following bitcoin's chain or not.

mironkraft

jr. member

Activity: 78

Merit: 4

Bump!

How I am suposed to test the coin before launch it?

Thanks!

mironkraft

jr. member

Activity: 78

Merit: 4

Quote from: BlackHatCoiner on December 29, 2021, 02:04:26 PM

Quote from: mironkraft on December 29, 2021, 10:49:02 AM

1- so I can maintain them as the bitcoin original right? wanted to change to make it "unique"

I'm sorry but I fail to understand what you're trying to mean here and because words matter in this subject, I'll have to ask you to repeat it in another way.

I was meaning that If I change the letters so was "styling" or making it diferent from bitcoin ones, nevermind it, ill keep them from bitcoin, i guess it doesnt matter

Quote from: mironkraft on December 29, 2021, 10:49:02 AM

2- sorry didnt understand fine your answer, never tested if the coin works

You have to make it work first and then check for these secondary changes.[/quote]

Could youplease tell me how I am supposed to test the coin if I did not managed to finish it? I mean, before building it i guess

Quote from: mironkraft on December 29, 2021, 01:28:47 PM

1- Do we work on RPC and P2P ports on chainparams?

What do you mean “we work”? Whenever you want to establish a connection you'll use those ports, yeah.[/quote]

I was meaning to edit them jejeje (what a failing english related to crypto...sorry for it)

BlackHatCoiner

legendary

Activity: 1512

Merit: 7340

Farewell, Leo

Quote from: mironkraft on December 29, 2021, 10:49:02 AM

1- so I can maintain them as the bitcoin original right? wanted to change to make it "unique"

I'm sorry but I fail to understand what you're trying to mean here and because words matter in this subject, I'll have to ask you to repeat it in another way.

Quote from: mironkraft on December 29, 2021, 10:49:02 AM

2- sorry didnt understand fine your answer, never tested if the coin works

You have to make it work first and then check for these secondary changes.

Quote from: mironkraft on December 29, 2021, 11:45:28 AM

I guess you mean to change every nMinimumChainWork to ("0x0000000000000000000000000000000000000000000000000000000100010001") on all the lines that we can found on the chainparams right?

Yes. At least if testnet or signet matter in your altcoin.

Quote from: mironkraft on December 29, 2021, 11:45:28 AM

Also, in the next step, when you say to delete vSeeds.emplace_back, you mean to delete complete lines from the chainparams?

Yes.

Quote from: mironkraft on December 29, 2021, 01:28:47 PM

1- Do we work on RPC and P2P ports on chainparams?

What do you mean “we work”? Whenever you want to establish a connection you'll use those ports, yeah.

Quote from: mironkraft on December 29, 2021, 01:28:47 PM

2- What about the seeds? Do they need to be chainged?

The seeds need to be removed. There's no point of having a seed from another block chain.

Quote from: mironkraft on December 29, 2021, 01:28:47 PM

3- In coin distribution (max supply, block rewards, halving interval, block time, sieze, BIPs) are needed to be changed?

It's your decision. Leave them the same as bitcoin's if you don't care.

Quote from: mironkraft on December 29, 2021, 01:28:47 PM

4- if the answer of 3 is YES, does it mean that I am making my own way to have own blockchain, meaning it as HARDFORK?

It's not a hard fork if you're building it from scratch. Remember that you start another block chain from 0. A hard fork happens within a certain block of the already existent chain.

Quote from: mironkraft on December 29, 2021, 01:28:47 PM

5- Doing my own Genesis block means also HardFork?

No.

Quote from: mironkraft on December 29, 2021, 01:28:47 PM

6- If bitcoin gets updated to 0.23 and my coin is 0.22, as softfork I can update the changes with the original bitcoin? and as HardFork I coulndt update right?

I guess you will be able to. You'll have to take 0.23's source code and rewrite the same values.

Quote from: mironkraft on December 29, 2021, 01:28:47 PM

Right now, I want to do my own genesis block (I know that in your tutorial doesnt appears)

I've given you a link: https://github.com/liveblockchain/genesisgen

mironkraft

jr. member

Activity: 78

Merit: 4

Well I followed my instinct and done everything

Right now, after going for the genesis block, I would like to ask some questions about the development:

1- Do we work on RPC and P2P ports on chainparams?
2- What about the seeds? Do they need to be chainged?
3- In coin distribution (max supply, block rewards, halving interval, block time, sieze, BIPs) are needed to be changed?
4- if the answer of 3 is YES, does it mean that I am making my own way to have own blockchain, meaning it as HARDFORK?
5- Doing my own Genesis block means also HardFork?
6- If bitcoin gets updated to 0.23 and my coin is 0.22, as softfork I can update the changes with the original bitcoin? and as HardFork I coulndt update right?

Right now, I want to do my own genesis block (I know that in your tutorial doesnt appears)

So, AFAIK I found information about;

Quote

https://motion-software.com/blog/how-to-create-your-own-blockchain-network-from-bitcoin

Old tutorial found: https://medium.com/@jordan.baczuk/how-to-fork-bitcoin-part-2-59b9eddb49a4

For me, it keeps understanding that making my own Genesis Block is hardforking

Thanks for your time if you answer

mironkraft

jr. member

Activity: 78

Merit: 4

Well, I go further and ask also, on your tutorial, you say:

Quote

We have to set the difficulty equal with 1, since you will be the only miner at the beginning. At chainparams.cpp change nMinimumChainWork:

Code:
consensus.nMinimumChainWork = uint256S("0x0000000000000000000000000000000000000000000000000000000100010001");

I guess you mean to change every nMinimumChainWork to ("0x0000000000000000000000000000000000000000000000000000000100010001") on all the lines that we can found on the chainparams right?

Also, in the next step, when you say to delete vSeeds.emplace_back, you mean to delete complete lines from the chainparams?

Code:

        vSeeds.emplace_back("seed.XXXXcoin.sipa.be."); // Pieter Wuille, only supports x1, x5, x9, and xd
        vSeeds.emplace_back("dnsseed.bluematt.me."); // Matt Corallo, only supports x9
        vSeeds.emplace_back("dnsseed.XXXXcoin.dashjr.org."); // Luke Dashjr
        vSeeds.emplace_back("seed.XXXXcoinstats.com."); // Christian Decker, supports x1 - xf
        vSeeds.emplace_back("seed.XXXXcoin.jonasschnelli.ch."); // Jonas Schnelli, only supports x1, x5, x9, and xd
        vSeeds.emplace_back("seed.btc.petertodd.org."); // Peter Todd, only supports x1, x5, x9, and xd
        vSeeds.emplace_back("seed.XXXXcoin.sprovoost.nl."); // Sjors Provoost
        vSeeds.emplace_back("dnsseed.emzy.de."); // Stephan Oeste
        vSeeds.emplace_back("seed.XXXXcoin.wiz.biz."); // Jason Maurice

Thanks for your time!

mironkraft

jr. member

Activity: 78

Merit: 4

Quote from: BlackHatCoiner on December 29, 2021, 10:07:36 AM

Quote from: mironkraft on December 29, 2021, 06:56:16 AM

About the bech32_hrp code, shouldn´t be changed when you change the adresses?

Why do you want so bad to change the prefixes? Have you tested to see if your altcoin is working? The prefix/styling is secondary.

Quote from: mironkraft on December 29, 2021, 06:56:16 AM

Also, in line 244, if I have to change that bech32 code, I have done it right? or should be another letters?

It seems fine. I don't cross my arms that you just change that variable and the “bc” prefix becomes invalid.

1- so I can maintain them as the bitcoin original right? wanted to change to make it "unique"

I guess the best is to leave it like it was

2- sorry didnt understand fine your answer, never tested if the coin works

BlackHatCoiner

legendary

Activity: 1512

Merit: 7340

Farewell, Leo

Quote from: mironkraft on December 29, 2021, 06:56:16 AM

About the bech32_hrp code, shouldn´t be changed when you change the adresses?

Why do you want so bad to change the prefixes? Have you tested to see if your altcoin is working? The prefix/styling is secondary.

Quote from: mironkraft on December 29, 2021, 06:56:16 AM

Also, in line 244, if I have to change that bech32 code, I have done it right? or should be another letters?

It seems fine. I don't cross my arms that you just change that variable and the “bc” prefix becomes invalid.

mironkraft

jr. member

Activity: 78

Merit: 4

Quote from: BlackHatCoiner on December 29, 2021, 06:25:01 AM

The SCRIPT_ADDRESS stands for the P2SH addresses, those that start with 3. If you notice it, it has “5” in the decimal version:

Code:

base58Prefixes[SCRIPT_ADDRESS] = std::vector(1,5);

And by going to the page I've linked it you can see the decimal prefixes and their leading symbols:

Change it to whatever you want. Same goes for SECRET_KEY & PUBKEY_ADDRESS.

oH! GREAT! understood!

I will leave it like this (question down also):

Line 140:

Code:

        base58Prefixes[PUBKEY_ADDRESS] = std::vector(1,45);
        base58Prefixes[SCRIPT_ADDRESS] = std::vector(1,48);
        base58Prefixes[SECRET_KEY] =     std::vector(1,128);
        base58Prefixes[EXT_PUBLIC_KEY] = {0x04, 0x88, 0xB2, 0x1E};
        base58Prefixes[EXT_SECRET_KEY] = {0x04, 0x88, 0xAD, 0xE4};

        bech32_hrp = "ac";

Line 244

Code:

        base58Prefixes[PUBKEY_ADDRESS] = std::vector(1,107);
        base58Prefixes[SCRIPT_ADDRESS] = std::vector(1,65);
        base58Prefixes[SECRET_KEY] =     std::vector(1,239);
        base58Prefixes[EXT_PUBLIC_KEY] = {0x04, 0x35, 0x87, 0xCF};
        base58Prefixes[EXT_SECRET_KEY] = {0x04, 0x35, 0x83, 0x94};

        bech32_hrp = "tb";

Line 369

Code:

        base58Prefixes[PUBKEY_ADDRESS] = std::vector(1,107);
        base58Prefixes[SCRIPT_ADDRESS] = std::vector(1,65);
        base58Prefixes[SECRET_KEY] =     std::vector(1,239);
        base58Prefixes[EXT_PUBLIC_KEY] = {0x04, 0x35, 0x87, 0xCF};
        base58Prefixes[EXT_SECRET_KEY] = {0x04, 0x35, 0x83, 0x94};

        bech32_hrp = "ta";

Line 466

Code:

        base58Prefixes[PUBKEY_ADDRESS] = std::vector(1,107);
        base58Prefixes[SCRIPT_ADDRESS] = std::vector(1,65);
        base58Prefixes[SECRET_KEY] =     std::vector(1,239);
        base58Prefixes[EXT_PUBLIC_KEY] = {0x04, 0x35, 0x87, 0xCF};
        base58Prefixes[EXT_SECRET_KEY] = {0x04, 0x35, 0x83, 0x94};

        bech32_hrp = "acrt";

About the bech32_hrp code, shouldn´t be changed when you change the adresses?
Also, in line 244, if I have to change that bech32 code, I have done it right? or should be another letters?

BlackHatCoiner

legendary

Activity: 1512

Merit: 7340

Farewell, Leo

The SCRIPT_ADDRESS stands for the P2SH addresses, those that start with 3. If you notice it, it has “5” in the decimal version:

Code:

base58Prefixes[SCRIPT_ADDRESS] = std::vector(1,5);

And by going to the page I've linked it you can see the decimal prefixes and their leading symbols:

Change it to whatever you want. Same goes for SECRET_KEY & PUBKEY_ADDRESS.

mironkraft

jr. member

Activity: 78

Merit: 4

Quote from: BlackHatCoiner on December 29, 2021, 05:50:10 AM

Quote from: mironkraft on December 29, 2021, 05:39:37 AM

and what happens with the scrip_adress? shouldnt be changed? or its only pubkey?

Yes, you can change the SCRIPT_ADDRESS too in the same way.

but what is the meaning of chainging it? I mean, if pubkey is something that people sees, for what is the script adress, what it is?

also, I only need to change the pubkey, not the script right?

BlackHatCoiner

legendary

Activity: 1512

Merit: 7340

Farewell, Leo

Quote from: mironkraft on December 29, 2021, 05:39:37 AM

and what happens with the scrip_adress? shouldnt be changed? or its only pubkey?

Yes, you can change the SCRIPT_ADDRESS too in the same way.

mironkraft

jr. member

Activity: 78

Merit: 4

Quote from: BlackHatCoiner on December 29, 2021, 05:08:20 AM

Quote from: mironkraft on December 29, 2021, 05:04:50 AM

Code:

base58Prefixes[PUBKEY_ADDRESS] = std::vector(120,75);

It should be like this:

Code:

base58Prefixes[PUBKEY_ADDRESS] = std::vector(1,75);

Don't change the “1”, just the number next to it.

and what happens with the scrip_adress? shouldnt be changed? or its only pubkey?
I remember time ago that it needed to be changed

BlackHatCoiner

legendary

Activity: 1512

Merit: 7340

Farewell, Leo

Quote from: mironkraft on December 29, 2021, 05:04:50 AM

Code:

base58Prefixes[PUBKEY_ADDRESS] = std::vector(120,75);

It should be like this:

Code:

base58Prefixes[PUBKEY_ADDRESS] = std::vector(1,75);

Don't change the “1”, just the number next to it.

mironkraft

jr. member

Activity: 78

Merit: 4

Quote from: BlackHatCoiner on December 29, 2021, 04:16:41 AM

Quote from: mironkraft on December 26, 2021, 10:35:22 PM

*It is really fine? as my point of view those 3 parts should have diferent prefixes, or i am wrong?

It seems fine to me. You've only changed the signature message and the port number, right?

Quote from: mironkraft on December 26, 2021, 10:35:22 PM

I stuck since I really don´t understand 100% this configuration and what should i do

In my tutorial, I've added this as an example:

Code:

base58Prefixes[PUBKEY_ADDRESS] = std::vector(1,75);

The “75” defines that the addresses will start with the letter “X”. You do the exact thing for any prefix. Choose the leading symbol and replace the number with its decimal version.

- 1 - Yes, signature and port number

- 2 - Ok, I understand that this makes the adress for each "user" / "direction"

How about if I leave it like that?

If not, I will choose 120 q 34

It should be like this right?:

ORIGINAL:

Code:


        base58Prefixes[PUBKEY_ADDRESS] = std::vector(1,0);
        base58Prefixes[SCRIPT_ADDRESS] = std::vector(1,5);
        base58Prefixes[SECRET_KEY] =     std::vector(1,128);
        base58Prefixes[EXT_PUBLIC_KEY] = {0x04, 0x88, 0xB2, 0x1E};
        base58Prefixes[EXT_SECRET_KEY] = {0x04, 0x88, 0xAD, 0xE4};

        base58Prefixes[PUBKEY_ADDRESS] = std::vector(1,111);
        base58Prefixes[SCRIPT_ADDRESS] = std::vector(1,196);
        base58Prefixes[SECRET_KEY] =     std::vector(1,239);
        base58Prefixes[EXT_PUBLIC_KEY] = {0x04, 0x35, 0x87, 0xCF};
        base58Prefixes[EXT_SECRET_KEY] = {0x04, 0x35, 0x83, 0x94};

CHANGED:

Code:


        base58Prefixes[PUBKEY_ADDRESS] = std::vector(120,75);
        base58Prefixes[SCRIPT_ADDRESS] = std::vector(1,5);
        base58Prefixes[SECRET_KEY] =     std::vector(1,128);
        base58Prefixes[EXT_PUBLIC_KEY] = {0x04, 0x88, 0xB2, 0x1E};
        base58Prefixes[EXT_SECRET_KEY] = {0x04, 0x88, 0xAD, 0xE4};

        base58Prefixes[PUBKEY_ADDRESS] = std::vector(120,75);
        base58Prefixes[SCRIPT_ADDRESS] = std::vector(1,196);
        base58Prefixes[SECRET_KEY] =     std::vector(1,239);
        base58Prefixes[EXT_PUBLIC_KEY] = {0x04, 0x35, 0x87, 0xCF};
        base58Prefixes[EXT_SECRET_KEY] = {0x04, 0x35, 0x83, 0x94};

Sorry if I dont understand clrearly, some technical english is kinda hard for me

Thanks in advance!

BlackHatCoiner

legendary

Activity: 1512

Merit: 7340

Farewell, Leo

Quote from: mironkraft on December 26, 2021, 10:35:22 PM

*It is really fine? as my point of view those 3 parts should have diferent prefixes, or i am wrong?

It seems fine to me. You've only changed the signature message and the port number, right?

Quote from: mironkraft on December 26, 2021, 10:35:22 PM

I stuck since I really don´t understand 100% this configuration and what should i do

In my tutorial, I've added this as an example:

Code:

base58Prefixes[PUBKEY_ADDRESS] = std::vector(1,75);

The “75” defines that the addresses will start with the letter “X”. You do the exact thing for any prefix. Choose the leading symbol and replace the number with its decimal version.

mironkraft

jr. member

Activity: 78

Merit: 4

Quote from: BlackHatCoiner on December 25, 2021, 07:56:09 AM

Quote from: mironkraft on December 24, 2021, 05:57:06 PM

Building genesis in linux right? excuse me for asking maybe stupid things, between language and that I am a bit rusted..

You can either build it in linux or windows. May I assume you're a Windows user? Just install gcc and run gcc genesis.c -o genesis.exe

Quote from: mironkraft on December 24, 2021, 05:57:06 PM

I might start all over with your tutorial, since i worked on bitcoin 2.1 and now is 22.00

You mean 0.21, right?

Hi black hat!

Hope you dont mind I quote you, could you help me to check whats wrong in my move in the last post?

thanks a lot, and hope doesnt disturbs you

thnx

mironkraft

jr. member

Activity: 78

Merit: 4

First stuck

Hello there!

Well, I just started and im stucked at this point of your tutorial;

Quote

Now we will choose a different signature message in pchMessageStart of chainparams.cpp. This is a very important step, if it is not changed and you connect to a bitcoin node it will consider the bitcoin blockchain as the correct one. Do it like this:
Code:
pchMessageStart[0] = 0xf0;
pchMessageStart[1] = 0xb0;
pchMessageStart[2] = 0xb0;
pchMessageStart[3] = 0xd0;

Optional, but you can change the address prefix too. (1, 3, bc1)
Link of all prefixes: https://en.bitcoin.it/wiki/List_of_address_prefixes
In the base58Prefixes of chainparams.cpp I will show an example of the "X" prefix:
Code:
base58Prefixes[PUBKEY_ADDRESS] = std::vector(1,75);

First part, I have succesfully* done changing the 3 part where the pch message on the chainparams neded:

Code:

		pchMessageStart[0] = 0xf0;
		pchMessageStart[1] = 0xb0;
		pchMessageStart[2] = 0xb0;
		pchMessageStart[3] = 0xd0;
        nDefaultPort = 17333;
        nPruneAfterHeight = 1000;
        m_assumed_blockchain_size = 40;
        m_assumed_chain_state_size = 2;

Code:

		pchMessageStart[0] = 0xf0;
		pchMessageStart[1] = 0xb0;
		pchMessageStart[2] = 0xb0;
		pchMessageStart[3] = 0xd0;
        nDefaultPort = 17444;
        nPruneAfterHeight = args.GetBoolArg("-fastprune", false) ? 100 : 1000;
        m_assumed_blockchain_size = 0;
        m_assumed_chain_state_size = 0;

Code:

		pchMessageStart[0] = 0xf0;
		pchMessageStart[1] = 0xb0;
		pchMessageStart[2] = 0xb0;
		pchMessageStart[3] = 0xd0;
        nDefaultPort = 17444;
        nPruneAfterHeight = args.GetBoolArg("-fastprune", false) ? 100 : 1000;
        m_assumed_blockchain_size = 0;
        m_assumed_chain_state_size = 0;

*It is really fine? as my point of view those 3 parts should have diferent prefixes, or i am wrong?

But, when I want to go to the step: base58Prefixes

I stuck since I really don´t understand 100% this configuration and what should i do
(for me is important to know for what is this and how should I do fine)

Las time ive done it i followed this from another source:

Quote

Change address prefixes
Finally, let’s dive into the source code. Currently there are 3 standard address types in Bitcoin:
Pay to Pubkey Hash
Mainnet prefix “1”
Testnet/Regtest prefix “m or n”
Pay to Script Hash
Mainnet prefix “3”
Testnet/Regtest prefix “2”
Bech32 (Segwit)
Mainnet prefix “bc1”
Testnet prefix “tb1”
Regtest prefix “bcrt1”
Since these addresses are base58check encoded (except for bech32 which is it’s own custom encoding), we can set any prefix we want by using this helpful table of values found at https://en.bitcoin.it/wiki/List_of_address_prefixes. The source file containing these prefix settings is src/chainparams.cpp:

Code:

// Mainnet: Line 140
// ...
base58Prefixes[PUBKEY_ADDRESS] = std::vector(1,0);
base58Prefixes[SCRIPT_ADDRESS] = std::vector(1,5);
base58Prefixes[SECRET_KEY] =     std::vector(1,128);
base58Prefixes[EXT_PUBLIC_KEY] = {0x04, 0x88, 0xB2, 0x1E};
base58Prefixes[EXT_SECRET_KEY] = {0x04, 0x88, 0xAD, 0xE4};
bech32_hrp = "bc";
// ...
// Testnet: Line 244
base58Prefixes[PUBKEY_ADDRESS] = std::vector(1,111);
base58Prefixes[SCRIPT_ADDRESS] = std::vector(1,196);
base58Prefixes[SECRET_KEY] =     std::vector(1,239);
base58Prefixes[EXT_PUBLIC_KEY] = {0x04, 0x35, 0x87, 0xCF};
base58Prefixes[EXT_SECRET_KEY] = {0x04, 0x35, 0x83, 0x94};
bech32_hrp = "tb";
// ...
// Regtest: Line 344
base58Prefixes[PUBKEY_ADDRESS] = std::vector(1,111);
base58Prefixes[SCRIPT_ADDRESS] = std::vector(1,196);
base58Prefixes[SECRET_KEY] =     std::vector(1,239);
base58Prefixes[EXT_PUBLIC_KEY] = {0x04, 0x35, 0x87, 0xCF};
base58Prefixes[EXT_SECRET_KEY] = {0x04, 0x35, 0x83, 0x94};
bech32_hrp = "bcrt";
...

We want our p2pkh addresses to start with the letter “K” on mainnet and “k” on testnet and regtest. Then we want p2psh addresses to start with “L” on mainnet and “t” on testnet and regtest. We’ll keep secret keys the same, but we’ll change the bech32 addresses to “lc”, “tl”, and “lcrt” for mainnet, testnet, and regtest respectively. Based on the values in the table linked above, our chainparams.cpp becomes:

Code:

// Mainnet: Line 140
// ...
base58Prefixes[PUBKEY_ADDRESS] = std::vector(1,45); // K
base58Prefixes[SCRIPT_ADDRESS] = std::vector(1,48); // L
// ...
bech32_hrp = "lc";
// ...
// Testnet: Line 244
base58Prefixes[PUBKEY_ADDRESS] = std::vector(1,107); // k
base58Prefixes[SCRIPT_ADDRESS] = std::vector(1,65);  // t
// ...
bech32_hrp = "tl";
// ...
// Regtest: Line 344
base58Prefixes[PUBKEY_ADDRESS] = std::vector(1,107); // k
base58Prefixes[SCRIPT_ADDRESS] = std::vector(1,65);  // t
// ...
bech32_hrp = "lcrt";
...

mironkraft

jr. member

Activity: 78

Merit: 4

Quote from: BlackHatCoiner on December 25, 2021, 07:56:09 AM

Quote from: mironkraft on December 24, 2021, 05:57:06 PM

Building genesis in linux right? excuse me for asking maybe stupid things, between language and that I am a bit rusted..

You can either build it in linux or windows. May I assume you're a Windows user? Just install gcc and run gcc genesis.c -o genesis.exe

Quote from: mironkraft on December 24, 2021, 05:57:06 PM

I might start all over with your tutorial, since i worked on bitcoin 2.1 and now is 22.00

You mean 0.21, right?

I usually use Windows (have windows virtualization for ubuntu) and i have workd even on backtrack distro old days

Yes, well I mean 21.0 after 22.0 update

BlackHatCoiner

legendary

Activity: 1512

Merit: 7340

Farewell, Leo

Quote from: mironkraft on December 24, 2021, 05:57:06 PM

Building genesis in linux right? excuse me for asking maybe stupid things, between language and that I am a bit rusted..

You can either build it in linux or windows. May I assume you're a Windows user? Just install gcc and run gcc genesis.c -o genesis.exe

Quote from: mironkraft on December 24, 2021, 05:57:06 PM

I might start all over with your tutorial, since i worked on bitcoin 2.1 and now is 22.00

You mean 0.21, right?

mironkraft

jr. member

Activity: 78

Merit: 4

Quote from: BlackHatCoiner on December 24, 2021, 02:37:05 PM

Alright, so here's what you're going to do. Go on genesisgen on github, download genesis.c and build it. Once you have the executable, run name.exe .

In you should add your public key in uncompressed format. In your message. In the target. Leave it on 486604799 (1d00ffff) which is the lowest you can have with a difficulty of 1.

Once you mine the genesis block, the program will return you the coinbase script, the scriptPubKey, the merkle hash, the byteswapped merkle hash, the unix time, the nonce and finally the genesis block's hash.

1. Change the genesisOutputScript to your scriptPubKey from #L54.
2. Change genesis.hashMerkleRoot to the byteswapped merkle hash in #L114.
3. Change consensus.hashGenesisBlock to your block's hash in #L113.
4. Change the first two values from the CreateGenesisBlock function to the unix time and nonce respectively in #L111.
5. Build Bitcoin Core.

I've made a tutorial here: How to create your own altcoin (v0.20.1). It should be the same for the latest version of Bitcoin Core.

Hi! Thanks for your time in advace

Building genesis in linux right? excuse me for asking maybe stupid things, between language and that I am a bit rusted..

I might start all over with your tutorial, since i worked on bitcoin 2.1 and now is 22.00

Ill keep informed in this post hows going

Thanks again!

BlackHatCoiner

legendary

Activity: 1512

Merit: 7340

Farewell, Leo

Alright, so here's what you're going to do. Go on genesisgen on github, download genesis.c and build it. Once you have the executable, run name.exe .

In you should add your public key in uncompressed format. In your message. In the target. Leave it on 486604799 (1d00ffff) which is the lowest you can have with a difficulty of 1.

Once you mine the genesis block, the program will return you the coinbase script, the scriptPubKey, the merkle hash, the byteswapped merkle hash, the unix time, the nonce and finally the genesis block's hash.

1. Change the genesisOutputScript to your scriptPubKey from #L54.
2. Change genesis.hashMerkleRoot to the byteswapped merkle hash in #L114.
3. Change consensus.hashGenesisBlock to your block's hash in #L113.
4. Change the first two values from the CreateGenesisBlock function to the unix time and nonce respectively in #L111.
5. Build Bitcoin Core.

I've made a tutorial here: How to create your own altcoin (v0.20.1). It should be the same for the latest version of Bitcoin Core.

mironkraft

jr. member

Activity: 78

Merit: 4

Hello there, I am back to the forum and I would like to achieve creating a coin, maybe based on bitcoin (now ver 22.0) or any other plataform

In the past I tried to make it based on 21.0 and stucked on the creation of the genesis block
(some of the posts where I asked help)
https://bitcointalk.org/index.php?topic=5319944.20
https://bitcointalksearch.org/topic/m.56435394

anyways this are not important

Anyone could help me to achieve creating a coin by myself? Or does anywhere were i can found a updated tutorial for it?
(I used linux to reach genesis block)

Thanks a lot, have a nice day!

Topic: back to creating new alt coin (Read 477 times)