hi
I made a post about jumbucks on btc12.com
http://btc12.com/2016/08/22/jumbucks-changingnameandchain/
btc12.com is updating Chinese investors/gamblers of recent altcoin news and ICO portfolios.
enjoy!
Topic: [JBS] Jumbucks - No IPO/ICO - Proof of Stake - Slack - DCR Stake Pool - 2+ Years - page 5. (Read 48226 times)
August 21, 2016, 07:11:14 PM
August 20, 2016, 01:56:55 PM
Jumbucks Releases The Exclusive Crypto Community Cards
Jumbucks is proud to announce the release of their Crypto Community Cards project. Crypto Community Cards is a unique product that can only be purchased with Jumbucks, through the website of launch partner Cryptochips.net. This product was created by the Jumbucks' team as a fun and promotional product, for the whole cryptocurrency community. We hope you embrace this initiative, and we look forward to meeting your interest with even more Community Card sets in the future!
"Community Cards are a fun way to introduce your friends that are new to crypto, to the wealth of notable personalities who have made an impact on this revolutionary technology. Trade, collect, and share - This is crypto!"
@cryptokrill
Cryptocurrencies at their heart are intended to be mediums of exchange for goods and services, however oftentimes, this simple factor is forgotten. If there is no demand or value placed on holding a particular cryptocurrency then its value naturally declines. The goal of every cryptocurrency should be to work towards establishing an intrinsic value, such that the marketplace begins to depend upon its very existence.
Twitter user @cryptokrill first mentioned the idea of crypto trading cards to me just a short while after Jumbucks' launch. In light of the vast array of cryptocurrency celebrities and personalities, I thought his idea was the perfect way to create memorabilia marking this exciting time in history. Because time and innovation move so swiftly in the world of cryptocurrency, the names and faces you know today might be completely forgotten by tomorrow, or they just might turn out to be the great leaders of a brave new future. Crypto Community Cards ensure that the excitement of these days will not be forgotten.
Our team worked together to brainstorm and plan out each detail of this project., and along the way we created a spreadsheet of over 100 people in the cryptocurrency world and went through several card designs.
In the end, and after weeks of development, we came up with 100 packs of 5 cards each which will make up the initial batch for sale to the public. The first set has a unique card for each of the following individuals: Gavin Andresen, Mark Karpeles, Jordan Fish, Andreas M. Antonopoulos and Charlie Shrem.
Each card is printed on ultra thick 16pt card stock, is full color on both sides, and is polished off with a UV coated glossy finish. These cards are made with the highest quality, and so are perfect for collecting! The front of each card features a colorful depiction of a crypto community member with a brief bio and quotation on the back. To complete the experience of opening a new pack of cards, each set is wrapped in beautiful foil packaging.
We encourage the community to give us their feedback on the Cryto Community Cards. We have a wealth of great ideas for future printings, and future sets are planned with additional features to enhance the collectible value of each card.
The Crypto Community Cards are a great way to spread word of cryptocurrencies to your friends and family, and they are set to launch just before Thanksgiving so that orders made today will arrive before Christmas!
This project was brought to you by the following people who helped contribute to its creation: @cryptokrill, @Sicarious_, @sasankansony, @yakpimp, and Jumbuck's developer, @jyap.
In the end we are excited and proud to bring the world a unique product that cannot simply be replicated. A lot of effort, cost, and time went into these cards to ensure that we were bringing something unique to the community, and not simply slapping the Jumbucks logo on hats, shirts, or keychains from a manufacturing wholesaler. Collecting coins goes hand-in-hand with collecting cards. It is our hope that the community embraces this project sot hat we can make reprints of the first set, and produce even more unique sets for people to enjoy! Who knows, one of these future sets might feature you.
Jumbucks is a Fair Launch cryptocurrency which launched without an IPO and with zero premine. Jumbucks currently runs as 100% Proof of Stake, and is currently traded on Bittrex, Cryptsy and will be available at launch on the upcoming AltMarket.com. Find out more information at GetJumbucks.com.
The first set is available for purchase NOW on Cryptochips.net!
August 20, 2016, 01:34:09 PM
can you elaborate zcash part? tks
August 20, 2016, 04:24:49 AM
To see some JBS-EE network stats, navigate to http://jbs-ee.sigwo.com and take a look 
August 20, 2016, 04:24:07 AM
Will there be an option to send other select alt coins into the JBS system when we swap to the new codebase?
August 20, 2016, 04:22:33 AM
etherwall works really well. tested that out tonight. just a simple GUI for managing accounts. simple send and receive. another potential option as a GUI.
https://github.com/almindor/etherwall
August 19, 2016, 05:56:29 AM
Serial alt coin developers, experimenting in public and transference of value
Serial alt coin developers
There are many parallels with this crypto game in other known microcosms such as the drug game we see portrayed in serial cop dramas such as The Wire.
In this game there are many unstated rules but what they come down to is ethics, doing the right thing and general respect for other peoples time and money.
We understand that many of the players in this game are in certain positions such as exchanges, developers and traders. Those in the role of an exchange could basically screw us at any time by stealing which would totally violate any assumed code. For developers, there are many grey areas which are often times "accepted" but are not definitely a violation of the code. This would include the concept of the "serial alt coin developer".
The serial alt coin developer is one which divides their time and efforts between avoiding the coins they have made and launched in the past, and ones that they are about to make.
This is something which never sat well with me. It has never been acceptable to me. Consider it my way of respecting the game and the respective players.
When I set out to make a coin and put my name to it, I did. And to this day I have never launched another coin and been solely focused on one.
Experimenting in public
There are ways to experiment in public. Right now we are running a live Testnet for the next incarnation of Jumbucks. A key point is that this Testnet allows us to learn, rapidly test and experiment but in now way could it cause financial harm as there is no value added to the coins.
Experimenting by launching multiple coins is deeply disrespectful to those to put in money. At the end of the day, an abandoned coin is lost money. There can be hopes of a revival but the damage has been done. A coin with no focused development is one which can only be one filled with empty promises and story telling.
Transference of value
This shouldn't be a common occurrence but we faced a brick wall in terms of development that the code base we were running on wasn't actively worked on by multiple people world wide. Ultimately it is a stale codebase which had current issues but would never be updated.
If we were serial alt coin developers we would have launched a new experiment in public with no recourse or reflection that we were creating "just another coin".
What we will do instead is respect the money and value that people have put into the coin, and by transferring value to a new chain we aren't screwing people over.
So while there are cut and dry violations of the game such as the recent Bitfinex hack incident, developers will tend to always tread that fine line of being a scammer and on that one that is genuinely trying something which might work out.
In summary, I feel that respect for this crypto game comes down to some obvious plays for me.
Namely:
Serial alt coin developers
There are many parallels with this crypto game in other known microcosms such as the drug game we see portrayed in serial cop dramas such as The Wire.
In this game there are many unstated rules but what they come down to is ethics, doing the right thing and general respect for other peoples time and money.
We understand that many of the players in this game are in certain positions such as exchanges, developers and traders. Those in the role of an exchange could basically screw us at any time by stealing which would totally violate any assumed code. For developers, there are many grey areas which are often times "accepted" but are not definitely a violation of the code. This would include the concept of the "serial alt coin developer".
The serial alt coin developer is one which divides their time and efforts between avoiding the coins they have made and launched in the past, and ones that they are about to make.
This is something which never sat well with me. It has never been acceptable to me. Consider it my way of respecting the game and the respective players.
When I set out to make a coin and put my name to it, I did. And to this day I have never launched another coin and been solely focused on one.
Experimenting in public
There are ways to experiment in public. Right now we are running a live Testnet for the next incarnation of Jumbucks. A key point is that this Testnet allows us to learn, rapidly test and experiment but in now way could it cause financial harm as there is no value added to the coins.
Experimenting by launching multiple coins is deeply disrespectful to those to put in money. At the end of the day, an abandoned coin is lost money. There can be hopes of a revival but the damage has been done. A coin with no focused development is one which can only be one filled with empty promises and story telling.
Transference of value
This shouldn't be a common occurrence but we faced a brick wall in terms of development that the code base we were running on wasn't actively worked on by multiple people world wide. Ultimately it is a stale codebase which had current issues but would never be updated.
If we were serial alt coin developers we would have launched a new experiment in public with no recourse or reflection that we were creating "just another coin".
What we will do instead is respect the money and value that people have put into the coin, and by transferring value to a new chain we aren't screwing people over.
So while there are cut and dry violations of the game such as the recent Bitfinex hack incident, developers will tend to always tread that fine line of being a scammer and on that one that is genuinely trying something which might work out.
In summary, I feel that respect for this crypto game comes down to some obvious plays for me.
Namely:
- Not creating multiple alt coins which allows focus of developments to pass through to a common good
- Not conducting nonsensical value based experiments in public and respecting other peoples money.
- Transferring and retaining value on everything we do so that value can only grow and expand.
August 17, 2016, 03:30:23 AM
Jumbucks Ethereum Edition - Alpha 2 released
Here we present you the second "pre-launch" release. This release comes with lots of polish and some protocol changes.
JBS EE has now been modified to run with 88 seconds block times as the target with 8 coin rewards.
This is running really well as we can see some current blocks and times now that difficulty has leveled off:
If you are running Alpha 1, please delete everything in your data directory except for the keystore directory.
This Alpha 2 release has the Genesis Block and Boot node built in. Just run it.
Testnet addresses will have Testnet coins already pre-allocated in the Genesis block.
The Alpha 2 changes are incompatible with the Alpha 1 network.
Expect this network to have several changes before the actual launch. You can participate in Jumbucks Slack in the #jumbucks channel. Testing is going really well with many participants.
You can find the release here:
https://github.com/jumbucks/go-jumbucksee/releases/tag/v1.4.10-alpha2
Changes
Start the console and connect to my boot node:
Optionally: Running on a separate console
On one screen:
On another screen:
Binaries (compiled by Julian)
$ shasum -a 256 gjbsee-darwin-amd64.zip gjbsee-linux-amd64.tgz gjbsee-windows-4.0-amd64.exe.zip
816d213aea551854d6fcb0828d6b63c694d175cf166f963115b3b60b7e57ba3d gjbsee-darwin-amd64.zip
8bce4e117e2c4224055b8262c1faff42c725e9c54d789760a3515f3ac80273f8 gjbsee-linux-amd64.tgz
07a82577c0aaa710127577fef7685c22814622c9808193f550c6d76a0cbbee79 gjbsee-windows-4.0-amd64.exe.zip
Here we present you the second "pre-launch" release. This release comes with lots of polish and some protocol changes.
JBS EE has now been modified to run with 88 seconds block times as the target with 8 coin rewards.
This is running really well as we can see some current blocks and times now that difficulty has leveled off:
Code:
22:07:04.148341 - Block 950 [86150be1 / 86150be1]
22:08:45.275130 - Block 951 [9d34f0ea / 9d34f0ea]
22:09:53.300668 - Block 952 [7d9ded50 / 7d9ded50]
22:11:19.321095 - Block 953 [8c053e60 / 8c053e60]
22:12:02.440269 - Block 954 [210236e2 / 210236e2]
22:12:35.075147 - Block 955 [3ec999fb / 3ec999fb]
22:16:05.475079 - Block 956 [e0456825 / e0456825]
22:18:56.404921 - Block 957 [3e3e3e7f / 3e3e3e7f]
22:19:10.000041 - Block 958 [d5c0818a / d5c0818a]
22:20:34.256908 - Block 959 [0b2fe7f1 / 0b2fe7f1]
22:21:49.364843 - Block 960 [5f6d88d2 / 5f6d88d2]
22:22:25.089983 - Block 961 [547cb5db / 547cb5db]
22:23:50.231235 - Block 962 [f382e8d5 / f382e8d5]
22:24:00.591984 - Block 963 [24365298 / 24365298]
22:08:45.275130 - Block 951 [9d34f0ea / 9d34f0ea]
22:09:53.300668 - Block 952 [7d9ded50 / 7d9ded50]
22:11:19.321095 - Block 953 [8c053e60 / 8c053e60]
22:12:02.440269 - Block 954 [210236e2 / 210236e2]
22:12:35.075147 - Block 955 [3ec999fb / 3ec999fb]
22:16:05.475079 - Block 956 [e0456825 / e0456825]
22:18:56.404921 - Block 957 [3e3e3e7f / 3e3e3e7f]
22:19:10.000041 - Block 958 [d5c0818a / d5c0818a]
22:20:34.256908 - Block 959 [0b2fe7f1 / 0b2fe7f1]
22:21:49.364843 - Block 960 [5f6d88d2 / 5f6d88d2]
22:22:25.089983 - Block 961 [547cb5db / 547cb5db]
22:23:50.231235 - Block 962 [f382e8d5 / f382e8d5]
22:24:00.591984 - Block 963 [24365298 / 24365298]
If you are running Alpha 1, please delete everything in your data directory except for the keystore directory.
This Alpha 2 release has the Genesis Block and Boot node built in. Just run it.
Testnet addresses will have Testnet coins already pre-allocated in the Genesis block.
The Alpha 2 changes are incompatible with the Alpha 1 network.
Expect this network to have several changes before the actual launch. You can participate in Jumbucks Slack in the #jumbucks channel. Testing is going really well with many participants.
You can find the release here:
https://github.com/jumbucks/go-jumbucksee/releases/tag/v1.4.10-alpha2
Changes
- Modify Difficulty calculation
- Remove difficulty bomb
- Modify DifficultyBoundDivisor for faster retargeting
- Modify block time. Now 88 seconds
- Modify block reward. Now 8 coins per block
- Modify default NetworkId
- Modify discovery port
- Modify MainNetHomesteadBlock
- Hardcode the Genesis Block. No longer need to Initialize
- Hardcode the boot node. No longer need to specify
Start the console and connect to my boot node:
Code:
gjbsee console
Optionally: Running on a separate console
On one screen:
Code:
gjbsee
On another screen:
Code:
gjbsee attach ipc:/Users/julian/Library/JumbucksEE/gjbsee.ipc
Binaries (compiled by Julian)
$ shasum -a 256 gjbsee-darwin-amd64.zip gjbsee-linux-amd64.tgz gjbsee-windows-4.0-amd64.exe.zip
816d213aea551854d6fcb0828d6b63c694d175cf166f963115b3b60b7e57ba3d gjbsee-darwin-amd64.zip
8bce4e117e2c4224055b8262c1faff42c725e9c54d789760a3515f3ac80273f8 gjbsee-linux-amd64.tgz
07a82577c0aaa710127577fef7685c22814622c9808193f550c6d76a0cbbee79 gjbsee-windows-4.0-amd64.exe.zip
August 15, 2016, 09:15:54 PM
Token contract installed on JBS EE Testnet
I've deployed a Token contracts on the JBS EE Testnet.
Install Token contract:
I've sent some tokens to Testnet users so you can check your balance with the following (replace with your address):
Something we will do on the Live network is deploy a Global Registrar contract. This is similar to DNS or other name lookup systems.
This will allow Token names to be associated with contract Addresses.
I've deployed a Token contracts on the JBS EE Testnet.
Install Token contract:
Code:
token = eth.contract([{constant:false,inputs:[{name:'receiver',type:'address'},{name:'amount',type:'uint256'}],name:'sendCoin',outputs:[{name:'sufficient',type:'bool'}],type:'function'},{constant:true,inputs:[{name:'',type:'address'}],name:'coinBalanceOf',outputs:[{name:'',type:'uint256'}],type:'function'},{inputs:[{name:'supply',type:'uint256'}],type:'constructor'},{anonymous:false,inputs:[{indexed:false,name:'sender',type:'address'},{indexed:false,name:'receiver',type:'address'},{indexed:false,name:'amount',type:'uint256'}],name:'CoinTransfer',type:'event'}]).at('0xe5b45a5c9adbd078161d9d2cff4816e8f82d9455')
I've sent some tokens to Testnet users so you can check your balance with the following (replace with your address):
Code:
token.coinBalanceOf("0x476fd3e95ed3a1e9e764987bff3230b08850fd4d")
Something we will do on the Live network is deploy a Global Registrar contract. This is similar to DNS or other name lookup systems.
This will allow Token names to be associated with contract Addresses.
August 14, 2016, 02:48:10 PM
I have mist running on the JBSEE testnet chain.
I still have a lot of work to do on the code. Obviously renaming, but I cant reveal the new name just yet ;P
As well as removing all of the daofork code, a few other tweaks, and possibly some additions.
But things are coming along nicely
I still have a lot of work to do on the code. Obviously renaming, but I cant reveal the new name just yet ;P
As well as removing all of the daofork code, a few other tweaks, and possibly some additions.
But things are coming along nicely
August 13, 2016, 03:46:18 AM
Easter Egg
This contract is on the JBS EE Testnet.
Contract mined! address: 0x62718f95b5dfc6f92a09f7cee5a2ed5077708e54 transactionHash: 0x02f13efd029f0a696770050d7cac5c7b6f29ecb8e330e8f53f815b77cc69d014
Install contract:
Run contract:
Don't tell anyone after you read it so they can find it for themselves.
This contract is on the JBS EE Testnet.
Contract mined! address: 0x62718f95b5dfc6f92a09f7cee5a2ed5077708e54 transactionHash: 0x02f13efd029f0a696770050d7cac5c7b6f29ecb8e330e8f53f815b77cc69d014
Install contract:
Code:
var greeter2 = eth.contract([{constant:false,inputs:[],name:'kill',outputs:[],type:'function'},{constant:true,inputs:[],name:'greet',outputs:[{name:'',type:'string'}],type:'function'},{inputs:[{name:'_greeting',type:'string'}],type:'constructor'}]).at('0x62718f95b5dfc6f92a09f7cee5a2ed5077708e54');
Run contract:
Code:
greeter2.greet();
Don't tell anyone after you read it so they can find it for themselves.
August 12, 2016, 09:01:19 PM
I've set up a test pool at 104.207.133.114
I invite anyone with a rig to try it out. If you have any problems, please join the slack and get in touch with me or in the #jumbucks channel.
Also, add the pool node if you can, it helps payment processing.
I invite anyone with a rig to try it out. If you have any problems, please join the slack and get in touch with me or in the #jumbucks channel.
Also, add the pool node if you can, it helps payment processing.
Code:
enode://4a5b918960f5db18a5bd07b23a796c07269c5206165206ada39a6184cec476578a0a2e035d9aec034ab8061939dfd70957975e7c7e833220e9ff81d7f42430b7@[::]:30303
August 12, 2016, 03:03:47 AM
I've uploaded and built the Windows binary for Jumbucks Ethereum Edition - Alpha 1. Right now I have my cross compile environment up and running so we'll be able to support basically any architecture such as ARM (Raspberry Pi).
Here are some changes we are discussing:
Coin swap with a higher coin count ratio
For example 1:10. Right now Jumbucks has 3,602,462 JBS coins minted. The proposal would then be to increase the coin count proportionally to 36 million (or a different multiple). Purely on a mathematical scale, this doesn't change a thing in that you still have a same percentage. What changes is perception and actual use of the coin. A higher coin count works out better for distribution as there are more "full units" to disburse.
A new name with newly associated paradigms
This would be worthwhile at this stage since we are also making core changes to the coin.
Feel free to post your suggestions in this thread. Something cool would be a coin name and paired with an associated name for the coin units, for example "Ethereum" and "Ethers" or "Factom" and "Factoids".
zkSNARKs in Ethereum
This was recently published: https://z.cash/blog/zksnarks-in-ethereum.html
Adding zkSNARKs in a JBS EE would require "extending the Ethereum contract language to efficiently support verification of zkSNARK proofs. Specifically, we added a snarkverify precompile (like an opcode) to a fork of Parity which uses libsnark to verify generic proofs." As this requires modifying the underlying client/server code, this is something we could support and would make our chain unique.
Parity client
This is another "nice to have" feature but would benefit smaller embedded systems a lot.
Parity is an alternative Ethereum client written in Rust which is generally a faster systems level language compared to Go (which is what Geth is written in). Overall, it should use less resources.
Parity is fairly recently released which is why less people use it... But yeah, Geth was an early client.
You can run Parity in "--geth" mode with no issues. It just exposes a compatible communications mechanism that Geth uses.
Here are some changes we are discussing:
Coin swap with a higher coin count ratio
For example 1:10. Right now Jumbucks has 3,602,462 JBS coins minted. The proposal would then be to increase the coin count proportionally to 36 million (or a different multiple). Purely on a mathematical scale, this doesn't change a thing in that you still have a same percentage. What changes is perception and actual use of the coin. A higher coin count works out better for distribution as there are more "full units" to disburse.
A new name with newly associated paradigms
This would be worthwhile at this stage since we are also making core changes to the coin.
Feel free to post your suggestions in this thread. Something cool would be a coin name and paired with an associated name for the coin units, for example "Ethereum" and "Ethers" or "Factom" and "Factoids".
zkSNARKs in Ethereum
This was recently published: https://z.cash/blog/zksnarks-in-ethereum.html
Adding zkSNARKs in a JBS EE would require "extending the Ethereum contract language to efficiently support verification of zkSNARK proofs. Specifically, we added a snarkverify precompile (like an opcode) to a fork of Parity which uses libsnark to verify generic proofs." As this requires modifying the underlying client/server code, this is something we could support and would make our chain unique.
Parity client
This is another "nice to have" feature but would benefit smaller embedded systems a lot.
Parity is an alternative Ethereum client written in Rust which is generally a faster systems level language compared to Go (which is what Geth is written in). Overall, it should use less resources.
Parity is fairly recently released which is why less people use it... But yeah, Geth was an early client.
You can run Parity in "--geth" mode with no issues. It just exposes a compatible communications mechanism that Geth uses.
August 10, 2016, 08:31:44 PM
Jumbucks Ethereum Edition - Alpha 1 released
This can be considered the first "pre-launch" release. We are still in a "Testnet phase" but changes are now in a dedicated Github repository. Expect this network to have several changes before the actual launch. You can participate in Jumbucks Slack in the #jumbucks channel. Testing is going really well with many participants.
You no longer need to specify a Data directory when starting up the server.
If you have an existing keystore, please put that in the new Data directory.
You can find the release here:
https://github.com/jumbucks/go-jumbucksee/releases/tag/v1.4.10-alpha1
Changes
Get a copy of the Jumbucks Testnet Genesis block:
Initialize the Data Directory with the Genesis Block:
Move the boot nodes file into the dedicated data directory.
Start the console and connect to my boot node:
Optionally: Running on a separate console
On one screen:
On another screen:
Binaries (compiled by Julian)
Mac
$ shasum -a 256 gjbsee-darwin-alpha1.tar.gz
14b24aee655053c3f1e6cb125a2eb3ab6a5f65753ddfe89aa67c5fb633513b08 gjbsee-darwin-alpha1.tar.gz
Linux
$ shasum -a 256 gjbsee-linux64-alpha1.tgz
0ef26b9144587a1ee02811f19bcc4b51785cb465337e0b11e3617e0624631565 gjbsee-linux64-alpha1.tgz
This can be considered the first "pre-launch" release. We are still in a "Testnet phase" but changes are now in a dedicated Github repository. Expect this network to have several changes before the actual launch. You can participate in Jumbucks Slack in the #jumbucks channel. Testing is going really well with many participants.
You no longer need to specify a Data directory when starting up the server.
If you have an existing keystore, please put that in the new Data directory.
You can find the release here:
https://github.com/jumbucks/go-jumbucksee/releases/tag/v1.4.10-alpha1
Changes
- Binary has been changed from geth to gjbsee.
- JBS EE now has its own dedicated data directory.
- Mac OS X: ~/Library/JumbucksEE
- Windows: %APPDATA%\JumbucksEE
- Unix: ~/.jumbucksee
- Default TCP port for the HTTP RPC server is now 8588
- Default TCP port for the websocket RPC server is now 8589
- Default (relative) name of the IPC RPC socket is now gjbsee.ipc
Get a copy of the Jumbucks Testnet Genesis block:
Code:
http://getjumbucks.com/download/JumbucksTestnetGenesis.json
Get a copy of the boot nodes:Code:
http://getjumbucks.com/download/static-nodes.json
Initialize the Data Directory with the Genesis Block:
Code:
$ gjbsee init JumbucksTestnetGenesis.json
I0810 12:53:30.229101 ethdb/database.go:82] Alloted 16MB cache and 16 file handles to /Users/julian/Library/JumbucksEE/chaindata
I0810 12:53:30.233218 cmd/gjbsee/main.go:299] successfully wrote genesis block and/or chain rule set: 868d13655a2c47b4b7dd280e4c928870f208d3074875d41c1b6e771a311cbd7f
I0810 12:53:30.229101 ethdb/database.go:82] Alloted 16MB cache and 16 file handles to /Users/julian/Library/JumbucksEE/chaindata
I0810 12:53:30.233218 cmd/gjbsee/main.go:299] successfully wrote genesis block and/or chain rule set: 868d13655a2c47b4b7dd280e4c928870f208d3074875d41c1b6e771a311cbd7f
Move the boot nodes file into the dedicated data directory.
Start the console and connect to my boot node:
Code:
gjbsee console
Optionally: Running on a separate console
On one screen:
Code:
gjbsee
On another screen:
Code:
gjbsee attach ipc:/Users/julian/Library/JumbucksEE/gjbsee.ipc
Binaries (compiled by Julian)
Mac
$ shasum -a 256 gjbsee-darwin-alpha1.tar.gz
14b24aee655053c3f1e6cb125a2eb3ab6a5f65753ddfe89aa67c5fb633513b08 gjbsee-darwin-alpha1.tar.gz
Linux
$ shasum -a 256 gjbsee-linux64-alpha1.tgz
0ef26b9144587a1ee02811f19bcc4b51785cb465337e0b11e3617e0624631565 gjbsee-linux64-alpha1.tgz
August 07, 2016, 07:27:34 AM
Jumbucks Ethereum Edition?
what?
okay i've read page 9, still fuzzy on this point:
- JBS is a very fine POS chain
- JBS EE is a cool idea
- can we have both?
i hope you favor a snap shot; 2 chains.
maybe require signing to claim the JBS EE, but no swap.
what?
okay i've read page 9, still fuzzy on this point:
- JBS is a very fine POS chain
- JBS EE is a cool idea
- can we have both?
i hope you favor a snap shot; 2 chains.
maybe require signing to claim the JBS EE, but no swap.
Sounds nice!
The ticker could be JEDI (Jumbucks Ethereum eDItion)
August 07, 2016, 06:58:34 AM
August 06, 2016, 04:05:35 AM
Jumbucks Ethereum Edition?
what?
okay i've read page 9, still fuzzy on this point:
- JBS is a very fine POS chain
- JBS EE is a cool idea
- can we have both?
i hope you favor a snap shot; 2 chains.
maybe require signing to claim the JBS EE, but no swap.
what?
okay i've read page 9, still fuzzy on this point:
- JBS is a very fine POS chain
- JBS EE is a cool idea
- can we have both?
i hope you favor a snap shot; 2 chains.
maybe require signing to claim the JBS EE, but no swap.
August 06, 2016, 03:18:34 AM
Slowly compiling a list of things to do for the switch to Jumbucks Ethereum Edition.
JBS EE Changes
Change executable name.
Change block time. 1 min or greater. Test this.
Change difficulty adjustment. Test this.
Review further code changes.
Todo
Set up coin swap site and system.
Contact exchanges regarding coin swap.
Ask mining pools to support JBS EE.
Ask mining profitability sites to mention.
Test out and modify Mist graphical wallet. Xocel.
Test out Token contract.
Set up core nodes.
Set up block explorer.
Eventual Todo
New ANN.
New web site.
Contact Coinmarketcap.
Create Slack tip bot.
JBS EE Changes
Change executable name.
Change block time. 1 min or greater. Test this.
Change difficulty adjustment. Test this.
Review further code changes.
Todo
Set up coin swap site and system.
Contact exchanges regarding coin swap.
Ask mining pools to support JBS EE.
Ask mining profitability sites to mention.
Test out and modify Mist graphical wallet. Xocel.
Test out Token contract.
Set up core nodes.
Set up block explorer.
Eventual Todo
New ANN.
New web site.
Contact Coinmarketcap.
Create Slack tip bot.
August 06, 2016, 03:12:07 AM
I have checked the dependencies and i have all the required ones, thank you in advance
Weird that it doesn't work. Works fine for me but I usually compile on Ubuntu 14. Haven't tried an Ubuntu 16 system yet.
August 02, 2016, 04:43:27 AM
Hi all, i am trying to compile jumbucks daemon for run a node, but when i try to compile it fail in main.o, i have checked all dependencies and others daemons compiles without issues, i have tried too from ubuntu 16 and debian 7 and ko, some help is welcomed
Hey mate. Can you post the error message on build?
Thanks Julian
Hi thanks Julian the error i get in the compilation is:
Code:
-DHAVE_BUILD_INFO -fno-stack-protector -fstack-protector-all -Wstack-protector -D_FORTIFY_SOURCE=2 -MMD -MF obj/main.d -o obj/main.o main.cpp
In file included from alert.h:13:0,
from main.cpp:6:
util.h: In function ‘std::string i64tostr(int64_t)’:
util.h:153:69: warning: format ‘%d’ expects argument of type ‘int’, but argument 3 has type ‘int64_t {aka long int}’ [-Wformat=]
#define strprintf(format, ...) real_strprintf(format, 0, __VA_ARGS__)
^
util.h:222:12: note: in expansion of macro ‘strprintf’
return strprintf("%d", n);
^
In file included from checkpoints.h:8:0,
from main.cpp:7:
net.h: In member function ‘void CNode::AskFor(const CInv&)’:
net.h:393:142: warning: format ‘%d’ expects argument of type ‘int’, but argument 3 has type ‘int64_t {aka long int}’ [-Wformat=]
printf("askfor %s %d (%s)\n", inv.ToString().c_str(), nRequestTime, DateTimeStrFormat("%H:%M:%S", nRequestTime/1000000).c_str());
^
In file included from alert.h:13:0,
from main.cpp:6:
main.h: In member function ‘std::string CTransaction::ToString() const’:
util.h:153:69: warning: format ‘%u’ expects argument of type ‘unsigned int’, but argument 6 has type ‘std::vector::size_type {aka long unsigned int}’ [-Wformat=]
#define strprintf(format, ...) real_strprintf(format, 0, __VA_ARGS__)
^
main.h:634:16: note: in expansion of macro ‘strprintf’
str += strprintf("(hash=%s, nTime=%d, ver=%d, vin.size=%u, vout.size=%u, nLockTime=%d)\n",
^
util.h:153:69: warning: format ‘%u’ expects argument of type ‘unsigned int’, but argument 7 has type ‘std::vector::size_type {aka long unsigned int}’ [-Wformat=]
#define strprintf(format, ...) real_strprintf(format, 0, __VA_ARGS__)
^
main.h:634:16: note: in expansion of macro ‘strprintf’
str += strprintf("(hash=%s, nTime=%d, ver=%d, vin.size=%u, vout.size=%u, nLockTime=%d)\n",
^
In file included from db.h:8:0,
from main.cpp:8:
main.h: In member function ‘void CBlock::print() const’:
main.h:1065:67: warning: format ‘%u’ expects argument of type ‘unsigned int’, but argument 9 has type ‘std::vector::size_type {aka long unsigned int}’ [-Wformat=]
HexStr(vchBlockSig.begin(), vchBlockSig.end()).c_str());
^
In file included from alert.h:13:0,
from main.cpp:6:
main.h: In member function ‘std::string CBlockIndex::ToString() const’:
util.h:153:69: warning: format ‘%x’ expects argument of type ‘unsigned int’, but argument 13 has type ‘uint64_t {aka long unsigned int}’ [-Wformat=]
#define strprintf(format, ...) real_strprintf(format, 0, __VA_ARGS__)
^
main.h:1306:16: note: in expansion of macro ‘strprintf’
return strprintf("CBlockIndex(nprev=%p, pnext=%p, nFile=%u, nBlockPos=%-6d nHeight=%d, nMint=%s, nMoneySupply=%s, nFlags=(%s)(%d)(%s), nStakeModifier=%016x, hashProof=%s, prevoutStake=(%s), nStakeTime=%d merkle=%s, hashBlock=%s)",
^
main.cpp: In function ‘bool AddOrphanTx(const CTransaction&)’:
main.cpp:208:110: warning: format ‘%u’ expects argument of type ‘unsigned int’, but argument 2 has type ‘size_t {aka long unsigned int}’ [-Wformat=]
printf("ignoring large orphan tx (size: %u, hash: %s)\n", nSize, hash.ToString().substr(0,10).c_str());
^
main.cpp:217:37: warning: format ‘%u’ expects argument of type ‘unsigned int’, but argument 3 has type ‘std::map::size_type {aka long unsigned int}’ [-Wformat=]
mapOrphanTransactions.size());
^
main.cpp: In member function ‘bool CTxMemPool::accept(CTxDB&, CTransaction&, bool*)’:
main.cpp:651:41: warning: format ‘%d’ expects argument of type ‘int’, but argument 3 has type ‘int64_t {aka long int}’ [-Wformat=]
nFees, txMinFee);
^
main.cpp:651:41: warning: format ‘%d’ expects argument of type ‘int’, but argument 4 has type ‘int64_t {aka long int}’ [-Wformat=]
main.cpp:705:24: warning: format ‘%u’ expects argument of type ‘unsigned int’, but argument 3 has type ‘std::map::size_type {aka long unsigned int}’ [-Wformat=]
mapTx.size());
^
main.cpp: In function ‘int64_t GetProofOfWorkReward(int, int64_t)’:
main.cpp:1004:107: warning: format ‘%d’ expects argument of type ‘int’, but argument 3 has type ‘int64_t {aka long int}’ [-Wformat=]
printf("GetProofOfWorkReward() : create=%s nSubsidy=%d\n", FormatMoney(nSubsidy).c_str(), nSubsidy);
^
main.cpp: In function ‘int64_t GetProofOfStakeReward(int64_t, int64_t, int)’:
main.cpp:1023:107: warning: format ‘%d’ expects argument of type ‘int’, but argument 3 has type ‘int64_t {aka long int}’ [-Wformat=]
printf("GetProofOfStakeReward(): create=%s nCoinAge=%d\n", FormatMoney(nSubsidy).c_str(), nCoinAge);
^
main.cpp:1035:1: error: a function-definition is not allowed here before ‘{’ token
{
^
main.cpp:1028:22: warning: unused variable ‘nTargetTimespan’ [-Wunused-variable]
static const int64_t nTargetTimespan = 16 * 60; // 16 mins
^
main.cpp:3733:5: error: expected ‘}’ at end of input
}
^
main.cpp:3733:5: warning: control reaches end of non-void function [-Wreturn-type]
}
^
main.cpp: At global scope:
main.cpp:110:13: warning: ‘bool GetTransaction(const uint256&, CWalletTx&)’ defined but not used [-Wunused-function]
bool static GetTransaction(const uint256& hashTx, CWalletTx& wtx)
^
main.cpp:145:13: warning: ‘void SetBestChain(const CBlockLocator&)’ defined but not used [-Wunused-function]
void static SetBestChain(const CBlockLocator& loc)
^
main.cpp:152:13: warning: ‘void UpdatedTransaction(const uint256&)’ defined but not used [-Wunused-function]
void static UpdatedTransaction(const uint256& hashTx)
^
main.cpp:159:13: warning: ‘void PrintWallets(const CBlock&)’ defined but not used [-Wunused-function]
void static PrintWallets(const CBlock& block)
^
main.cpp:166:13: warning: ‘void Inventory(const uint256&)’ defined but not used [-Wunused-function]
void static Inventory(const uint256& hash)
^
main.cpp:972:16: warning: ‘uint256 GetOrphanRoot(const CBlock*)’ defined but not used [-Wunused-function]
uint256 static GetOrphanRoot(const CBlock* pblock)
^
make: *** [obj/main.o] Error 1
In file included from alert.h:13:0,
from main.cpp:6:
util.h: In function ‘std::string i64tostr(int64_t)’:
util.h:153:69: warning: format ‘%d’ expects argument of type ‘int’, but argument 3 has type ‘int64_t {aka long int}’ [-Wformat=]
#define strprintf(format, ...) real_strprintf(format, 0, __VA_ARGS__)
^
util.h:222:12: note: in expansion of macro ‘strprintf’
return strprintf("%d", n);
^
In file included from checkpoints.h:8:0,
from main.cpp:7:
net.h: In member function ‘void CNode::AskFor(const CInv&)’:
net.h:393:142: warning: format ‘%d’ expects argument of type ‘int’, but argument 3 has type ‘int64_t {aka long int}’ [-Wformat=]
printf("askfor %s %d (%s)\n", inv.ToString().c_str(), nRequestTime, DateTimeStrFormat("%H:%M:%S", nRequestTime/1000000).c_str());
^
In file included from alert.h:13:0,
from main.cpp:6:
main.h: In member function ‘std::string CTransaction::ToString() const’:
util.h:153:69: warning: format ‘%u’ expects argument of type ‘unsigned int’, but argument 6 has type ‘std::vector
#define strprintf(format, ...) real_strprintf(format, 0, __VA_ARGS__)
^
main.h:634:16: note: in expansion of macro ‘strprintf’
str += strprintf("(hash=%s, nTime=%d, ver=%d, vin.size=%u, vout.size=%u, nLockTime=%d)\n",
^
util.h:153:69: warning: format ‘%u’ expects argument of type ‘unsigned int’, but argument 7 has type ‘std::vector
#define strprintf(format, ...) real_strprintf(format, 0, __VA_ARGS__)
^
main.h:634:16: note: in expansion of macro ‘strprintf’
str += strprintf("(hash=%s, nTime=%d, ver=%d, vin.size=%u, vout.size=%u, nLockTime=%d)\n",
^
In file included from db.h:8:0,
from main.cpp:8:
main.h: In member function ‘void CBlock::print() const’:
main.h:1065:67: warning: format ‘%u’ expects argument of type ‘unsigned int’, but argument 9 has type ‘std::vector
HexStr(vchBlockSig.begin(), vchBlockSig.end()).c_str());
^
In file included from alert.h:13:0,
from main.cpp:6:
main.h: In member function ‘std::string CBlockIndex::ToString() const’:
util.h:153:69: warning: format ‘%x’ expects argument of type ‘unsigned int’, but argument 13 has type ‘uint64_t {aka long unsigned int}’ [-Wformat=]
#define strprintf(format, ...) real_strprintf(format, 0, __VA_ARGS__)
^
main.h:1306:16: note: in expansion of macro ‘strprintf’
return strprintf("CBlockIndex(nprev=%p, pnext=%p, nFile=%u, nBlockPos=%-6d nHeight=%d, nMint=%s, nMoneySupply=%s, nFlags=(%s)(%d)(%s), nStakeModifier=%016x, hashProof=%s, prevoutStake=(%s), nStakeTime=%d merkle=%s, hashBlock=%s)",
^
main.cpp: In function ‘bool AddOrphanTx(const CTransaction&)’:
main.cpp:208:110: warning: format ‘%u’ expects argument of type ‘unsigned int’, but argument 2 has type ‘size_t {aka long unsigned int}’ [-Wformat=]
printf("ignoring large orphan tx (size: %u, hash: %s)\n", nSize, hash.ToString().substr(0,10).c_str());
^
main.cpp:217:37: warning: format ‘%u’ expects argument of type ‘unsigned int’, but argument 3 has type ‘std::map
mapOrphanTransactions.size());
^
main.cpp: In member function ‘bool CTxMemPool::accept(CTxDB&, CTransaction&, bool*)’:
main.cpp:651:41: warning: format ‘%d’ expects argument of type ‘int’, but argument 3 has type ‘int64_t {aka long int}’ [-Wformat=]
nFees, txMinFee);
^
main.cpp:651:41: warning: format ‘%d’ expects argument of type ‘int’, but argument 4 has type ‘int64_t {aka long int}’ [-Wformat=]
main.cpp:705:24: warning: format ‘%u’ expects argument of type ‘unsigned int’, but argument 3 has type ‘std::map
mapTx.size());
^
main.cpp: In function ‘int64_t GetProofOfWorkReward(int, int64_t)’:
main.cpp:1004:107: warning: format ‘%d’ expects argument of type ‘int’, but argument 3 has type ‘int64_t {aka long int}’ [-Wformat=]
printf("GetProofOfWorkReward() : create=%s nSubsidy=%d\n", FormatMoney(nSubsidy).c_str(), nSubsidy);
^
main.cpp: In function ‘int64_t GetProofOfStakeReward(int64_t, int64_t, int)’:
main.cpp:1023:107: warning: format ‘%d’ expects argument of type ‘int’, but argument 3 has type ‘int64_t {aka long int}’ [-Wformat=]
printf("GetProofOfStakeReward(): create=%s nCoinAge=%d\n", FormatMoney(nSubsidy).c_str(), nCoinAge);
^
main.cpp:1035:1: error: a function-definition is not allowed here before ‘{’ token
{
^
main.cpp:1028:22: warning: unused variable ‘nTargetTimespan’ [-Wunused-variable]
static const int64_t nTargetTimespan = 16 * 60; // 16 mins
^
main.cpp:3733:5: error: expected ‘}’ at end of input
}
^
main.cpp:3733:5: warning: control reaches end of non-void function [-Wreturn-type]
}
^
main.cpp: At global scope:
main.cpp:110:13: warning: ‘bool GetTransaction(const uint256&, CWalletTx&)’ defined but not used [-Wunused-function]
bool static GetTransaction(const uint256& hashTx, CWalletTx& wtx)
^
main.cpp:145:13: warning: ‘void SetBestChain(const CBlockLocator&)’ defined but not used [-Wunused-function]
void static SetBestChain(const CBlockLocator& loc)
^
main.cpp:152:13: warning: ‘void UpdatedTransaction(const uint256&)’ defined but not used [-Wunused-function]
void static UpdatedTransaction(const uint256& hashTx)
^
main.cpp:159:13: warning: ‘void PrintWallets(const CBlock&)’ defined but not used [-Wunused-function]
void static PrintWallets(const CBlock& block)
^
main.cpp:166:13: warning: ‘void Inventory(const uint256&)’ defined but not used [-Wunused-function]
void static Inventory(const uint256& hash)
^
main.cpp:972:16: warning: ‘uint256 GetOrphanRoot(const CBlock*)’ defined but not used [-Wunused-function]
uint256 static GetOrphanRoot(const CBlock* pblock)
^
make: *** [obj/main.o] Error 1
I have checked the dependencies and i have all the required ones, thank you in advance
Jump to: