Search results

This is pretty disappointing to read. I agree the one thing we haven't done well is keep a place for all of this type of info to be correlated for the people who don't have time to read all the forum posts so let me try and just touch on a few things that get me hot and bothered (and moli as...

Thanks for doing this moli! At the current time I try to keep an entire set of infrastructure up and dedicated to testnet. I have been doing this for over a year and many people have benefited from these resources. I have at one time or currently hosted the following for testnet: Abe Block...

What price are you wanting for them? Are you only willing to sell them all or would you part with a few to different people?

I think there is a string overflowing on the automated backup... See screen shot...

The point is that we want to be respectful to the external people using our wallets. Exchanges, API systems, anything like that that requires specific expected results should be able to easily find what's changed so they can update their code. It takes a bunch of time for them to make those...

So I guess we still have a centralization issue that only evan can turn on or off enforcement. We did have an issue once where we got stuck on a block and had no blocks for many hours until someone reached evan to turn off enforcement. I guess we should circle around and chat about how this...

Best submit your concerns here: https://github.com/dashpay/dash/issues

Yeah totally agreed any major changes that will break a production server or need to be handled differently that will break code should definitely be pointed out.

Nothing bring's me warm fuzzies a week before desired launch like the words "I hope" and "maybe"...

I think I got most of the spam moli...thanks for hte ping.

Status: 9 confirmations (verified via instantx), broadcast through 8 nodes Date: 7/27/2015 08:22 To: y9TqsvUd4uQKCjcK4RF1qpBGA2GeUP2JTg Debit: -100.00000000 tDASHTransaction fee: -0.01000000 tDASH Net amount: -100.01000000 tDASH Transaction ID...

Seems like some of my wallet transactions are showing as "Conflicted". Not really sure but that probably explains why it seems like there should be 8k tdash but maybe they aren't all actually there cause some are conflicted tx's? Status: conflicted Date: 7/27/2015 03:14 From: unknownTo...

Double dog dare you.

Look at the date stamps on my sends??? 08/06 then 07/27? How is that even possible? I was seeing weird stuff like that with DS+ too as I was mixing my collateral payments were all showing with the 07/27 date stamp.

I think my coins were just more mature? I mean I'm more mature? LOL When I went to any value above 100 though I started getting that error even though the wallet still has 8k coins that all have 100+ confirms?

IX is insanely faaaaaaaaaaaaast holy crap!

lol who me??? haha yeah 10's coming next then 100's then 999's

Looking through the console I see this: Arguments: 1. "dashaddress" (string, required) The dash address to send to. 2. "amount" (numeric, required) The amount in btc to send. eg 0.1 3. "comment" (string, optional) A comment used to store what the transaction is for. "The amount in btc to send"

I don't find that in my logs here on local windows wallet. evan82@klaus:~/.dash/testnet3$ cat debug.log | grep "invalid finalized budget" evan82@klaus:~/.dash/testnet3$ Nothing on klaus either.

Left my v38 wallet mixing over night. Came back to a crashed qt. This is windows 10 using the 64bit wallet.