Windows 10 is likely going to be the reason I finally switch entirely over to linux.
I couldn't agree more. It literally might be the worse release of windows ever IMHO. I have disabled runtime broker and cortonna and they still seem to eat up resources to the point where windows shows me a popup that asks would I like to shut them down :-) "YES I would like to shut them down PERMANENTLY" :-) I would also like to quit Windows 10. Question: If one were to switch from Windows 10 to Ubuntu, would the same wallet.dat work with the new Linux wallet? Could one also bring the Blockchain into the new wallet and have it work correctly? Thanks in advance. It's worked for me, with several other coins. Never tried verge, but can't see why not... |
|
|
|
O.K HUBBY GOT A JOB AND WE ARE MOVING TODAY WE HAD FEW HOURS NOTICE LOL AND MOVING TOWN I WILL BE IN A SMALL B AND B FOR FEW DAYS LOOKING FOR A PLKACE FOR US TO LIVE SO I WILL BE BUSY FOR A FEW DAYS, I WILL KEEP U POSTED WHEN I CAN DO BAGBONUS AS EARLY AS P[OSS..
BLESSINGS
ELLIE
Congratulations, and good luck on finding the new place. |
|
|
|
AHHH, I was waiting for the trolls. Did you somehow just show his DogeD posts, or is that all he trolls.... Get a life... |
|
|
|
|
Just throwing this out there. Will cointopay be supporting VERGE? Have they been contacted? They used to handle DogeD. Seems like a good way to get VERGE accepted at more retailers.
|
|
|
|
|
I don't use Twitter, but someone should tweet poloniex and specifically mention the volume.... 200BTC is crazy... That the only thing they care about.
|
|
|
|
If your running on windows, and you had dogeD installed and synced, you can just delete everything in the appdata/roaming verge directory, and copy everything from the doged directory. Then you don't have to sync. It worked for me.
Thanks Chilly! Worked like a champ. Only thing I did was change the conf file name to VergeCoin.conf Also sent 500 coins as a test to bittrex BEFORE I downloaded and installed new Verge wallet. Coins made it no problem. I've never seen a Dev on the ball like this one. This whole change thing had me a little concerned but WOW.....just WOW. Kudos and applause! Glad to hear it worked for you. When you mentioned the conf file I had to go check, because I didn't remember changing it. I never created one for dogeDark, or Verge, they both just worked "out of the box". And yea I agree, good job Dev... |
|
|
|
Can't seem to properly sync the VERGE windows wallet. Are the addnodes the same as with DOGED? or is there womething new I should be putting in the conf file? also would it be VERGE.conf, verge.conf, vergecoin.conf???
stuck on block 48771
it's probably syncing. if you show connections, you're good to go. for some reason the spinnder syncing icon isnt showing up, but if u hover just below connections you should see the progress. Ya, ive read earlier in the thread that I just hover where it should be, but after doing that, multiple hours apart, its still at block no 48771 (or 20.28%) If your running on windows, and you had dogeD installed and synced, you can just delete everything in the appdata/roaming verge directory, and copy everything from the doged directory. Then you don't have to sync. It worked for me. |
|
|
|
|
Not sure why Verge is on your list. Care to elaborate?
|
|
|
|
|
Well it looks like things are starting on Bittrex. DogeD had a banner saying wallet maintenance, and there is no longer a listing in the BTC markets. I'm assuming step 2 is to rename it Verge.
|
|
|
|
I'm jumping late in here but I've been talking to the dev and want to sum of what I told him:
We charge for swaps and renames for 2 reasons...
1) its very time intensive to do these renames/swaps. For better or worse, that is how the system is designed. Its purposefully difficult to change anything in the system that messes with audit ability.
2) for a while we had people "rescuing" old coins and "rebranding" them for nefarious purpose. The fee was implemented to slow that down.
We implemented a policy that any renames/swaps would incur a fee. I just had to charge the LIMX folks for the same thing today, and thats after they paid for a spotlight to get listed.
For me to waive anything would be unfair to the other coins that we have forced to do this. The best i can do is reduce the fee to 1.5 ... If you choose not to go that route, I'll be happy to close the market and let people withdraw and we will re-evaluate the re-listing of XVG after we close down DOGED.
thanks
richie@bittrex
I'm sure Poloniex would make the right decision here. Is Bittrex seriously making a fairness argument when DOGED takes in so much in fees? Bittrex, ever heard of "Don't bite the hand that feeds you"? Bittrex just lost a customer if they don't waive this fee. Spend those funds on hosting DogedDev! I kind of thought the same thing. How dare they do that. Especially since the volume is high now. Doged (Verge) is really starting to take off, and they are making a ton in fee's. That was until I did the math. Lets use the latest 20 BTC volume a day. 20 * .0025 = .05 BTC * 410 USD = $20.5 a day. And that's with the latest volume. Would you take on all of the risks and headaches running an exchange for $20 a day? |
|
|
|
I know some of that dumping was caused by myself.... used the clams as collateral to short other coins. got called so clams got dumped. Wasn't intended..
Part of the exposure having clams margin traded, and able to be used as collateral on Poloniex.
That's very interesting. It hadn't occurred to me that dumping could happen accidentally, as a result of a collateralized loan going bad. So let's say you were shorting ETH using CLAM as collateral. That means you borrowed some ETH on the lending market and then sold it for BTC, hoping for the price to drop. When the price continued to increase your CLAM was automatically dumped for BTC, and that BTC was used together with the BTC from selling the ETH to buy back the ETH at the new higher price, and then the loan was repaid. So the lender gets his ETH back plus a little interest. You're out all your CLAM. So where did the value you lost go to? Other than the lender making a little interest, and the exchange making a little in fees, I guess the rest of your value ended up with ETH traders who bought cheap from you and sold back higher when you got margin called. I find the mechanism both interesting and confusing. But also offtopic here I guess. So I'll shut up about it.  That's exactly how it works. I didn't lose all my clams but most of what I risked. I still had about 20% of my collateral after it was all done. Polo did a pretty good job keeping track of everything. They have to account for multiple trades at the same time, IE they need to sell assets over several buy orders at different price. At least I can lick my wounds and chalk it up to a learning experience. |
|
|
|
|
I know some of that dumping was caused by myself.... used the clams as collateral to short other coins. got called so clams got dumped. Wasn't intended..
Part of the exposure having clams margin traded, and able to be used as collateral on Poloniex.
|
|
|
|
Looking forward to the rebrand.  thanks! launches monday =] 8 sats are getting eaten on bittrex. Like it. 8's gone, on to 9. |
|
|
|
someone help me to program this sequences..
bet 1 lose
bet 2 lose
switch
bet 3 lose
bet 4 lose
switch
bet 5 lose
switch
bet 6
only until bet 6
thanks
Not sure what your trying to do, but that's easy. losscount = 0 if(win) then losscount = 0 else losscount += 1 if(losscount == 2 or losscount == 4 or losscount == 5) then bethigh = !bethigh end if (losscount == 6) then "do something else" losscount = 0 end end So you setup and initialize a variable called losscount (That's just a name I picked) Then each time you lose, increment losscount by 1. if it equals 2 4 or 5 then switch the bethigh variable. if it equals 6 do something else, like reset your bet, and reset losscount so you start again. If you win you need to reset losscount, otherwise it will accumulate. |
|
|
|
hey guys, im currently at the hospital, me and my girl are having our baby! hopefully you forgive me if i am not around to answer questions today and tomorrow! (community members feel free to answer peoples questions to the best of your ability) ill do my best to check in here later tonight. i've got a ton of the verge stuff already up and running.. and ill be back to work here in 2-3 days tops  Congratulations, Enjoy the moment and don't worry about us.... |
|
|
|
with such a hi inflation rate i would expect my wallet to have staked by now. 90000 hyps in about 35 blocks of sizes from 800 - 4500 kind of randomly.
so how do i know it is set up right?
it's been sittin there 2 weeks
I would put it into 9 blocks of 10K each. or maybe 10 blocks of 9K. Either way with so few I found it better to have bigger blocks and stake more reliably. Once your up to around 250 - 300 K you can start lowering the block size to get more staking because of the randomness. I've got around 500K and set my stakesplitthreshold to 5000, which means my blocks are between 2500 - 5000. I'm averaging a few stakes per day from 0 - 6 a day in the last week. That's just how things seemed to work best for me. Play around with setting up different block sizes, and check the block explore to see what size blocks are staking. Anything less then 1K would be like hitting the lottery. 1K-2K is a little harder, and your 2K - 4.5K are more likely to hit. But it's still very random. in the past 2 weeks I've had a 1.8K block hit and several in the 2.8K range, the rest were in the 3-5K range. And I still have a 3K block sitting at 200 days old. |
|
|
|
|
Did something change on BetKing? I was in the middle of running a script and the bot froze. Tried restarting it, and get the message tried bet 3 times, check network and settings.
I reset my modem, restarted the bot several times, rebooted the PC, and even deleted the app data folder.
I can log into JD and place a bet, but on betking, I can log in OK, but my stats and balance are all zero. I have a feeling Dean changed something and broke the bot, as I think the site was down for maintenance a short while before this happened.
Thanks
|
|
|
|
How is this dev.
This guy has been in so many coins and even more scams then you can count on 1 hand.
I think you answered your own question. |
|
|
|
#!/usr/bin/env python
import random, string, time
def rand():
return start_date + random.random() * (end_date - start_date)
def fmt(seconds):
return '[%s]' % time.ctime(seconds)
def find(seconds):
last = None
for sec in times:
if sec < seconds:
return sec, last
last = sec
datfile = "clamblocks.dat"
count = 0
lines = 100000
samples = 100000
times = []
fp = open(datfile, "r")
while True:
line = fp.readline()
if not line:
break
line = string.split(line[:-1])
times.append(string.atoi(line[5]))
count += 1
if (count == lines):
break
start_date = times[-1]
end_date = times[0]
print "picking random dates between %s and %s" % (fmt(start_date), fmt(end_date))
before_sum = 0
after_sum = 0
count = 0
while True:
t = rand()
before, after = find(t)
before_sum += t - before
after_sum += after - t
count += 1
if count % 1000 == 0:
print ("(%6d) %s is %6.2f seconds after %s (%6.2f) and %6.2f seconds after %s (%6.2f)" %
(count,
fmt(t),
t - before, fmt(before), before_sum / count,
after - t, fmt(after), after_sum / count))
I'm not a python programmer, but in the find routine, it looks like your returning the newer block, and then the older block. but in the main routine, your looking for the older block then the newer block. Have you tried running the code with a small subset, just so you can manually verify the output. I would expect the averages to be 1/2 the block time. Maybe I don't know what I'm talking about.... (Won't be the first time) |
|
|
|
What is "average block time"? Suppose blocks were found every minute, at the top of the minute, and my random point is 30 seconds past the minute. It's 30 seconds since the last block and 30 seconds to the next block. The time between blocks is 30+30. ie. A+B=C I did mean for A to be the expected time to the next block (ie. 1 minute), not the time of the next block (ie. Tuesday at 12:34 or whatever). A, B, and C are all 60 seconds. A) From a random point in time we all agree that the expected time to the next block is 60 seconds. I don't think anyone's going to argue with that (except that we find blocks a little too fast, so it's actually 59 seconds or something, but let's ignore that. B) I don't think anyone can really make a reasonable argument that the same isn't true about the expected time to the previous block. Just record the block creation process happening and play it backwards. It's indistinguishable from playing it forwards. Like smooth's sliding paper revealing the blocks. You can slide in either direction and the expect time to the 'next' block (which is the 'previous' one when sliding backwards) is 60 seconds. C) Can anyone argue that the expected time between blocks is not 60 seconds? I put it to you that A, B, and C are ALL equal to 60 seconds, and that this isn't a contradition. There is a rational explanation for this. I just like to make people figure it out for themselves -- dooglus the deceiver I guess I still don't get it. If I just pick a random time, IE not when a block is found. And not knowing when the last block was found, I can only estimate that the next block will be found in less then 60 seconds (based on a 1 minute block time average). And the same with the previous block less then 60 seconds assuming the time I choose is not exactly on a block found time. Your example 30 + 30 = 60 (or 1 minute) Makes sense. But 1+1 = 1 doesn't. I can almost see a) if nothing else is know and you select a time, then a block should be found within 1 minute. But it's not a fact that, "If you select a random time the next block will be found in 1 minute". If you change in to within, then I buy it. Same for B. I'm sure I'm just taking this to literal.... |
|
|
|
|
Show Posts
