 Show Posts
|
|
Pages: [1] 2 »
|
Got a few for ya!  25485e02584a1a0262e6735a3e461347ba28473a181f58b382253f887e92dc83
5af604eed0b6f8ab79a3fe27fad079669b4009cfb25dc52369dfa5783fdcae04
e81f09db10d754787f85be839cb162518250fd397dafe31f17215d0c4f5e3202
cdb657f8fdb9f7058dd208dca9db254adf39a30d9c660801777b618acf72a359
a66b3950ea19a0d2f13fa8887ee46d64af830be0eb33055863af5976e69eda00
aba533e1fc3406302b79ef6ada5ca05db27dd5c031260a017bc1e7c2ee9c2e4f
e2b02233ef434cb26db4f76751e7ca04a4f6b808fe990cd2c13ff50bae4ef58c
dc4f65c0bd69ef044e305d7b1fbda86879f7f8e5e1e42bad147f658fc3fd6f31
b365fc5a2c34e6975c40b8a642c7ad9affb1efbe1534f4d2d5d2f8b976c247ce
34ee8ce5b575d1727a75116d07957ba650d11e5d7b2c2d1d1353c5c369eb7d4c
|
|
|
|
|
Red Entry for me, I'll be on 1999x71r5uEKMXfkibCBaHkMS39sSnzzef.
|
|
|
|
|
1999x71r5uEKMXfkibCBaHkMS39sSnzzef
I'm in!
|
|
|
|
|
Put me in again coach
1999x71r5uEKMXfkibCBaHkMS39sSnzzef
|
|
|
|
|
I'm in, register me! 1999x71r5uEKMXfkibCBaHkMS39sSnzzef
|
|
|
|
Was thinking the other day how it might be interesting to move the 999 around in red, so here's a few submissions revolving around that idea. Multipliers: (center to extreme)
---------------------------------------------------
0.1 0.1 0.1 0.1 1.8 9 24 999 2000
---------------------------------------------------
Max amount playable: 0.05
--
Odds: 98.282%
Max win: 100.00 BTC
Name: ?
Bitcoin Address: 1999x71r5uEKMXfkibCBaHkMS39sSnzzef
Multipliers: (center to extreme)
---------------------------------------------------
0.1 0.1 0.1 0.1 2.65 9 27 999 130
---------------------------------------------------
Max amount playable: 0.1
--
Odds: 98.395%
Max win: 99.90 BTC
Name: ?
Bitcoin Address: 1999x71r5uEKMXfkibCBaHkMS39sSnzzef
|
|
|
|
That's one of the seed nodes with over 120 connections
OK, so how do we fix this issue, the debug log says 14 seed nodes loaded but the only one it will connect to is the bad one. Is that preventing my wallet from connecting to others. How do we get others to connect. I haven't tried it, but could the banscore setting be used to tell our clients to avoid it instead of failing 100 times? -banscore=<n> Threshold for disconnecting misbehaving peers (default: 100) |
|
|
|
I am now having issues with the wallet and I need some help please.
I was running with 4 connections on 1 machine and 3 on the other fine, staked 6 different times, got 2 or 3 confirms for all, then they disappeared and I lost my peer connections on both machines.
I have tried rebooting both of my machines, running with and without .conf file, flushng and resetting my network stack.
The only peer I can connect to is this one even when using GoillaBucks.conf with 8 or so peers from this thread, but it will not sync:
[
{
"addr" : "23.92.61.98:36480",
"services" : "00000000",
"lastsend" : 1435651618,
"lastrecv" : 0,
"bytessent" : 129,
"bytesrecv" : 0,
"conntime" : 1435651618,
"pingtime" : 0.00000000,
"version" : 0,
"subver" : "",
"inbound" : false,
"startingheight" : -1,
"banscore" : 0,
"syncnode" : false
}
]
This is happening on 2 seperate wallets running on 2 different machines and connected through 2 different ISP connections.
None of my other wallets, or any wallets from MMXIV, Teeth, Balls, 10K, Vary, Original Bucks have had this problem.
What do I do to fix this? What is different about this coin than any other wallet?
All other wallets connected to 8 peers each without any problem.
Please help as I am losiing a lot of stakes while I cannot connect.
As I was typing this I now have 0 connections
Same thing here. Spots, or anyone else can you help us out please All the other coins worked fine, MMXIV, VARY, TEETH, BUCKS. Full connections, always synced. This one is always connecting to node 23.92.61.98:36480 which is a bad boy, always missbehaving: Misbehaving: 23.92.61.98:36480 (0 -> 1)
ProcessMessage(dsee, 253 bytes) FAILED
Misbehaving: 23.92.61.98:36480 (1 -> 2)
ProcessMessage(dsee, 253 bytes) FAILED Same problem here, if the wallet can connect to 1 peer it should be able to connect to others. Pinging the other peers works so they are there. I am receiving the same error. Misbehaving: 23.92.61.98:36480 (0 -> 1)
ProcessMessage(dsee, 253 bytes) FAILED
Misbehaving: 23.92.61.98:36480 (1 -> 2)
ProcessMessage(dsee, 253 bytes) FAILED I've seen a lot of that too, I'm not sure who that node is but it seems bad. |
|
|
|
First and foremost, do I need the conf file as seen in my last reply at all with the whole one click set up ?
I didn't get that part either, I'm using a config file. My config file looks exactly like yours except has a bunch of the addnode flags that I put in the beginning when I couldn't sync up with anyone. Some things to note: - When you click "Start" on the GorillaBand, it says something about Adreneline Node started with your IP. - The status column under "My GorillaBands" never actually says anything, it's always empty. - My GorillaBands show up on the GorillaBand network tab and the active timers work. - I have my GorillaBands unlocked for staking, I think that might be required, would like to know but it's working. |
|
|
|
Screw it, I can't sleep because this is bugging the piss outa me since I seem to be sitting on 10k between two bands doing nothing. I assume the one click config mentioned on the site is what otherwise eliminates the need for the conf file. That being said, if I removed the listed band from the band tab and opt for a conf file alone, will I (if I'm lucky) still have a running band ? That being said, here's what one bands conf file looks like, it's all otherwise visible info from the band tab with the exception to the <removed> priv key which I assume is that of the 5k band address. rpcallowip=127.0.0.1
rpcuser=<removed>
rpcpassword=<removed>
rpcport=11839
staking=0
server=1
listen=1
port=11838
masternode=1
masternodeaddr=24.154.55.93:11838
masternodeprivkey=<removed>
I don't see you in the network list. Have you looked at the debug.log in your GorillaBucks folder? That might shed some insight into the problem. I ended up having to do some work on my router and forward the ports to the appropriate machine before things started working (apparently UPNP wasn't working). |
|
|
|
I see we are already approaching 50 GorillaBand Masternodes. That's nearly 25% of the entire coin supply not even trying to sell  Only 12k bucks on the exchange as well, that's only enough for 2 more masternodes |
|
|
|
Where should conf go - in GorillaBucks raoming?
Yep, as GorillaBucks.conf |
|
|
|
|
So I've hit a snag while transferring my 10k.
I had over 4.2bn 10k, and only managed to transfer about 2.4bn of them over to the exchange for the swap. If I look on one of the block explorers, it shows the remaining 1.8bn coins on the address, however it doesn't show in the wallet.
I've run repairwallet to no avail. I've also tried re-downloading the client and blockchain, then importing the private key into a clean wallet. Both my old wallet and new wallet show the same balance though, of 79m, short about 1.79bn.
Any advice on how to get these coins loaded up into a wallet so I can transfer?
|
|
|
|
My point is that if anyone were to buy the level 2 miner or higher, it will by default be a signature miner because it will require more than 1% of the coin supply to purchase. So I am trying to figure out if the purchaser of 1% of the coins or higher will only be able to take advantage of this benefit if and only if they purchased within the ICO time period.
As one of the few addresses that holds more than 1%, I'd like some clarification on this in general. From one of the previous posts it sounds like the signature miner is still in development and happening (it was mentioned it had a 25% more performance?). I'd just like to know whether or not I'm getting one for being an early adopter of the project. I realize that the ICO didn't sell out or even hit the 50% mark, so I'm not going to be upset and I'll understand if the 1% holders WON'T be getting a free device. But I'll be incredibly happy if it still happens. I'd just like to know either way and know what I need to do to prove my ownership and purchase during the ICO. And no matter what, my CHASH is going to purchase one of the first few devices released  |
|
|
|
Nice one's flux! Decided to play with a few of my own, nice job on using a fiddle and writing a small script to generate these! Hope my bet generator had a hand in inspiring that Multipliers: (center to extreme)
---------------------------------------------------
0.2 0.2 0.2 0.2 0.2 0.2 1 975 9999
---------------------------------------------------
Max amount playable: 0.005
--
Odds: 98.405%
Max win: 49.995000000000005 BTC
Name: Over 9000
Color: Orange (Fiery!)
Bitcoin Address: 1JAdRaNqgYg5Eppkey1HcTuoTaR35EJAGw
The above lines are designed to play with "raining" bets, you barely ever get your bet back.. but if you hit the outer two rings you hit big. I also really wanted to see a number that just dwarfs the 999 on the current boards! Screw winning x999, lets do x9999! Multipliers: (center to extreme)
---------------------------------------------------
0.2 0.2 0.4 0.65 1.22 9 77 333 777
---------------------------------------------------
Max amount playable: 0.065
--
Odds: 98.336%
Max win: 50.505 BTC
Name: Lucky 777's
Bitcoin Address: 1JAdRaNqgYg5Eppkey1HcTuoTaR35EJAGw
7's are lucky right? Multipliers: (center to extreme)
---------------------------------------------------
0.2 0.2 0.5 1.25 3 10 45 99 1111
---------------------------------------------------
Max amount playable: 0.045
--
Odds: 98.248%
Max win: 49.995 BTC
Name: Buncha Ones
Bitcoin Address: 1JAdRaNqgYg5Eppkey1HcTuoTaR35EJAGw
A little bit more harsh than our current red line, with a little sweeter reward on the far outside pay lines. Multipliers: (center to extreme)
---------------------------------------------------
2.5 0.2 0.2 0.2 0.25 2.5 25 250 2500
---------------------------------------------------
Max amount playable: 0.02
--
Odds: 98.284%
Max win: 50 BTC
Name: Two and a half chips
Bitcoin Address: 1JAdRaNqgYg5Eppkey1HcTuoTaR35EJAGw
And the last one, which I was just trying to revolve around the number 25 and variants of. |
|
|
|
How many HASH is in supply?
I think it was somewhere between 120k-130k, don't remember the exact figure. |
|
|
|
|
@CleverHash - So, any more information regarding the 1%/5%/10%/etc holders? Is there still a free signature miner for those who hold 1%?
|
|
|
|
Oh, this is sweeter than a sugar cookie with icing dunked in syrup.  Tipped ya 0.005 for this and I will be using it. Wishlist: * Toggle for the satoshi-organizer addition. Personally I don't care if my bets get mixed up and I'd rather not burn a satoshi or ten. * Items in the list box should toggle rather than standard list box behavior (hold CTRL). * Put the stuff that appears below the button in a second column. * Sanity checking: Limit 150 bets, and minimum 0.001 bet. Maximum bets would be a nightmare with the randomizer. * Reset form button. Appreciate the tip! Spending a bit more free time today to clean it up a little bit. Here's the updated link with the newer version: http://jsfiddle.net/jadra/brt5kjdL/14/embedded/result/- Removed the promo line from the bet options
- You can now toggle on/off the bid incrementer. It's used to attempt to maintain bet order during a rain if you're trying to create fill the board with different colors.
- There's a "Total Amount" display that shows the total amount of the bet right above the copy/paste area.
- The address selection is now checkboxes instead of a multi-select. Should be easier to use.
- The script won't generate bets under 0.001 anymore and 500 is the limit for bets.
- Anytime an error is encountered, the CSV output data is cleared until the error is fixed.
- I've cleaned up the styles a little bit so it's a bit nicer looking.
Still planning on finding a more permanent home for the project, but JSFiddle will do for now |
|
|
|
I started working on a small script to generate "rain" bets using Electrum's "Create Transaction from CSV Text" feature. It's a working prototype, the code isn't great, but it's a solid concept to start with. You can find the CSV Generator here: http://jsfiddle.net/jadra/brt5kjdL/6/embedded/result/(JSFiddle.net is a free CSS/HTML/JS code sharing tool - this entire tool is just a web page and doesn't interact with anything except your browser) It works with Electrum wallets right now, you can click "Create Transaction", then "From CSV Text" and paste the CSV it generates into the box to generate a bet of your choice. Right now it has the following features: - Lets you pick one or more color to bet on. It randomly picks from what you pick for each bet it generates.
- Lets you choose how many bets the rain will be.
- Gives you the choice of different bet types, the two so far are:
- All Bets of Equal Value - Every bet it generates is the same value (+0.00000001 to each bet, to try and maintain the sequence of the bets)
- Bets between X/Y - Lets you pick a minimum and maximum value, all bets will fall between these two value ranges at random.
- Randomize Button to re-randomize the CSV to randomly create a new sequence.
Please note, this script is about 2 hours old and may contain bugs. Please REVIEW THE CSV BEFORE YOU BET to ensure that there are no bets you do not wish to place. I take no responsibility for any errors you may encounter, but I will do my best to fix them! The CSV itself is formatted as such: DESTINATIONADDRESS, BETAMOUNT (one bet per line) DESTINATIONADDRESS, BETAMOUNT (one bet per line) DESTINATIONADDRESS, BETAMOUNT (one bet per line) DESTINATIONADDRESS, BETAMOUNT (one bet per line) The code is also available on jsfiddle here: http://jsfiddle.net/jadra/brt5kjdL/6/Happy 1-year Luckyb.it! You're a great site with a great community and one of the best social gaming platforms I've seen. |
|
|
|
|
