|
5
|
Alternate cryptocurrencies / Announcements (Altcoins) / Re: [ANN][BLAZR] BlazerCoin 🌿POW with DGW3🌿 Blazing the way for Future Generations
|
on: May 28, 2023, 05:02:01 AM
|
|
Won't compile on Ubuntu 22 nor 20 (SSL Bignum issues) and, won't even compile one Ubuntu 16 ...
AI assisted clues, if anyone want to fix:
Summary of the issues and possible solution paths for the developer to explore:
rpcrawtransaction.cpp: This file contains the code where the ExtractDestinations function is called, and the handling of the extracted information is performed.
script.h and script.cpp: These files contain the implementation of the ExtractDestination and ExtractDestinations functions.
Compilation Error: The error message indicates an issue with the Boost variant library and the usage of boost::get and boost::strict_get functions.
Possible Solution:
Verify that the Boost library is installed correctly and accessible by the compiler.
Include the necessary Boost headers, specifically the Boost variant-related headers such as boost/variant.hpp.
Double-check the compatibility of the Boost library version with your code.
Ensure that the Boost variant types and related functions are used correctly and that the necessary types are defined and included.
Incomplete Type Error: The error message mentions an invalid application of sizeof to an incomplete type.
Possible Solution:
Review the Boost variant-related code and ensure that all necessary types and definitions are correctly included and accessible.
Check for any missing or incorrect type definitions related to Boost variant usage.
Verify that the Boost headers are included in the correct order before the relevant code snippets.
Extraction and Handling of Destinations: The code snippets involve the extraction and handling of destination addresses from scriptPubKeys.
Possible Solution:
Review the implementation of the ExtractDestinations function and ensure it correctly extracts the necessary information.
Verify that the ExtractDestinations function returns the expected values for type, addresses, and nRequired.
Check the implementation of the GetTxnOutputType function to ensure it returns the proper output type based on the input txnouttype.
Ensure that the objects (out, addresses, etc.) used to store the extracted information are properly defined and capable of storing the required key-value pairs.
By exploring these solution paths, reviewing the code implementations, and addressing any identified issues, the developer should be able to resolve the compilation error and ensure correct handling of destination addresses in the code.
|
|
|
|
|
8
|
Alternate cryptocurrencies / Announcements (Altcoins) / Re: FireFlyCoin Launched! - REBOOT
|
on: July 20, 2022, 12:24:25 PM
|
Hello!
I want to update the FFC blockchain.
but I don't have any working nodes!
Can you give us somes nodes?
Thank's!
addnode=91.206.16.214 On *NIX machine, use the dig command to query the DNS Seeder. 'dnsseed.fireflycoin.cc' dig dnsseed.fireflycoin.cc ; <<>> DiG 9.10.6 <<>> dnsseed.fireflycoin.cc
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 50711
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1232
;; QUESTION SECTION:
;dnsseed.fireflycoin.cc. IN A
;; ANSWER SECTION:
dnsseed.fireflycoin.cc. 3600 IN A 91.206.16.214
;; Query time: 991 msec
;; SERVER: 103.86.96.100#53(103.86.96.100)
;; WHEN: Wed Jul 20 05:20:30 PDT 2022
;; MSG SIZE rcvd: 67 |
|
|
|
|
12
|
Alternate cryptocurrencies / Altcoin Discussion / Re: [BTE] The Bytecoin Information Thread
|
on: February 11, 2022, 02:03:32 PM
|
86.131.40.79 looks good and connects as a peer.
188.213.34.67 also appears to connect as a peer.
I cannot connect to 172.31.47.236 or 164.68.101.222.
It still can't find good nodes ... I wonder if the chain parameters I'm using are correct. There seem to be two bytecoins out there at least; where is the latest code for this blockchain? 188.213.34.67 no longer connects. "Two bytecoins". Two possibilities here. 1) Pre-mined shitcoin calling itself "bytecoin". Usually differentiated as "BCN" versus "BTE", the real Bytecoin. 2) Ahmed Bodi tried to fork BTE. I've never seen any evidence that he succeeded. What "latest code" are you looking for? Looking for the source code to BTE the "real" Bytecoin. In other words, the reference implementation, or any "correct" implementation. |
|
|
|
|
13
|
Alternate cryptocurrencies / Altcoin Discussion / Re: [BTE] The Bytecoin Information Thread
|
on: February 09, 2022, 12:35:23 AM
|
86.131.40.79 looks good and connects as a peer.
188.213.34.67 also appears to connect as a peer.
I cannot connect to 172.31.47.236 or 164.68.101.222.
It still can't find good nodes ... I wonder if the chain parameters I'm using are correct. There seem to be two bytecoins out there at least; where is the latest code for this blockchain? |
|
|
|
|
14
|
Alternate cryptocurrencies / Altcoin Discussion / Re: [BTE] The Bytecoin Information Thread
|
on: February 06, 2022, 11:05:52 AM
|
dbkeys@home ~ % dig bte.chainetics.com
;; ANSWER SECTION:
bte.chainetics.com. 3420 IN A 86.160.129.103 IP is not valid for a node. Do you have a list of good, valid nodes I can prime the tracker/seeder with ? These are the IP's the tracker/seeder is primed with right now ( I removed the IP you said is invalid ): // At least one valid seed ip address is required to begin crawling the network
seed_1="164.68.101.222" // https://bitcointalk.org/index.php?topic=169559.680
seed_2="172.31.47.236"
seed_3="86.131.40.79"
Once it latches on to the P2P network, the Node Tracker / DNS Seeder will maintain a real-time list of good nodes which accept connections. These are the blockchain parameters programmed into the node tracker:
// BlockChain parameters and Protocol version numbers
//--------------------------------------------------------------------------------------------------------------------------------------/
blockchain_name="Bytecoin" //
ticker="BTE"
protocol_version="70001" // --- Typically, these are found ( protocol version,init_proto_version, etc) in the coin's version.h file
init_proto_version="209" //
min_peer_proto_version="209" // Leave blank or set to the same value as protocol_version if not applicable in your blockchain
caddr_time_version="31402" //
pchMessageStart_0 = "0x0b" // --- Typically you can find the 4 pchMessageStart values in your coin's main.cpp or chainparams.cpp file
pchMessageStart_1 = "0x22" // ByteCoin: main.cpp pchMessageStart[0]..[3]
pchMessageStart_2 = "0x03" //
pchMessageStart_3 = "0x14" //
wallet_port="6333" // P2P port: The coin servers's main port
block_count="64754" // A node cannot be considered "good" unless it has a block height greater or equal to this value.
host="bte.chainetics.com" // -h parameter : subdomain to query
|
|
|
|
|
15
|
Alternate cryptocurrencies / Altcoin Discussion / Re: [BTE] The Bytecoin Information Thread
|
on: February 05, 2022, 04:00:46 PM
|
It does not say anywhere who created this coin and why. Also how much preminning happened with this coin?
Check here https://bitcointalk.org/index.php?topic=164569.0Bytecoin was launched with no pre-mining, but almost immediately a guy who goes by Ahmed Bodi from BC, Canada (I think) pointed a big ASIC at the coin. He and his gang scarfed over 100,000 BTE during the first year from startup. He would mine until the difficulty went up, wait till it dropped at the next recalc, mine again and so on. He did this at least half a dozen times, but then seemed to lose interest. We have had several posters on this thread recently that I suspect are Bodi or one of his associates posing as newbies under different handles. Difficulty is now down to 264k, so now is a good time to start mining. This coin evidently needs a hardfork to a more responsive diffalgo (like Dark Gravity Wave, etc.) Tried to compile a node, but the code is quite obsolete ... lots of errors related to new SSL library / BIGNUM. I did set up a node tracker / DNS seeder for fun, with the few IP's I found on the thread; but so far it has not found any novel nodes, it just gives back the hard coded IP from this thread: dbkeys@home ~ % dig bte.chainetics.com
;; ANSWER SECTION:
bte.chainetics.com. 3420 IN A 86.160.129.103 |
|
|
|
|
16
|
Alternate cryptocurrencies / Altcoin Discussion / multiseeder : Multiple BlockChain DNS Seeder / Node Tracker
|
on: January 11, 2022, 04:41:37 PM
|
Multiple Block Chain DNS Seeder / Node Tracker multiseeder In order to support several Altcoins on a single machine / VPS, we have built upon joe@exor's excellent work with generic-seeder to create multiseeder. Thanks also to sipa, creator of the original bitcoin seeder. multiseeder examines the DNS query packet to select which set of IP nodes, from the several coin networks it tracks, it will give back to the asking client. multiseeder supports the ' settings.conf' configuration files of generic-seeder in a single binary, making it possible to support up to 10 different altcoin networks with the same VPS. multiseeder uses the ncurses library to present a consistent, organized display. example ' settings.conf' files are included in the distribution for Bitmark (MARKS), Exor (EXOR) and Vertcoin (VTC) multiseeder scans /usr/local for directories of the form ' sDNS.<COIN>', and seeks to read ' settings.conf' from each of these directories. |
|
|
|
|
Show Posts
