Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - modprobe

Pages: 1 2 3 4 [5] 6 7
DevShares / Re: DVS Light Wallet for Mac Open Beta
« on: February 05, 2015, 10:43:29 pm »
And only 21 of those 35 registered accounts, and several of those never sent a transaction from the light wallet. So is anyone having trouble?

But I also note that the LW is currently very simple, so there's not much *to* test. The fact that 21 people registered accounts and many of them sent transactions to and from their wallets without reporting serious problems tells me that it's working pretty well so far, which was really the point of this release: get a minimal, useful product out there which is simple enough to be quick and easy to fully test.

DevShares / Re: DVS Light Wallet for Mac Open Beta
« on: February 05, 2015, 09:43:27 pm »
That's the plan! :)

We're planning to release a beta of the LW on BitShares. Are there any critical issues in the light wallet that have been found which need to be fixed prior to releasing on the live BitShares network?

DevShares / Re: DVS Light Wallet for Mac Open Beta
« on: February 05, 2015, 08:32:24 pm »
I'm afraid not, clayop. I spent about 5 hours on monday trying to get our windows dev box to build something, but neither I nor the resident windows user could get it working. Maybe cgafeng can give you a binary? At some point, we'll have to get the light wallet integrated into our normal windows build process, but we haven't done that yet.

DevShares / Re: DVS Light Wallet for Mac Open Beta
« on: February 03, 2015, 03:53:49 pm »
Since all of this information is recorded in the blockchain and associated to the active key of the light wallet accounts, why can't the light wallet client simply query the light wallet server to give it all the raw transactions from the blockchain that are associated with its public active key? Then the light wallet could reconstruct the transaction history even if didn't store it locally.
That's exactly what it does, although it caches things based on time, so I'm guessing your cache got damaged in the crash. Right now I'm just using FC to do persistence, but I think I need something a little more capable. I'll look into this. To clarify, the light wallet always reports your balance correctly, but not always your history? It's designed to be a bit more careful about reporting the balance correctly, so I'm glad that's working as intended.

I am curious about that crash, though. I haven't seen any crashes except crashes on exit. I don't suppose you collected the command line output around said crash, or maybe even a backtrace, did you? :]

DevShares / Re: DVS Light Wallet for Mac Open Beta
« on: February 02, 2015, 06:16:44 pm »
Builds for android are technically possible, but no one has any idea how to build fc for android, so that's a non-starter for now. Someday I'll look into it further.

Unfortunately, has taken to giving unreliable results for their hashes. The Qt wallet even shows different images for the same thing on different pages. This is not our bug.

@arhag: I'm not entirely sure what all issues you're describing... I note that if you used transfer_to_address, memos will *not* be sent, as it's impossible to send a memo without a public key (and transfer_to_address doesn't use a key; only an address) so it's expected behavior that the recipient won't have the memo. Are you reporting that the light wallet listed an incorrect balance, or an incorrect transaction display?

DevShares / Re: DVS Light Wallet for Mac Open Beta
« on: February 01, 2015, 10:28:32 pm »
@fluxer: I agree with you, and I'd like to see such solutions deployed. The issues aren't insurmountable, but they need consideration, and I welcome new ideas on how to solve them (why waste time implementing one bad solution if someone else can think of a better one?). Right now I'm the only one running a light server because it's under heavy development (you think delegates have to upgrade a lot? Ha!) and I need to be able to debug and redeploy rapidly. Once I've got a relatively stable solution (which is, of course, the point of this beta -- to figure out what needs to be changed to sustain a reliable solution) then I'll be looking into multi-server models. Eventually, I'll make it configurable.

Still, the model of paying a centralized party to provide immediate, accurate information is a reasonable one, particularly when I deploy mobile apps where all matters of internet traffic are much more expensive (in time and money).

@cn-members: Thank you very much for taking the time to detail out those instructions. I'll add those to a README on GitHub soon.

@arhag: I'm glad you got it working! Yes, I do develop against 5.4. I think 5.3 would work, but you'll have to turn back the version numbers in the import statements until it works, and doing that might break something which depends on the later version. I haven't researched exactly when all the features I need were added, so I just use the latest version available at the time of writing.

Is anyone else still having trouble building? For the rest of you, do you have any comments or problems you've experienced?

For the windows users, I'm hoping to get my hands on a windows dev box tomorrow, so hopefully I'll get something together for you. Thanks for being patient!

DevShares / Re: DVS Light Wallet for Mac Open Beta
« on: February 01, 2015, 01:46:43 am »
For those on Qt 5.3, which I believe ships QtQuick 2.3, I've updated the imports in the QML files to reference QtQuick 2.3 instead of 2.4. I've also updated the light wallet to connect to my server on the devshares branch. Hopefully that will simplify building for you all.

DevShares / Re: DVS Light Wallet for Mac Open Beta
« on: January 31, 2015, 11:54:20 pm »
Yeah, for some reason it's still pointing at localhost. I thought I fixed that. Anyways, just change "localhost" to "" and you'll be set.

DevShares / Re: DVS Light Wallet for Mac Open Beta
« on: January 31, 2015, 07:12:41 pm »
Hi, fluxer. Thanks for the thoughts. I would like to move to a multiple server model, but this does have some difficulties. One is performance (I've got to wait for N servers to respond instead of 1), and another is fragility (if I use 2 servers and they give different results... now what?) as well as ambiguity (If I query three servers and two never respond... now what?), as well as economics (each light server charges a fee for propagating transactions; if I have N lightservers, I have to pay N fees?). I haven't taken the time to come up with good answers to these questions, so the current version only supports one server. If we can come up with a good design, though, I'll be happy to implement a multiple server architecture.

As to the issue of delegates hosting servers, it's a great idea, but the light wallet has no way of knowing who the delegates are nor what they've published in their accounts. The light wallet would then need to trust a lightserver to give it accurate information about the delegates, which defeats the purpose.

DevShares / Re: DVS Light Wallet for Mac Open Beta
« on: January 31, 2015, 06:41:09 pm »
Xeroc: You're using papyros's copy of qml-material, not my fork. Make sure to get qml-material from and to use the develop branch. Edit: scratch that, you've got an old version of the light wallet. Are you sure you're building on the devshares branch?

Arhag: Your version of Qt is older than the lightwallet expects. You can update Qt, or you can try modifying the wallet to use an older version of Qt by turning down the version number in the qml files (change `import QtQuick 2.4` to 2.3 or lower)

DevShares / Re: DVS Light Wallet for Mac Open Beta
« on: January 31, 2015, 06:47:44 am »
Oops, I spoke too soon. Looks like the qml tests build after installing qtdeclarative5-dev

DevShares / Re: DVS Light Wallet for Mac Open Beta
« on: January 31, 2015, 06:36:57 am »
Update for the Ubuntu users: I can't get qml-extras and qml-material to build their tests. My best guess is that the old version of Qt that ships with Ubuntu just can't handle it. As a workaround, disable the tests by editing and and removing the references to the tests subdir. Then you can just `sudo make install` and it should work.

Oh, and remember to use my fork of qml-material at -- I've made some changes that haven't been merged upstream.

DevShares / Re: DVS Light Wallet for Mac Open Beta
« on: January 31, 2015, 05:53:04 am »
I'll try and set up an Ubuntu VM to test building in. I'm building on ArchLinux right now, and it's going buttery smooth. Installing qml-extras and qml-material didn't give me any difficulty, but those are packaged for Arch so it's laughably easy. :}

For the windows folks, I think I can get a binary for you, but I'm not certain how hard it'll be to pull all the dependencies together.

DevShares / DVS Light Wallet for Mac Open Beta
« on: January 31, 2015, 12:03:28 am »
Hello, all!

It's finally time to publish an open beta for my light wallet, currently available for DevShares. For those who want to skip the intro and get straight to the download, a Mac binary is available here: Update! Just ignore the error about assets at startup. Should fix the junk characters in the brain key
Windows binaries will hopefully be available at some point. I would post build instructions, but we need to merge everything necessary into the official DevShares release first.

The usual disclaimers. This is beta software. It has bugs. It sometimes crashes on exit. It might lose your money, it might start thermonuclear war, and it might eat your lunch. Use it at your own risk. I'm happy to support it, but I'm not liable for anything it does. Also, the source code is available in the programs/light_wallet folder on the BitShares code repository, though this particular binary is built using a custom merge of the develop and devshares branches which is not published anywhere, as some of the features it requires have not yet been tagged into a devshares release. It does not have any code which is not available on one of those two branches, though.

This wallet is a light wallet; it uses my server at to query the blockchain and also to register accounts. The light wallet manages your private keys, and never sends them to anyone else, as you would expect. It also creates its transactions locally, then scans them and confirms them with the user before signing and submitting to my server for broadcast. This way, I give the user reasonable certainty that a bug in the code will not cause them to sign an unintended transaction.

At present, the wallet only allows one account to be created, and it requires that the account be registered by my server. It does not support BitShares Logins or other BTS URLs. Future versions will allow more options, but I want to keep it as simple as possible for the beta test, so that I can fix bugs in the code now, as this will be the platform upon which all future features are built. I also want to get it out there in hopes that it can be useful to people sooner rather than later, and I can prioritize further development based on feedback.

Finally, I note that the full-node web/qt wallet currently has a bug which prevents it from displaying transactions from my light wallet in the history. This is purely a history display bug; the full wallet does include the received funds in your balance and can spend them. I also note that at present, our extended memos are buggy and memos longer than 19 bytes are not displayed correctly.

Thanks for reading, and let me know what you think, and vote for :)

DevShares / Re: No WIF Error starting rpc server
« on: January 29, 2015, 07:23:04 pm »
You can use the bts_create_key utility (in programs/utils) to generate a private key to use. We should make it disable encrypted RPC if no key is provided.

Pages: 1 2 3 4 [5] 6 7