Topic: [DVC]DevCoin - Official Thread - Moderated - page 286. (Read 1058956 times)

Hey Markm,

Vircurex's API is horrible...and it's made even worse by their incalculable need to release every order after it's been created.

As a side note they also only let you have 100 open positions at any one time (according to their API page), which means you could only really have 100 santoshis difference between the lowest and highest prices, and if you're creating buy as well as sell orders, it's only really 50 santoshis either way. Seeing as you've put in lots of orders already, does this mean you have hundreds/thousands of open orders on vircurex? Also, is it more important for you to set the price in 1 santoshi increments, or set the range (eg 50-350 santoshis) with it working out the increments itself?

If you think the most useful tool would be a 100 santoshi range finder, what I'm imagining is something like this:


enter first currency
enter second currency
enter min price
delete all open orders
create 100 orders depending on min price compared to market price - if it's less, create buy orders instead of sell.

Is that what you're after? If you know for a fact vircurex lets you have more than 100 open orders total (against all the different currency pairs), then of course that last line would be set to a range the user decides.

Success!

1) started old client, funded with 1000 coins from my vcx account
2) Sent 100 coins back to vcx using old client, confirmed on next block
3) Upgraded to v1.0.8 client, wallet upgraded automatically
4) Ran new client, sent 200 coins to my vcx account, confirmed on next block

So transactions are compatible between clients... last step is to merge mine a block with the new client and see that both old and new clients pick it up.

http://sourceforge.net/projects/devcoin/files/txacceptnewdvc.PNG/download

Fired up the old devcoin wallet and tried to send 10 dvc says I need to pay 6 dvc fee same as new client.

http://sourceforge.net/projects/devcoin/files/feeolddvc.PNG/download

The rescan is default true to the importprivkey function in the new client.

When you send coins it has to use existing outputs from existing transactions to make up the amount.

Often of course no existing outputs add up to the desired amount.

Thus it uses previous outputs that add up to more than enough, and sends "the change" to a new "change address" that it creates for the purpose of receiving your change.

I have heard that clients nowadays automatically "re-scan" the blockchain when they need to, but certainly the older code did not do that and I am nor convinced the new ones can always tell if you switched the wallet. So in the past you always had to deliberately tell it to re-scan if you switched the wallet out from under it. Such as when you import a key.

TO tell it to re-scan you start it with -rescan as one of the switches on its command-line.

(In a GUI the command-line is usually one of the "properties" of the shortcut or icon or menu-item; the command-line that it in effect types for you behind the scenes when you click that shortcut or icon or menu-item.)

I used to always have -rescan on the commandline in my "start the daemon" script just in case the reason I was having to start the thing was that a power outage or reboot had killed the one that had previously been running, possibly leaving the wallet in an inconsistent state or something. It is this usage of -rescan that I have been told is not needed in recent clients; supposedly the client or daemon should notice for itself if it is in an inconsistent state due to having crashed/died previously. Merely importing a key might not trigger a rescan, I do not know but I would think it would be awkward to automatically re-scan when someone imports a key because they might have another key and another key and another key and so on that they want to import before finally being ready to do the re-scan, and it would be very painful to have to wait for a full re-scan between each key and the next.

I have always used an external tool to import keys too, so I close down the daemon, use a tool to import a key or bunch of keys, then restart with -rescan so it will re-scan the blockchain to check for any transactions involving any keys in the wallet thus find any balance associated with the added keys.

-MarkM-

Yes I agree, bitcoin got painted into a corner by their existing marketing all over the web etc much of which could not be changed (gosh knows who made this that or the other webpage or article or press release etc, good luck getting all the newspapers to publish retractions or whatever etc etc etc) claiming transactions were free, then later that transactions could be free and even when not free were negligible cost and on and on backpedalling.

-MarkM-

I get that issue too. Sometimes I have to try two or three times before the faucet "sticks" long enough for me to enter the info.

I just tried and it took me three times to stay on the page.  The ad was bitcoinadvertisers.  Thanks for the faucet!

Did it sync up? It should start from
where the old client left off unless it is not
compatible(old database and new database) So in that case it starts over again.. but I thought it doesnt do that.. thats not a problem though as long as you can still send and rcv new blocks after the upgrade.

#1 - it's not every time, but it is pretty often. It's with "bitcoinadvertiser" IIRC that is doing the forwarding. The top block has no problem.

#2 - that sucks, . Someone always has to try to destroy it for everyone...

Thanks for the info.

1) I can't found anything wrong with the ads, could anyone other to confirm this ?

2) This has been solved. someone want to hack into the faucet and submit unusual data, and cause wrong status of the db.

A bounty update:

If anyone is interested in the open-source toy bounty, there is an excellent modelling software called Tinkercad available here: https://tinkercad.com/.  I believe it is proprietary  but it is free for a limited time: https://tinkercad.com/plans/

For more information about the toy bounty, see http://www.devtome.com/doku.php?id=devcoin_bounty#capitalization_1_000_000_usd

Also, if there are any new and notable DVC businesses opening up, don't hesitate to notify me.  I will soon add altcoincards to the list here: http://www.devtome.com/doku.php?id=where_to_spend_your_devcoins

Blocks are downloading and I have 8 connections.

I do have the entire block index from the old client though

Hehe thats crazy.. I think in the process of our testing multiple versions with different fees and versions old vs new clients that we corrupt our wallet such that it wont match whats on the blockchain.. So then you have to claim balances using your private keys.

However the important thing to test is that we can start with an old wallet funded say 1000 dvc and then simply upgrade by installing 1.0.8 and then thr wallet gets upgraded automatically. This is a trusted process and allows you to spend in the same wallet file via upgrading... so then subsequent sends should work.. send some to an old client like vircurex or your linux address to see if it shows up on the blockchain.. Im trying thos as it will prove that we dont have a fork.

The balance is the same as the client states = 10 DVC. However, according to my own administration, I should have 2.2 DVC now including subtracting a payment of 1,000 today to my Vircurex account.

Let's call the client I worked with today the 'old client' (showing the 2.2 balance, but with payments that do not register). The client I am currently working with is the 'new client' (showing a balance of 10 DVC, which is incomplete). The address I worked with is 18GCTJhxrWfXjnLwwjJKsSYBpyEV16pRsB.

I think the problem arises from the way payments work. Take my 10 DVC payment to Weisoq and the 1,000 DVC contribution to the Devcoin counter on 25 December 2013. These payments show in the old client as a payment of 10 and 1,000 DVC. The 10 DVC payment went to Weisoq's address and the 1,000 DVC to 1HUnznpv5nh91vEzbwvYud9ieeBCgzuscF. The Weisoq payment was made from my regular address, but in fact made a step in between. Looking at the payment details, the following happened. First, the client takes 2145 from my wallet address and splits it into two amounts, each with their own address.  The 10 DVC goes to Weisoq, I presume, and 6 DVC get's lost (I assume as payment fee).

The 2129 is then situated in the address: 14B2RbyRWfu892RJnm7CE3VBMKbZ5R9rNx. The next step is that - from this address and to make the 1,000 payment to the Devcoin counter - the 2129 DVC is splitted again into 1,000 and 1,123. The 1,000 DVC goes to the address of the Devcoin counter (1HUnznpv5nh91vEzbwvYud9ieeBCgzuscF). This is the actual address I used as recipient address. The other 1,123 DVC goes into the address 163eDwvgdhaxiEbCfozF8B81sxsx1o7ri3 which still shows a balance of 1,123 DVC.

I think the problem with my routine of importing the private key is that I do import the private key of my regular DVC address but not the private key of the intermediate DVC addresses that were created over time due to this 'splitting' activity when making payments. Therefore, in the new client I get an incomplete overview of payments and some amounts remain in limbo. In the old client, these intermediate balances show, but as payments already made that do not register on the network.

Essentially, now some 1,000 DVC is sitting in one or more addresses without an option to access this balance. The keys are still in my possession (the original wallet.dat of the old client). I would like to try an older devcoin wallet (1.0.3/4) to see how it reacts to the original wallet.dat file.

I think we should not focus on this, I just want to take out the balance and start fresh again with the current 1.0.8 wallet with a new wallet.dat.

When you copy around wallet files and run different clients on same wallet file it messed mine up so once you overwrote the wallet file with a copied version the dvc cannot be spent for security reasons.

Can you put your dvc address into the
block explorer to see what the balance is? It should match the client balance after import. Maybe blockchain thinks u have only 10?

_{^{For the avoidance of doubt, I am happy to keep our conversation on the experimental Windows client outside of this thread to avoid anoying the rest. Do you use certain IM software (I can use Google Hangouts but can install something else of course)?}}


I did the following:

1. made back up of wallet.dat
2. started client (upgraded to 1.0.8 again)
3. dumped private key
4. closed client
5. deleted wallet.dat from the Appdata/etc folder
6. started client
7. imported private key

This gives me a strange result. My balance is 10 DVC while it should be 2000+ (if everything from 26/12 until now is not counted). I think that importing the private key does not bring back certain internal changes in the original wallet (see pic below).



Closing the client, reinstating the original wallet.dat, gives me the expected balance again, but with the problem that everything after my donation to the Devcoin counter is not seen by the network (see pic below).

Metazilla is very busy, and has been replying slowly if at all, so I'm suspending Metazilla from being an admin until he has more time. He was handling the share list, so I looked for another programmer who is not already an admin to handle that.

Hunterbunter did good work with the chart and countdown clock, so I asked him to be the share admin and he agreed. To everyone who contacted Metazilla about earning devcoins for development and didn't get a reply, please message Hunterbunter.

Did you copy your wallet.dat file between versions of the client? I did that while testing and it screwed my setup. I exported my private key using dumpprivkey then saved the key.. deleted the wallet.dat then loaded up same client again and called importprivkey on the saved private key and got my coins back.. then sent to vircurex and you and it worked... so a valid test would be to take a machine with old client and simply upgrade to new client and try to send

Another review of Max’s http://altcoincards.com/

Purchased a $50 Barnes & Noble eGift Card. Very simple to select and input details (which I just made up, except email). Site forwards to coinpayments.net where you can check info and are given a DVC address and sum to transfer.

Coin payments send through a payment-submitted then funds-received mail, with link to check on progress. Altcoincards provide an order-received page. With 6 confirmations the transaction was complete and I got order receipt within minutes then egiftcard through later. Hadn’t used B&N before, but that part was fine, picking up a couple of music books (modern method & hanson fingerstyle for anyone into guitar) without having to set up an account.

All-in a really nice and attractive site with quite a few options for shopping with Devcoins.