Search content
Sort by
Showing 20 of 125 results by felco
Re: Request: If you have some free CPU power then try mining Gapcoin
Tried to compil from source and failed. Used the source on Gitlab and Github both are falling to build. Using Ubuntu 20.04 LTS.
The code seems to need a review, and you guys dev env should get updated. Also provide static linked binaries.
The code seems to need a review, and you guys dev env should get updated. Also provide static linked binaries.
Every Time I open my Qt wallet it shows( 0 ZERO) balance... And Synchronises from beginning...(v- 15.1)
But my previous wallet only synchronised from the last Updated blocks.. And showed last synchronised/updated balance...(14.1)
Can anybody help...?? ?
That is weird. Have you tried(Possibly yes, still) to delete all contents of your Datadir, on Windows it is on C:\Users\AppData\Roaming[Or Local]\Bitcore - On *nix it is on ~/.bitcore. Try to wipe it clean, of course save your wallet.dat, and then sync it from scratch one more time.
I have fired up the 15.1 and have 0 issues here.
Can I run the legacy wallet and the new format wallet on the same computer side by side?
This is not confirmed by the devs, but I do it and it works so far.Can I run the legacy wallet and the new format wallet on the same computer side by side?
Yes. You need to change the P2P Port and the RPC Port for one of your wallets in the bitcore.conf file, like:---snip---
You can save the custom configure files in those Data Directories, when you launch those wallets it will read the bitcore.conf from the custom Data Directories.
no replies on my post here https://bitcointalk.org/index.php?topic=1883902.msg41668239#msg41668239
can you two please read it and tell me whether the second (last) part of that post possible?
2 wallets point/use the same datadir and wallet.dat? I will only run one at a time
Yeah, I think that will work *but*, I don't think that is good idea if you want just to use two wallets with the same wallet.dat, then make two copies of it and ran each bitcore-qt with it own datadir and wallet.dat(even that is the same privkey[wallet]).
Can I run the legacy wallet and the new format wallet on the same computer side by side?
Yes. You need to change the P2P Port and the RPC Port for one of your wallets in the bitcore.conf file, like:
Code:
#bitcore.conf 1
port=8555
rpcport=18555
#bitcore.conf 2
port=8556
rpcport=19555
port=8555
rpcport=18555
#bitcore.conf 2
port=8556
rpcport=19555
Also, while starting those wallets you want to specify what the Data Directory for those wallet has to be, like:
Code:
#Wallet one:
$ bitcore-qt -datadir=/home/user/.bitcoredata1
#Wallet two:
$ bitcore-qt -datadir=/home/user/.bitcoredata2
$ bitcore-qt -datadir=/home/user/.bitcoredata1
#Wallet two:
$ bitcore-qt -datadir=/home/user/.bitcoredata2
You can save the custom configure files in those Data Directories, when you launch those wallets it will read the bitcore.conf from the custom Data Directories.
felco
** HODLing !! **
Important update: Bitcore Public Keys
Dear Bitcore community,
Due to potential roadblocks with many hardware and service providers, we have come to the conclusion that it is necessary for us to change the public key prefix. Since we use the same prefix as bitcoin ("1", "3" and "bc1"), we decided that Bitcore BTX should use the following new prefixes:
Wallets 1xxx -> 2xxx
Wallets 3xxx -> sxxx
Wallets bc1 -> btx
We would like to ask all Bitcore users to slowly but surely upgrade to the new system.
To do so, please follow these steps:
1. Open your Bitcore core / Bitcore-QT wallet.
2. Create a backup of your wallet.dat and store it in a safe place. For example a USB-Stick that you later put in a safe-deposit box.
3. Download the latest wallet and replace the wallet.dat that will be created on startup with your old wallet.dat
4. Bitcore-QT will automatically create new public keys for your private keys, starting with 2xxx instead of 1xxx.
5. It is important to note, that you can only use your old public keys to send to other old addresses and vis versa - you can send only to the new format from the new format. The address formats are not interchangeable.
Please note that the private keys are in no way affected by this change. Any private key is fully compatible with both the old formatting as well as the new one.
The new wallet, supporting the new format only, is still in beta mode but can be download and tested via the official github:
https://github.com/LIMXTEC/BitCore/releases
Note: There will be an official release soon. Meanwhile here is a basic tool, to convert old addresses to the new 2xxx format: https://limxtec.github.io/btx-convert/
We also want to inform you that there's no rush to update, we set a timeframe of 3 months in which we want to complete the transition. After this period bitcore core 0.16 will be released which will only use the new public keys.
If you have any questions feel free to ask here in the forum or on our numerous social media and telegram channels. See https://bitcointalk.org/index.php?topic=1883902.msg40724430#msg40724430 for a full link list.
Thank you for your support and for your understanding.
- Your Bitcore team
Kind of confusing. I think should be made easier for users and the old and new format should remain interchangeable forever. Having to use two wallets to send to old and new addresses will be kind of a hassle and make the coin less user friendly to people that don't like confusing crypto coins.
You don't have to use 2 wallets. Just use the conversion tool to send to old addresses with the new wallet. Or vice versa. https://limxtec.github.io/btx-convert/
Helo . inn wallet bitcore qt windows. what should be saved for recovery wallet? such as the fear of someday I will reinstall windows and so on.
what should I keep and how to restore it
Set a passphrase for your Wallet, then save the wallet.dat - if you are on Windows that file is in your User home directory C:\Users\\AppData\Local\Bitcore.(I not sure, if it is in the Local dir or Roaming, but one of those)what should I keep and how to restore it
If you ever reinstall your system, to recovery your wallet just replace the wallet.dat in your new installation.
HODL!
Re: [ANN][Main] Bitcore- BTX - SEGWIT - hybrid fork 1:0.5 of Bitcoin
Hey guys why the circulating supply in CMC is not 16mln?
Market Cap
$102,680,680 USD[11,294 BTC]
Volume (24h)
$904,738 USD[99.51 BTC]
Circulating Supply
15,428,848 BTX
Total Supply
16,939,075 BTX
Market Cap
$102,680,680 USD[11,294 BTC]
Volume (24h)
$904,738 USD[99.51 BTC]
Circulating Supply
15,428,848 BTX
Total Supply
16,939,075 BTX
Re: [ANN]Bitcore- BTX - SEGWIT - hybrid fork 1:0.5 of Bitcoin- 8% Airdrop every week
Obviously the core devs which consist of Jon, Steve, and Chris. They of course modified the choice a little. If you don't know them then why are you invested?
i know the (nick)name of the devs, of course, but i wanted to know whoms choice was followed. a team always consists of more than one person.
The Airdrop model were put to voting and you aren't here by the time.
--
You guys should leave gwestcot alone. It is funny, anybody can dump, did you thought about that? He did and he is here, but I assure you, lots of dumpers aren't. Take it easy and hold on tight.
felco
Re: [ANN]Bitcore- BTX - SEGWIT - hybrid fork 1:0.5 of Bitcoin- 7% Airdrop every week
Bitcoin Cash was nothing but a brandtheft and the poor attempt to make BTC kneel.
It had to fail and so they went to Plan b and sold most of their Coins.
Still a success for them and most ppl who played it right.
It is what it is in the end.
BTX should simply go for Lightning as soon as possible.
I think thats what the Market is waiting for.
Lightning network is a new hot trend in crypto ecosystem. Recently, most of coins tend to fall in the race of integrating Lightning network to their platforms. Of course, faster transaction is good for all crypto users, but good coins need more features than that. I don't think quality of coins will be totally depended upon whether it has lightning network or not.It had to fail and so they went to Plan b and sold most of their Coins.
Still a success for them and most ppl who played it right.
It is what it is in the end.
BTX should simply go for Lightning as soon as possible.
I think thats what the Market is waiting for.
The technical aspects mean nothing without a use case, cryptocurrency can't go on forever if it just a tradable asset with no real purpose. Crypto was created as a money alternative, with the intention of it being used as a currency. There is only so far the current scenario will go before the bubble really does burst, and people realise they are just buying and selling something with no value and no purpose. It is a bit like a pyramid scheme in some respects. or a game of pass the hot potato lol. The future will only be bright for the currencies that can be used, the ones that have real value behind them.
So making the right partnerships and finding a future use for any currency should be a top priority. Features are nice and all but there is already a lot of tech and rivals in the crypto space, and that only really matters to crypto nerds. Being able to spend the coins and use them in your daily life is what really matters, or the market won't keep growing and it will never become mainstream. Like anything that does not succeed in what it was created for, it will gradually become irrelevant. That is my opinion.
Wow! This guy gets it.
I think its not fair to go that way. He has a point that is valid but is just part of the problem. More important than if we have a "use case"(We must realize that, it would have - at least one use case - for every cryptocurrencie out there, that is as a Payment system - The only exception here being BTC). Unfortunately, this is not our fault, or anybody, but a lack of acceptance by the status quo.
As we speak I'm sure there are several players in the traditional market trying to take control of our cryptocurrencie economies, namely BTC. If they succeed at this, this is the end for everybody, BTC will never retain value and other coins will go down.
I think the most important thing people(That believe in have control of their wealth) can do is to not sell, and I talking about the wales.
Because in the end of the day it is simple enough, if our cryptocurrencies worth some, them someone will "create" the needed "bridge" to flow our wealth to them. In other words, we could have several use cases already, we don't because it is not in the best interest of the current financial system.
Re: [ANN] Bitcore - BTX - SEGWIT - BLOOM - ONLINE - CORE 0.14 - 4900+ BTX Claimed
No plan to other exchanges 
agree...what about poloniex, bittrex, novaexchange?
Our next goal is Bittrex.
Kind Regards Christian
It's almost 1 year..still our next goal is bittrex
After that post lots of things were discussed here. And I remember that was a consensus that while we still have the Airdrop running new Exchanges would be difficult. So let's wait May, and hopefully all weak hands should have dumped their coins and then we can look forward to new Exchanges.
Re: [ANN][HEXX: REBORN] Xnodes| Zero Protocol | Community Driven | CPU Only
Code:
2018-03-17 18:21:49 AcceptBlock ...
2018-03-17 18:21:49 AcceptBlock nHeight=231167
2018-03-17 18:21:49 CheckBlock() nHeight=231167, blockHash= 2f78b7cf473c6f8f07e66fd9f7b80f5021c10a7cebdfc7bc54dff678a04cc8d2, isVerifyDB = false
2018-03-17 18:21:49 ProcessNewBlock->ActivateBestChain
2018-03-17 18:21:49 ActivateBestChain()
2018-03-17 18:21:49 ActivateBestChainStep()
2018-03-17 18:21:49 ConnectTip() nHeight=231167
2018-03-17 18:21:49 ConnectBlock nHeight=231167, hash=2f78b7cf473c6f8f07e66fd9f7b80f5021c10a7cebdfc7bc54dff678a04cc8d2
2018-03-17 18:21:49 CheckBlock() nHeight=231167, blockHash= 2f78b7cf473c6f8f07e66fd9f7b80f5021c10a7cebdfc7bc54dff678a04cc8d2, isVerifyDB = false
2018-03-17 18:21:49 ERROR: ConnectBlock():
2018-03-17 18:21:49 InvalidChainFound: invalid block=2f78b7cf473c6f8f07e66fd9f7b80f5021c10a7cebdfc7bc54dff678a04cc8d2 height=231167 log2_work=42.324064 date=2018-03-17 18:20:21
2018-03-17 18:21:49 InvalidChainFound: current best=d35e013f1ec90a62b1036f6aa7f6bd9094039639bf1adc80385f6154fbb07f53 height=231166 log2_work=42.324 date=2018-03-17 18:17:11
2018-03-17 18:21:49 ERROR: ConnectTip(): ConnectBlock 2f78b7cf473c6f8f07e66fd9f7b80f5021c10a7cebdfc7bc54dff678a04cc8d2 failed
2018-03-17 18:21:49 InvalidChainFound: invalid block=2f78b7cf473c6f8f07e66fd9f7b80f5021c10a7cebdfc7bc54dff678a04cc8d2 height=231167 log2_work=42.324064 date=2018-03-17 18:20:21
2018-03-17 18:21:49 InvalidChainFound: current best=d35e013f1ec90a62b1036f6aa7f6bd9094039639bf1adc80385f6154fbb07f53 height=231166 log2_work=42.324 date=2018-03-17 18:17:11
2018-03-17 18:21:50 ERROR: AcceptBlockHeader: block 2f78b7cf473c6f8f07e66fd9f7b80f5021c10a7cebdfc7bc54dff678a04cc8d2 is marked invalid
2018-03-17 18:21:50 ERROR: invalid header received
2018-03-17 18:21:50 ProcessMessages(headers, 82 bytes) FAILED peer=12
2018-03-17 18:21:49 AcceptBlock nHeight=231167
2018-03-17 18:21:49 CheckBlock() nHeight=231167, blockHash= 2f78b7cf473c6f8f07e66fd9f7b80f5021c10a7cebdfc7bc54dff678a04cc8d2, isVerifyDB = false
2018-03-17 18:21:49 ProcessNewBlock->ActivateBestChain
2018-03-17 18:21:49 ActivateBestChain()
2018-03-17 18:21:49 ActivateBestChainStep()
2018-03-17 18:21:49 ConnectTip() nHeight=231167
2018-03-17 18:21:49 ConnectBlock nHeight=231167, hash=2f78b7cf473c6f8f07e66fd9f7b80f5021c10a7cebdfc7bc54dff678a04cc8d2
2018-03-17 18:21:49 CheckBlock() nHeight=231167, blockHash= 2f78b7cf473c6f8f07e66fd9f7b80f5021c10a7cebdfc7bc54dff678a04cc8d2, isVerifyDB = false
2018-03-17 18:21:49 ERROR: ConnectBlock():
2018-03-17 18:21:49 InvalidChainFound: invalid block=2f78b7cf473c6f8f07e66fd9f7b80f5021c10a7cebdfc7bc54dff678a04cc8d2 height=231167 log2_work=42.324064 date=2018-03-17 18:20:21
2018-03-17 18:21:49 InvalidChainFound: current best=d35e013f1ec90a62b1036f6aa7f6bd9094039639bf1adc80385f6154fbb07f53 height=231166 log2_work=42.324 date=2018-03-17 18:17:11
2018-03-17 18:21:49 ERROR: ConnectTip(): ConnectBlock 2f78b7cf473c6f8f07e66fd9f7b80f5021c10a7cebdfc7bc54dff678a04cc8d2 failed
2018-03-17 18:21:49 InvalidChainFound: invalid block=2f78b7cf473c6f8f07e66fd9f7b80f5021c10a7cebdfc7bc54dff678a04cc8d2 height=231167 log2_work=42.324064 date=2018-03-17 18:20:21
2018-03-17 18:21:49 InvalidChainFound: current best=d35e013f1ec90a62b1036f6aa7f6bd9094039639bf1adc80385f6154fbb07f53 height=231166 log2_work=42.324 date=2018-03-17 18:17:11
2018-03-17 18:21:50 ERROR: AcceptBlockHeader: block 2f78b7cf473c6f8f07e66fd9f7b80f5021c10a7cebdfc7bc54dff678a04cc8d2 is marked invalid
2018-03-17 18:21:50 ERROR: invalid header received
2018-03-17 18:21:50 ProcessMessages(headers, 82 bytes) FAILED peer=12
By the Explorer this is correct:
Code:
Block 231166: d35e013f1ec90a62b1036f6aa7f6bd9094039639bf1adc80385f6154fbb07f53
Block 231167: 2f78b7cf473c6f8f07e66fd9f7b80f5021c10a7cebdfc7bc54dff678a04cc8d2
Block 231167: 2f78b7cf473c6f8f07e66fd9f7b80f5021c10a7cebdfc7bc54dff678a04cc8d2
This is the second time I synchronize the node to see the node drop new blocks while the explorer correctly verify and accept the same solution. Something is not right, another thing is the node will unexpectedly stop replying to the stratum server, this happens while working directly with the node. Another thing is that I only see one node minting blocks.
Edit: I noticed that, after the XNodes get synchronized then it fails to validate new blocks.
Edit2: Running latest git version 4.0.3.0 protocol 99021 seems to be working ok - XNode count 81(29)
Code:
20:18:08 getblockchaininfo
20:18:08 {
"chain": "main",
"blocks": 231300,
"headers": 231300,
"bestblockhash": "a4a2d8a72605485c85c884169d6400046a9a5823376d0fa23fa76071aff9f937",
"difficulty": 0.06157637782254427,
"mediantime": 1521328219,
"verificationprogress": 0.9999976189703254,
"chainwork": "0000000000000000000000000000000000000000000000000000050a0e7d471c",
"pruned": false,
"softforks": [
{
"id": "bip34",
"version": 2,
"enforce": {
"status": true,
"found": 1000,
"required": 750,
"window": 1000
},
"reject": {
"status": true,
"found": 1000,
"required": 950,
"window": 1000
}
},
{
"id": "bip66",
"version": 3,
"enforce": {
"status": true,
"found": 1000,
"required": 750,
"window": 1000
},
"reject": {
"status": true,
"found": 1000,
"required": 950,
"window": 1000
}
},
{
"id": "bip65",
"version": 4,
"enforce": {
"status": true,
"found": 1000,
"required": 750,
"window": 1000
},
"reject": {
"status": true,
"found": 1000,
"required": 950,
"window": 1000
}
}
],
"bip9_softforks": {
"csv": {
"status": "failed",
"startTime": 1517744282,
"timeout": 1517744282
},
"segwit": {
"status": "failed",
"startTime": 1517744282,
"timeout": 1517744282
}
}
}
20:18:08 {
"chain": "main",
"blocks": 231300,
"headers": 231300,
"bestblockhash": "a4a2d8a72605485c85c884169d6400046a9a5823376d0fa23fa76071aff9f937",
"difficulty": 0.06157637782254427,
"mediantime": 1521328219,
"verificationprogress": 0.9999976189703254,
"chainwork": "0000000000000000000000000000000000000000000000000000050a0e7d471c",
"pruned": false,
"softforks": [
{
"id": "bip34",
"version": 2,
"enforce": {
"status": true,
"found": 1000,
"required": 750,
"window": 1000
},
"reject": {
"status": true,
"found": 1000,
"required": 950,
"window": 1000
}
},
{
"id": "bip66",
"version": 3,
"enforce": {
"status": true,
"found": 1000,
"required": 750,
"window": 1000
},
"reject": {
"status": true,
"found": 1000,
"required": 950,
"window": 1000
}
},
{
"id": "bip65",
"version": 4,
"enforce": {
"status": true,
"found": 1000,
"required": 750,
"window": 1000
},
"reject": {
"status": true,
"found": 1000,
"required": 950,
"window": 1000
}
}
],
"bip9_softforks": {
"csv": {
"status": "failed",
"startTime": 1517744282,
"timeout": 1517744282
},
"segwit": {
"status": "failed",
"startTime": 1517744282,
"timeout": 1517744282
}
}
}
Re: [ANN] | Rubix (RBX) | PoW/PoS | Wish Algo | MasterNodes | s-messages | VRX 3.0 |
Code:
ERROR: AcceptBlock() : Velocity rejected block 704, required parameters not met
This feature is nice I think, it is less likely that someone with lots of hashpower come and flood the blockchain with valid blocks. But, we are almost 1 hour without blocks, because it will drop a valid solution for the sake of block time(As I understood this), maybe you should reduce the block time to 2.5 minutes or even less, so that should be less likely to occur. Good luck!
Oh, and if your are not releasing the source, then do a Linux build. =)
Re: [ANN]Bitcore- BTX - SEGWIT - lowest fee - hybrid fork 1:0.5 of Bitcoin
I running two version of the Bitcore Node: v0.14.1.6-2b30982 and v0.15.0.2-gba8ed3a93be. I running specifically the latter because this version is accepting connections for both 0.14.1.6 and 0.15.0.2.
As I see in the blockexplorer looks like most of the network is running /BitCoreCore:0.15.0.2/, it may be the version I also running but I can't say for sure.
As people update their node version, our nodes need to accept both versions for a while. The latest release can't do that.
For the record:
The version I found that accepts both version is this one:
I also would like to know how can I deploy that specific version(The one that accepts both old and new version) from the git repository, I tested the binaries for Linux but they are only accepting 0.15.0.2.
Stay safe,
felco
As I see in the blockexplorer looks like most of the network is running /BitCoreCore:0.15.0.2/, it may be the version I also running but I can't say for sure.
As people update their node version, our nodes need to accept both versions for a while. The latest release can't do that.
For the record:
Code:
bitcore-qt.exe: SHA256:a6621fcadbb5b18f806ddba9249b98a154e369d4787d5c32e94aa6a5671addea
The version I found that accepts both version is this one:
Code:
bitcore-server-qt.exe: SHA256: c959cb3b69a83cc4773dadf3e4f23e6d967e0db39eec4d59452509ae12026112
I also would like to know how can I deploy that specific version(The one that accepts both old and new version) from the git repository, I tested the binaries for Linux but they are only accepting 0.15.0.2.
Stay safe,
felco
Hello guys!
I made a new pool for very low mining fees. I would like to invite anyone willing to help with testing to point some hashpower to it.
Here it is: http://pool.gtk.cl:81
I open to coins suggestions to add to the pool.
Thanks!
I made a new pool for very low mining fees. I would like to invite anyone willing to help with testing to point some hashpower to it.
Here it is: http://pool.gtk.cl:81
I open to coins suggestions to add to the pool.
Thanks!
Re: [ANN] MUNcoin - PoW 100% [SKUNK] [MASTERNODE] [BOUNTIES] [ANTI-INSTAMINE]
Small Fee Pool: http://pool.gtk.cl:81 - 0.25%
Code:
-a skunk stratum+tcp://pool.gtk.cl:8433 -u -p [c=MUN]
Hello guys!
I made a new pool for very low mining fees. I would like to invite anyone willing to help with testing to point some hashpower to it.
Here it is: http://pool.gtk.cl:81
Thanks!
I made a new pool for very low mining fees. I would like to invite anyone willing to help with testing to point some hashpower to it.
Here it is: http://pool.gtk.cl:81
Thanks!
Re: [ANN]Bitcore- BTX - SEGWIT - lowest fee - hybrid fork 1:0.5 of Bitcoin
For those complaining about Cryptopia, yes there is a problem there but it is not limited to Bitcore. We need other exchanges even to prevent price manipulation. So be aware of that problem with Cryptopia wallets - some days ago, I deposit some ZEC there and while in the blockchain I had more than 40 confirmations, I didn't have the 20 confirms Cryptopia asks for ZEC. And we all now that this is completely unnecessary. If you have 3 confirms that's pretty much secure to move the funds. Also, whenever your transaction enters the Blockchain and you see the pending deposit at Cryptopia, that means that what is to happen is at every new block in that blockchain one confirmation more in the deposit tab. This is not happening there, maybe it is on purpose which I don't think is completely out of question or they have a worse problem to deal with. But still, if they show you the Deposit, if everything were working as expected, you can pretty much forget the Deposit Tab go to the Explorer count how many blocks until n-Confirms, and the Deposit Tab would reflect that. I know most exchanges do apply some delay, like at Poloniex if I deposit Ether and Ether blocks go very fast, they will not follow as you would expect and it delays the deposit a little bit, but hey that is about 15 minutes or something in that range.
Look, as I can see we all want Bittrex, Binance or Poloniex for Bitcore. If we need to raise funds, let's raise funds to list it! Binance requires the developer to Apply for Listing.
If we want that, let's do this, let make it happen for God Sake, Cryptopia is f* me in the Ars and it is hurting dudes.
Look, as I can see we all want Bittrex, Binance or Poloniex for Bitcore. If we need to raise funds, let's raise funds to list it! Binance requires the developer to Apply for Listing.
If we want that, let's do this, let make it happen for God Sake, Cryptopia is f* me in the Ars and it is hurting dudes.
Re: [ANN]Bitcore- BTX - SEGWIT - lowest fee - hybrid fork 1:0.5 of Bitcoin
ciro1
where I can see a list of preers (nodes) for the synchronization of the wallet - my wallet does not see the peers.
where I can see a list of preers (nodes) for the synchronization of the wallet - my wallet does not see the peers.
I'm sorry but I couldn't find the nodes list anymore, you should try installing the latest version of the wallet and see if it sync. Please always backup your wallet before anything.
cryptopia has node list, check coin info there.
This is not a extensive list, but can help if you are out of peers:
Code:
addnode=211.22.182.101:8555
addnode=88.115.99.24:8555
addnode=173.249.10.130:8555
addnode=208.52.184.212:8555
addnode=107.175.215.208:8555
addnode=177.33.1.40:8555
addnode=180.183.13.97:8555
addnode=199.233.247.4:8555
addnode=178.136.226.254:8555
addnode=185.194.140.60:8555
addnode=168.1.142.114:8555
addnode=70.113.33.131:8555
addnode=144.217.67.68:8555
addnode=134.255.225.139:8555
addnode=188.68.39.1:8555
addnode=83.243.113.4:8555
addnode=88.115.99.24:8555
addnode=173.249.10.130:8555
addnode=208.52.184.212:8555
addnode=107.175.215.208:8555
addnode=177.33.1.40:8555
addnode=180.183.13.97:8555
addnode=199.233.247.4:8555
addnode=178.136.226.254:8555
addnode=185.194.140.60:8555
addnode=168.1.142.114:8555
addnode=70.113.33.131:8555
addnode=144.217.67.68:8555
addnode=134.255.225.139:8555
addnode=188.68.39.1:8555
addnode=83.243.113.4:8555
Re: [ANN]Bitcore- BTX - SEGWIT - lowest fee - hybrid fork 1:0.5 of Bitcoin
please please please BTX team, can you change this horrible pink color, and find a solution for the scaling on high-DPI screens !
My eyes are bleeding !
Thanks
Sorry meditationguru, just try and find the inner pink-core in yourself and you will learn to enjoy these colourings. ; )My eyes are bleeding !
Thanks
Don't expect a colour change from our side, that's the BTX brand.
Is this Linux you are running? There are no scaling issues on my Windows machine, that's why I'm asking.
Yeah, I know pink is BTX color, and I have no problem with pink color, but maybe something more... subtle would be nice and less aggressive for the eyes
Yeah... I would like that too. I saw there is a "Theme" option now, perhaps you guys may just add a "Default QT"?