Search content
Sort by
Showing 20 of 346 results by joshafest
any news here?
where can I buy b3 coins
currently nowhere , we are working on new updatewhere can I buy b3 coins
Today i try to compile the Wallet on my Raspberry Pi 2 with the new Buster Image, but by the compile i have follow error, anyone have an idea?
Thank you for all ideas, regards
Code:
~
In file included from /usr/include/boost/asio/ssl/context.hpp:757,
from /usr/include/boost/asio/ssl.hpp:18,
from src/rpcprotocol.h:18,
from src/rpcclient.cpp:9:
/usr/include/boost/asio/ssl/impl/context.ipp:326:1: note: candidate: ‘boost::asio::ssl::context::context(boost::asio::ssl::context&&)’
context::context(context&& other)
^~~~~~~
/usr/include/boost/asio/ssl/impl/context.ipp:326:1: note: candidate expects 1 argument, 2 provided
/usr/include/boost/asio/ssl/impl/context.ipp:63:1: note: candidate: ‘boost::asio::ssl::context::context(boost::asio::ssl::context_base::method)’
context::context(context::method m)
^~~~~~~
/usr/include/boost/asio/ssl/impl/context.ipp:63:1: note: candidate expects 1 argument, 2 provided
In file included from src/util.h:16,
from src/rpcclient.cpp:10:
src/tinyformat.h: In static member function ‘static const char* tinyformat::detail::FormatIterator::streamStateFromFormat(std::ostream&, unsigned int&, const char*, int, int)’:
src/tinyformat.h:785:21: warning: this statement may fall through [-Wimplicit-fallthrough=]
out.setf(std::ios::uppercase);
~~~~~~~~^~~~~~~~~~~~~~~~~~~~~
src/tinyformat.h:786:9: note: here
case 'x': case 'p':
^~~~
src/tinyformat.h:791:21: warning: this statement may fall through [-Wimplicit-fallthrough=]
out.setf(std::ios::uppercase);
~~~~~~~~^~~~~~~~~~~~~~~~~~~~~
src/tinyformat.h:792:9: note: here
case 'e':
^~~~
src/tinyformat.h:797:21: warning: this statement may fall through [-Wimplicit-fallthrough=]
out.setf(std::ios::uppercase);
~~~~~~~~^~~~~~~~~~~~~~~~~~~~~
src/tinyformat.h:798:9: note: here
case 'f':
^~~~
src/tinyformat.h:802:21: warning: this statement may fall through [-Wimplicit-fallthrough=]
out.setf(std::ios::uppercase);
~~~~~~~~^~~~~~~~~~~~~~~~~~~~~
src/tinyformat.h:803:9: note: here
case 'g':
^~~~
make: *** [Makefile:2789: build/rpcclient.o] Fehler 1
pi@raspberrypi:~/B3-CoinV2 $
In file included from /usr/include/boost/asio/ssl/context.hpp:757,
from /usr/include/boost/asio/ssl.hpp:18,
from src/rpcprotocol.h:18,
from src/rpcclient.cpp:9:
/usr/include/boost/asio/ssl/impl/context.ipp:326:1: note: candidate: ‘boost::asio::ssl::context::context(boost::asio::ssl::context&&)’
context::context(context&& other)
^~~~~~~
/usr/include/boost/asio/ssl/impl/context.ipp:326:1: note: candidate expects 1 argument, 2 provided
/usr/include/boost/asio/ssl/impl/context.ipp:63:1: note: candidate: ‘boost::asio::ssl::context::context(boost::asio::ssl::context_base::method)’
context::context(context::method m)
^~~~~~~
/usr/include/boost/asio/ssl/impl/context.ipp:63:1: note: candidate expects 1 argument, 2 provided
In file included from src/util.h:16,
from src/rpcclient.cpp:10:
src/tinyformat.h: In static member function ‘static const char* tinyformat::detail::FormatIterator::streamStateFromFormat(std::ostream&, unsigned int&, const char*, int, int)’:
src/tinyformat.h:785:21: warning: this statement may fall through [-Wimplicit-fallthrough=]
out.setf(std::ios::uppercase);
~~~~~~~~^~~~~~~~~~~~~~~~~~~~~
src/tinyformat.h:786:9: note: here
case 'x': case 'p':
^~~~
src/tinyformat.h:791:21: warning: this statement may fall through [-Wimplicit-fallthrough=]
out.setf(std::ios::uppercase);
~~~~~~~~^~~~~~~~~~~~~~~~~~~~~
src/tinyformat.h:792:9: note: here
case 'e':
^~~~
src/tinyformat.h:797:21: warning: this statement may fall through [-Wimplicit-fallthrough=]
out.setf(std::ios::uppercase);
~~~~~~~~^~~~~~~~~~~~~~~~~~~~~
src/tinyformat.h:798:9: note: here
case 'f':
^~~~
src/tinyformat.h:802:21: warning: this statement may fall through [-Wimplicit-fallthrough=]
out.setf(std::ios::uppercase);
~~~~~~~~^~~~~~~~~~~~~~~~~~~~~
src/tinyformat.h:803:9: note: here
case 'g':
^~~~
make: *** [Makefile:2789: build/rpcclient.o] Fehler 1
pi@raspberrypi:~/B3-CoinV2 $
Thank you for all ideas, regards
Hello ! It seems you are using wrong version of boost, you can try with boost 1.55
I think , adding votings to a unconfirmed transaction is a solution .
How it works --
1. Someone broadcast a transaction (maybe with tag like dynamic transaction) to p2p network .
2. Each node receiving the transaction see if its a valid transaction (say by applying AcceptToMempol/AcceptableInput),
2a. If successful (Transaction is fully valid ) , give upvote(with some sort of signature )
2b. If failed (Transaction is not good) , do nothing or give downvote
3. Now, Network count the votes,
3a. If upvotes - downvotes >= certain amount of votes (say 100, i.e. upvotes - downvotes >= 100);
then assume transaction is valid and can be spent, (with proof that it has enough upvotes )
3b. If downvotes > upvotes ,
then transaction is not valid and should not be submitted to miners.
4. A transaction having enough upvotes submitted to miners (that in 3a)
How it works --
1. Someone broadcast a transaction (maybe with tag like dynamic transaction) to p2p network .
2. Each node receiving the transaction see if its a valid transaction (say by applying AcceptToMempol/AcceptableInput),
2a. If successful (Transaction is fully valid ) , give upvote(with some sort of signature )
2b. If failed (Transaction is not good) , do nothing or give downvote
3. Now, Network count the votes,
3a. If upvotes - downvotes >= certain amount of votes (say 100, i.e. upvotes - downvotes >= 100);
then assume transaction is valid and can be spent, (with proof that it has enough upvotes )
3b. If downvotes > upvotes ,
then transaction is not valid and should not be submitted to miners.
4. A transaction having enough upvotes submitted to miners (that in 3a)
Re: [B3]B3Coin Hybrid POW/POS [Scrypt] - ANTI-INSTAMINE, NO PREMINE, NO ICO, NO IPO
Hey, stakeunited is closing
is KB3 listed on any other Staking pool?
is KB3 listed on any other Staking pool?
This thread has been moved to
https://bitcointalk.org/index.php?topic=2811744.0
People have allowed this coin to sleep.
Coinexchange.io seems to have the highest trade volume.
Coinexchange.io seems to have the highest trade volume.
Its because we are head down for work.
Re: [B3]B3Coin Hybrid POW/POS [Scrypt] - ANTI-INSTAMINE, NO PREMINE, NO ICO, NO IPO
Announcement: as the 3rd party treasurer of b3 superblock I resign effectively immediately. This is just to inform some history and the reasons why. I was already banned in their discord, FYI. www.myfrogger.com is the announcement.
"I am not staying with a coin that is not willing to remain 100% transparent like it boasts and was promised to all of you. "
They crossed this bridge LONG ago when Jamie and those folks robbed everyone blind.
Glad to see you've come around as well.
This project doesn't deserve my post/bump, but I'm glad to see major community members getting their heads out of their asses!
Re: [B3]B3Coin Hybrid POW/POS [Scrypt] - ANTI-INSTAMINE, NO PREMINE, NO ICO, NO IPO
I think it's dead in the way a lot of the community see B3. A few made money on it and lots lost money... It just sorta feels tainted.
The discussion was moved to https://bitcointalk.org/index.php?topic=2811744
You're welcome to come to our Discord and see that B3 Coin far from dead, it is just getting started.
you mean it was moved to a thread where they can delete messages so they can scam people again
What are you on about? There has been poor management from the old team a long time ago, and because of this they are gone. If you believe they pulled a scam, I challenge you to show what happened which makes you use that word.
I don't "think", I know.
Poor management resulted in the loss of coins from "us". Thus making it tainted.
Thank god the pool people did their job eventually, but it wasn't the pool that made it scammy. It was the core development team.
Rather than pull of the stuff premined or whatever, they did "it" in the middle. I'm glad there was other more stupid shit going on in the Altcoin world and this went largely unnoticed thus far... If Forbes put this in their magazine. I would bet Jamie and a few others would go to jail.
Blackballing addresses unexpectedly over a holiday weekend isn't the way to go about fixing stuff and that isn't including the stuff that resulted in losses for the majority of the community.
Re: [ANN][MAC]Machinecoin | TimeTravel Algo | **Masternodes soon
anyone have an estimate of how many masternodes will go live in the first month? my guess is 350-400
I'm guessing ~100?
when is the masternodes from this coin will go alive ?
because on the roadmap said Q1 2018 is the time, and now we are already in Q2 2018
The roadmap is an estimate, but you are correct and we are a little behind schedule. The masternodes are coded and running on the testnet and should be live real soon.
The reason for the delay is because the dev decided to go ahead and update core from v0.14.xx to v0.16 with the masternode release to prevent everyone from having to do 3 separate upgrades so far this year. I believe most other masternode coins are on core v0.12 as Dash. To my knowledge, no other masternode coins are on 16. It is taking a bit longer, but check out the upgrades coming to the new core and I think you will see the worth of the wait.
wow that is great news, even BSD is not on core .16 yet. who will be first
I assume us considering ours is already working
By the way, we got an update in the telegram today that masternodes should be ready for deployment within the next couple of days. 
Hello,
the account from Limx Dev is hacked.
Account link : https://bitcointalk.org/index.php?action=profile;u=389271
Signmessage via Airdrop address 1 (Bitcore)
Please lock this account.
Best Regards Dishwara
the account from Limx Dev is hacked.
Account link : https://bitcointalk.org/index.php?action=profile;u=389271
Signmessage via Airdrop address 1 (Bitcore)
Code:
-----BEGIN BITCORE SIGNED MESSAGE-----
13hwgY4YUvrgnhjLP5ugFafL1cmbRRtr5e
-----BEGIN SIGNATURE-----
Limx Dev 30-01-2018 Account Dishwara
-----END BITCOIN SIGNED MESSAGE-----
H4XY9qSsd3uJAOUYRchgVEe+aUs60jIOcEUlqoFl+qU6Ikv2WG7+tL5Za57Xud/NHHHFYKQ3RRC5uRruZEaovOc=
13hwgY4YUvrgnhjLP5ugFafL1cmbRRtr5e
-----BEGIN SIGNATURE-----
Limx Dev 30-01-2018 Account Dishwara
-----END BITCOIN SIGNED MESSAGE-----
H4XY9qSsd3uJAOUYRchgVEe+aUs60jIOcEUlqoFl+qU6Ikv2WG7+tL5Za57Xud/NHHHFYKQ3RRC5uRruZEaovOc=
Please lock this account.
Best Regards Dishwara
Limxdev informed me that his account get hacked,
I verify that limxdev's account is hacked.
perfect a NEW thread that is self moderated so everything will look perfect ins b3 / KB3 land...
Really guys? if you do not want ppl screaming scam all the time, don't do things like this and toss up even more RED flags
There are a lot places where you can publish your research, .. but I don't think it is right place for publication, Really guys? if you do not want ppl screaming scam all the time, don't do things like this and toss up even more RED flags
And , I don't see your point, you want to day that Bitcoin was launched too earlier and you were not told , even though all was open source, ...so its red flag, ......
what you are saying is similar to this situation, even though all and everything was open sourced on GitHub, am I or anyone else responsible for you not being taught mathematics or coding at school ? or ..?
Re: [B3]B3Coin Hybrid POW/POS [Scrypt] - ANTI-INSTAMINE, NO PREMINE, NO ICO, NO IPO
This thread has been moved to new thread
https://bitcointalk.org/index.php?topic=2811744.new#new
https://bitcointalk.org/index.php?topic=2811744.new#new
Re: [B3]B3Coin Hybrid POW/POS [Scrypt] - ANTI-INSTAMINE, NO PREMINE, NO ICO, NO IPO
Yobit has problems, Please don't use yobit , And the 1 kB3 = 1000 B3, kB3 is a trading asset, and B3 is coin, exchangers which are at old wallet have B3 unit as default, and which are at new wallet have kB3 as default unit.
Max transaction size was 2 B in B3, but now it is 622B, it was announced much earlier.
lol that so funny!! so the max transaction was 2billions for a coins with more than 500billions B3 coins, and now its 622b for a 500millions coins ahahhaah. where is the logic? B3's dev trolling us. the right price is on CMC i have calculate it too, and its 0.025$ for 1KB3 the post before your who say its will be 1$ for 1KB3 are joking! cause B3 will need a X50 maket cap for hit 1$ so 500millions $ market cap. and you are right, its just a marketing confusion created by puting K befor B3, but mostly people think the price on CMC is for 1b3, but its for 1KB3.Max transaction size was 2 B in B3, but now it is 622B, it was announced much earlier.
This what you wrote is insane.. you dont know how to read or you dont understand how CMC calculate the price.. its a mess i agree but its very easy to understand.. i can bet with you for a 1BTC that a price on CMC is for 1B3, they have listed also a KB3 from CoinsMarkets for 0,09$ but its updated 31 hour ago and KB3 price did not effect in the calculation.. The price on CMC is price of Yobit.. dont you see 100% volume in the Yobit line and all others are 0%??!!
Re: [B3]B3Coin Hybrid POW/POS [Scrypt] - ANTI-INSTAMINE, NO PREMINE, NO ICO, NO IPO
Yobit has problems, Please don't use yobit , And the 1 kB3 = 1000 B3, kB3 is a trading asset, and B3 is coin, exchangers which are at old wallet have B3 unit as default, and which are at new wallet have kB3 as default unit.
Max transaction size was 2 M in kB3, but now it is 622M, it was announced much earlier.
Max transaction size was 2 M in kB3, but now it is 622M, it was announced much earlier.
Re: [B3]B3Coin Hybrid POW/POS [Scrypt] - ANTI-INSTAMINE, NO PREMINE, NO ICO, NO IPO
A lot new people in crypto and also in the B3 , who believe more in GUI or say their eyes , rather than to believe in core ,
Let me clarify again,
the 60% of your stake was not stolen by anyone, you never generated those coins, it was only a gui bug that was showing the whole value of transaction (vtx[1]*GetvalueOut()) , so one who got fundamental payment also saw that a lot coins come to him and one who staked.
This was only a bug in qt(gui) which people mistakenly thought that their 60% stolen, and fundamental people thought that 40% stolen from them.
People who were old in crypto and don't know the concept also effected by this.
But this bug is fixed in new wallet v3.1* so if you go to your past transactions, you will see that you never generated those coins, your coins were not stolen
Let me clarify again,
the 60% of your stake was not stolen by anyone, you never generated those coins, it was only a gui bug that was showing the whole value of transaction (vtx[1]*GetvalueOut()) , so one who got fundamental payment also saw that a lot coins come to him and one who staked.
This was only a bug in qt(gui) which people mistakenly thought that their 60% stolen, and fundamental people thought that 40% stolen from them.
People who were old in crypto and don't know the concept also effected by this.
But this bug is fixed in new wallet v3.1* so if you go to your past transactions, you will see that you never generated those coins, your coins were not stolen
Re: [B3]B3Coin Hybrid POW/POS [Scrypt] - ANTI-INSTAMINE, NO PREMINE, NO ICO, NO IPO
New Wallet has been releasd
Some Issues get fixed, To avoid forks,
Please use bootstrap
Bootstrap
https://github.com/B3-Coin/B3-CoinV2/releases/download/3.1.1.1/b3_bootstrap_block_82969.zipChanges
- Default unit - which is kB3 now (Virtual swap)
- Fixed GUI bug - people thought that 60% of their stake were stolen by fundamental nodes , however they never generated that much coins, this all happened due to this bug.
- One coin of FN now hidden (unspendable) - The fundamental node payment return 1 coin to that address, which is now remain hidden from available coins
- Transactions less then 1 coin cannot be done from gui qt
What still remains
- The Fundamental node payment warning still shows in B3 not in kB3
- There is still danger to spend the 1 coin from fundamental node in staking - Available coins for staking still can use 1 coin from fundamental node
Re: [B3]B3Coin Hybrid POW/POS [Scrypt] - ANTI-INSTAMINE, NO PREMINE, NO ICO, NO IPO
Joshafest can u please explain why total supply is higher than max supply?
it was max transaction limit, which was mistakenly taken as max supply.