0 Members and 1 Guest are viewing this topic.
arhag: Needing to restart the client after restoring is a known issue in previous versions, but I haven't seen it in the latest version. Is your build up-to-date? Same with missing transactions in the history; that should not be happening anymore. In particular, try dragging down the history view to refresh it, and let me know if that pulls in the missing transactions.
QQmlApplicationEngine failed to load componentqrc:/qml/main.qml:353 Type BackupLayout unavailableqrc:/qml/BackupLayout.qml:10 Cannot assign to non-existent property "onShowingChanged"
qml: PRESSED2187674ms Wallet Im json_connection.cpp:70 handle_message ] recv: {"id":4,"result":{"id":473,"name":"arhag-light","public_data":null,"owner_key":"DVS8EyLcift3nU7zL73WhsGP3wd71p3GcbipDJ5kZw2yjaHAs4wiE","active_key_history":[["2015-02-01T03:48:50","DVS6AryKFGdYZRJmmT2HaSZcRcuv1Q6VvQjbWgfnGodWrUqriM8Uz"]],"registration_date":"2015-02-01T03:48:50","last_update":"2015-02-01T03:48:50","delegate_info":null,"meta_data":{"type":"public_account","data":""}}}2188380ms Wallet Im json_connection.cpp:70 handle_message ] recv: {"id":5,"result":[[["DVS4DKUuFfL6dJfQ4kWhdayv11JHZ11MxVgy",{"condition":{"asset_id":0,"slate_id":0,"type":"withdraw_signature_type","data":{"owner":"DVSEmd5PghKWEGjnzSYQWvK4JNWwb8yHNo19","memo":null}},"balance":0,"restricted_owner":null,"snapshot_info":null,"deposit_date":"2015-02-01T06:36:00","last_update":"2015-02-01T06:38:50","meta_data":null}],["DVS6BCwPfrY1RmYQzP9CSNE6XJSGcZE9sq8G",{"condition":{"asset_id":0,"slate_id":11577634710984274078,"type":"withdraw_signature_type","data":{"owner":"DVSEmd5PghKWEGjnzSYQWvK4JNWwb8yHNo19","memo":{"one_time_key":"DVS8BE2mN2rsGgoaV1dgkPhwdYSi266kcKSUtUtQ3k5TQkUmsZapU","encrypted_memo_data":"cd8a8267d1f13a55eab3db9c0d41eecb07462d520dcac263fcb1e7b2a63429d5698b75e74228ebdc6857418e121c66fd5e4393350bb76bbb0ab205b789710acd"}}},"balance":0,"restricted_owner":null,"snapshot_info":null,"deposit_date":"2015-02-03T01:19:00","last_update":"2015-02-03T01:20:10","meta_data":null}],["DVSJNFNSppKT5EVUxZtVW5i2TWtxKsjziTC8",{"condition":{"asset_id":0,"slate_id":11577634710984274078,"type":"withdraw_signature_type","data":{"owner":"DVSEmd5PghKWEGjnzSYQWvK4JNWwb8yHNo19","memo":{"one_time_key":"DVS6kPMvYAjTFow5gAuD3rzF72iPEg1MV3NtK34g7DhVzhGgMwAFW","encrypted_memo_data":"4eaa40f41119d15a2dbdcd9db2605765e8c6919fbe00eb78e2352bd93c9be5dc6014e8c747fc66d006134976464f7422a2b6e7bf62c5e1f15f37c14d38af50d0"}}},"balance":0,"restricted_owner":null,"snapshot_info":null,"deposit_date":"2015-02-03T00:34:10","last_update":"2015-02-03T00:36:50","meta_data":null}]]]}
Just posted an updated binary (this change is not in the devshares branch yet) which should fix the junk data in the brain key.As to the Windows folks, I've contacted the guys who do our normal Windows builds and installers, and they'll be working today on getting an installer working. I make no promises as to when it will be available, but there are now experienced people working on it.
I created an account with the previous version and wrote down id,pw,recovery pw.Installed the new version and attempted to import, shows me this error."Could not claim registered account AAAA. Is your recovery password correct?"I think I entered correct one
Recovery key has broken charactershttp://www.ddengle.com/files/attach/images/894001/082/948/32893a73f961450a63d171b1a8b054ae.png
Hi, arhag. That was not implemented at the time of this beta release, but it is now implemented, albeit a bit buggy in the UX. If you rebuild from the devshares branch, you should get it.
(see link provided for full output)
^CProgram received signal SIGINT, Interrupt.0x00007ffff52aacbd in poll () at ../sysdeps/unix/syscall-template.S:8181 ../sysdeps/unix/syscall-template.S: No such file or directory.(gdb) bt#0 0x00007ffff52aacbd in poll () at ../sysdeps/unix/syscall-template.S:81#1 0x00007ffff40bafe4 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0#2 0x00007ffff40bb0ec in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0#3 0x00007ffff64fa554 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /opt/Qt5.4.0/5.4/gcc_64/lib/libQt5Core.so.5#4 0x00007ffff649deab in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /opt/Qt5.4.0/5.4/gcc_64/lib/libQt5Core.so.5#5 0x00007ffff64a2dc5 in QCoreApplication::exec() () from /opt/Qt5.4.0/5.4/gcc_64/lib/libQt5Core.so.5#6 0x000000000050e931 in main (argc=1, argv=<optimized out>) at /home/arhag/dev/bitshares/programs/light_wallet/main.cpp:53
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?
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.
To clarify, the light wallet always reports your balance correctly, but not always your history?
I don't suppose you collected the command line output around said crash, or maybe even a backtrace, did you? :]
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.
Now, I see that there was a commit just one hour ago that may solve this bug. When I posted "Great, I'm building now." I had already started the build, and now I realize I was building an older commit than the one you referenced (c6b6e4624d19a65cba0464aa06490f88f1a34b78). I guess it's time to build again...
Accounts can publish their preference to be a "public_account" or "titan_account". TITAN deposits should only be sent to registered accounts with the latter preference (but the current BTS release right now also attempts TITAN in other cases I believe). If you look at the spec for "wallet_account_register", it currently defaults to titan. You can update your preference using "wallet_account_update_registration". I'm not sure if the GUI currently shows the preference anywhere, or even if it's currently pretty printed in the CLI. If you do "enable_raw" to get the raw json output then do "blockchain_get_account <name>", you should be able to see the current setting. Light wallet always registers as public_account.
>> wallet_account_transaction_history20017 invalid_name: invalid account nameInvalid account name! {"account_name":"GENESIS"} th_a wallet.cpp:809 is_valid_account {} th_a transaction_ledger.cpp:1618 get_pretty_transaction_history {} th_a wallet_api.cpp:979 wallet_account_transaction_history {} th_a common_api_client.cpp:3474 wallet_account_transaction_history {"command":"wallet_account_transaction_history"} th_a cli.cpp:626 execute_command
Great, I'm building now. And I assume that also works from the GUI?
Can you provide more detail on this? What do I need to do to check this and change it if necessary? And specifically, what about accounts created with the light wallet? Are they public_accounts by default? I assume they should be because the light wallet can't handle TITAN and certainly doesn't currently provide any way to run advanced console commands.
If you pull latest devshares branch (c6b6e4624d19a65cba0464aa06490f88f1a34b78 right now which should be good), you should just be able to do a normal wallet_transfer to arhag-light,
assuming that it's set to a "public_account" on the blockchain.
So what command should I use to properly (non-TITAN) send funds to a light wallet account with memo and sender info working?
I helped Nathan fix that bug earlier today.
Quote from: modprobe on February 02, 2015, 06:16:44 pmI 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. Oh, okay. Is there a way to send a non-TITAN (since I presume the light wallet has no way right now of knowing about received funds via TITAN) to an account rather than an address from the full client? I basically want to send some DVS to arhag-light, have the sending client grab the public key of arhag-light from the blockchain, use it as the address to send funds to (so the light wallet is aware of the funds received), and use the one-time key included with the transaction and the public key of arhag-light to derive the shared secret that encrypts the memo and sender information.Quote from: modprobe on February 02, 2015, 06:16:44 pmAre you reporting that the light wallet listed an incorrect balance, or an incorrect transaction display?The main issue I was reporting is that a transfer initiated in the light wallet from arhag-light to another account (arhag) causes the full client holding the keys to that arhag account to believe (at least according to the transaction history) that it was the one that sent the funds rather than the one that received the funds.
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?
Quote from: cn-members on February 02, 2015, 12:22:55 pmQuote from: cgafeng on February 02, 2015, 02:50:15 amBuild the window version by vs2013 is success.But i try to build the android version by windows and looks like it can't be done.I use the qt for android(windows) and need to build the boost by mingw, and the lib boost_context can't build on windows by mingw, any idea?I think i figure out how to build the boost_context, will try it later.guide please? I never get to know how to use VS, but certainly I want to build the Windows version. Thanks不知道你是到哪一步卡住了,假设你已经能能用vs编译命令行的钱包,如果不行的话看BUILD_WIN32.md文件。编译轻钱包另外用到了库qml-extras和qml-material,qt开发包Qt 5.4.0 for Windows 32-bit (VS 2013, OpenGL) ,Qt 5.4.0 for Android (Windows 32-bit),可以在http://www.qt.io/download-open-source/#section-3下载。Qt5.4或5.3版本应该都可以,用qt5.4 for android其实只是用来编译qml-extras和qml-material,用Qt 5.4.0 for Windows 32-bit (MinGW 4.9.1)也可以。编译qml-extras和qml-material一样,都用命令行设置环境变量后用mingw编译。假设qt for android安装在d:/qt/qtAndroidCode: [Select]set PATH=D:\Qt\qtAndroid\5.4\mingw491_32\bin;D:\Qt\qtAndroid\Tools\mingw491_32\bin;%PATH%;qmakemingw32-make.exemingw32-make.exe checkmingw32-make.exe install编译成功后D:\Qt\qtAndroid\5.4\mingw491_32\qml目录下就会有material,拷贝material到Qt for Window目录下D:\Qt\Qt5.4.0\5.4\msvc2013_opengl\qml。我觉着ubuntu下编译出来的material应该也可以直接拷贝过来用。在能编译命令行钱包的基础上添加环境变量,设置vs使用的qt库目录CMAKE_PREFIX_PATH D:\Qt\Qt5.3.0\5.3\msvc2013添加编译轻钱包INCLUDE_LIGHT_WALLET TRUE这样就行了。
Quote from: cgafeng on February 02, 2015, 02:50:15 amBuild the window version by vs2013 is success.But i try to build the android version by windows and looks like it can't be done.I use the qt for android(windows) and need to build the boost by mingw, and the lib boost_context can't build on windows by mingw, any idea?I think i figure out how to build the boost_context, will try it later.guide please? I never get to know how to use VS, but certainly I want to build the Windows version. Thanks
Build the window version by vs2013 is success.But i try to build the android version by windows and looks like it can't be done.I use the qt for android(windows) and need to build the boost by mingw, and the lib boost_context can't build on windows by mingw, any idea?I think i figure out how to build the boost_context, will try it later.
set PATH=D:\Qt\qtAndroid\5.4\mingw491_32\bin;D:\Qt\qtAndroid\Tools\mingw491_32\bin;%PATH%;qmakemingw32-make.exemingw32-make.exe checkmingw32-make.exe install
TIMESTAMP BLOCK FROM TO AMOUNT MEMO BALANCE FEE ID ==============================================================================================================================================================================================...2015-01-24T23:57:20 155748 arhag UNKNOWN 100.00000 DVS To: DVS2AgMj... (X) DVS 1.00000 DVS 0162871b2015-02-01T06:36:02 213806 arhag UNKNOWN 10.00000 DVS test (X - 11) DVS 1.00000 DVS a95dc4a12015-02-01T06:39:00 213823 arhag arhag-light 8.00000 DVS testing (X - 11 - 9) DVS 1.00000 DVS cf9aa5c6
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!
~$ mkdir BitShares && cd BitShares~/BitShares$ sudo apt-get install cmake git libreadline-dev uuid-dev g++ libdb++-dev libdb-dev zip libssl-dev openssl build-essential python-dev autotools-dev libicu-dev libbz2-dev libboost-dev libboost-all-dev npm nodejs-legacy~/BitShares$ sudo npm install -g lineman
~/BitShares$ wget http://download.qt-project.org/official_releases/qt/5.4/5.4.0/qt-opensource-linux-x64-5.4.0.run~/BitShares$ sha256sum qt-opensource-linux-x64-5.4.0.run
~/BitShares$ chmod +x qt-opensource-linux-x64-5.4.0.run~/BitShares$ sudo ./qt-opensource-linux-x64-5.4.0.run
~/BitShares$ git clone https://github.com/papyros/qml-extras.git~/BitShares$ mkdir qml-extras-build && cd qml-extras-build~/BitShares/qml-extras-build$ /opt/Qt5.4.0/5.4/gcc_64/bin/qmake ../qml-extras~/BitShares/qml-extras-build$ make && make check
~/BitShares/qml-extras-build$ sudo make install~/BitShares/qml-extras-build$ cd ..~/BitShares$ git clone https://github.com/nathanhourt/qml-material.git~/BitShares$ mkdir qml-material-build %% cd qml-material-build~/BitShares/qml-material-build$ /opt/Qt5.4.0/5.4/gcc_64/bin/qmake ../qml-material~/BitShares/qml-material-build$ make && make check
~/BitShares/qml-material-build$ sudo make install~/BitShares/qml-material-build$ cd ..
~/BitShares$ rm -rf bitshares # Remove any prior bitshares folder~/BitShares$ git clone https://github.com/BitShares/bitshares.git~/BitShares$ cd bitshares~/BitShares/bitshares$ git submodule init && git submodule update~/BitShares/bitshares$ cd programs/web_wallet~/BitSharesbitshares/programs/web_wallet$ npm install~/BitSharesbitshares/programs/web_wallet$ cd ../../../
~/BitShares$ cd bitshares~/BitShares/bitshares$ git pull~/BitShares/bitshares$ git checkout devshares~/BitShares/bitshares$ git submodule update~/BitShares/bitshares$ cd ..~/BitShares$ rm -rf devshares-build # Remove any prior devshares-build folder~/BitShares$ mkdir devshares-build && cd devshares-build~/BitShares/devshares-build$ cmake -DINCLUDE_QT_WALLET=ON -DINCLUDE_LIGHT_WALLET=ON -DCMAKE_PREFIX_PATH=/opt/Qt5.4.0/5.4/gcc_64/ ../bitshares/~/BitShares/devshares-build$ make forcebuildweb~/BitShares/devshares-build$ make~/BitShares/devshares-build$ cd ..
~/BitShares$ cd bitshares~/BitShares/bitshares$ git pull && git checkout devshares && git submodule update && cd ../devshares-build~/BitShares/devshares-build$ make forcebuildweb # Only needed if web_wallet code changed~/BitShares/devshares-build$ make
add-apt-repository ppa:beineri/opt-qt54-trustyapt-get updateapt-get install qt54-meta-full
export QTDIR=/opt/qt54/export PATH=$QTDIR/bin:$PATH export MANPATH=$QTDIR/man:$MANPATH export LD_LIBRARY_PATH=$QTDIR/lib:$LD_LIBRARY_PATH
qmake -v
git clone https://github.com/papyros/qml-extrascd qml-extrasqmakemakemake checksudo make installcd ..
git clone https://github.com/nathanhourt/qml-materialcd qml-materialqmakemakemake checksudo make installcd ..
git clone https://github.com/BitShares/bitsharescd bitsharesgit checkout devsharesgit submodule initgit submodule updatecmake -DINCLUDE_LIGHT_WALLET=ON CMakeLists.txtmake
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.
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?).
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.
I will try installing Qt 5.4 and building LightWallet against that next.
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.
$ ./LightWallet1502092ms th_a thread.cpp:95 thread ] name:ntp tid:1399316280378881502118ms ntp ntp.cpp:77 request_now ] resolving... ["pool.ntp.org",123]QML debugging is enabled. Only use this in a safe environment.1502613ms ntp ntp.cpp:81 request_now ] sending request to 132.163.4.102:123QQmlApplicationEngine failed to load componentqrc:/qml/main.qml:116 Type WelcomeLayout unavailableqrc:/qml/WelcomeLayout.qml:2 module "QtQuick.Controls" version 1.3 is not installed
Xeroc: You're using papyros's copy of qml-material, not my fork. Make sure to get qml-material from github.com/nathanhourt/qml-material 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?
54 function connectToServer() { 55 if( !wallet.connected ) 56 wallet.connectToServer("localhost", 5657, "DVS8GV6nP15gBZQbuEGamH95gYR5EioxkUbEYjpDHMjPEeRWsvR63") 57 }
./LightWallet --help ─┘1553542ms th_a thread.cpp:95 thread ] name:ntp tid:29560737921553542ms ntp ntp.cpp:77 request_now ] resolving... ["pool.ntp.org",123]QML debugging is enabled. Only use this in a safe environment.1553554ms ntp ntp.cpp:81 request_now ] sending request to 141.82.25.201:1231553594ms ntp ntp.cpp:147 read_loop ] received ntp reply from 141.82.25.201:1231553594ms ntp ntp.cpp:161 read_loop ] ntp offset: 5618, round_trip_delay 397131553594ms ntp ntp.cpp:177 read_loop ] ntp_delta_time updated to 5618QQmlApplicationEngine failed to load componentfile:///files/git/bitshares/programs/light_wallet/qml/main.qml:284 Type TransferLayout unavailablefile:///files/git/bitshares/programs/light_wallet/qml/TransferLayout.qml:67 Cannot assign to non-existent property "showHelperText"
where are the sources for the light-client? I'd like to compile locally
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 qml-extras.pro and qml-material.pro and removing the references to the tests subdir. Then you can just `sudo make install` and it should work.
FAIL! : extras::HttpTests::test_getgoogle() Uncaught exception: HttpLib is not defined
2703390ms th_a thread.cpp:95 thread ] name:ntp tid:1406443924907522703391ms ntp ntp.cpp:77 request_now ] resolving... ["pool.ntp.org",123]2703397ms ntp ntp.cpp:81 request_now ] sending request to 50.116.38.157:123QML debugging is enabled. Only use this in a safe environment.2703485ms ntp ntp.cpp:147 read_loop ] received ntp reply from 50.116.38.157:1232703485ms ntp ntp.cpp:161 read_loop ] ntp offset: 87993113, round_trip_delay 883882703485ms ntp ntp.cpp:177 read_loop ] ntp_delta_time updated to 87993113QQmlApplicationEngine failed to load component file:///home/arhag/devshares/programs/light_wallet/qml/main.qml:1 module "QtQuick" version 2.4 is not installed
Oh, and remember to use my fork of qml-material at github.com/nathanhourt/qml-material -- I've made some changes that haven't been merged upstream.
********* Start testing of materials *********Config: Using QtTest library 5.3.0, Qt 5.3.0PASS : materials::Card Test::initTestCase()PASS : materials::Card Test::test_showCard()PASS : materials::Card Test::cleanupTestCase()QWARN : materials::UnknownTestFunc() file:///home/arhag/qml-material/tests/tst_pagestack.qml:27:5: Type ApplicationWindow unavailable ApplicationWindow { ^QWARN : materials::UnknownTestFunc() file:///home/arhag/qml-material/modules/Material/ApplicationWindow.qml:82:5: Type Toolbar unavailable Toolbar { ^QWARN : materials::UnknownTestFunc() file:///home/arhag/qml-material/modules/Material/Toolbar.qml:150:5: Type Tabs unavailable Tabs { ^QWARN : materials::UnknownTestFunc() file:///home/arhag/qml-material/modules/Material/Tabs.qml:44:13: Type Ink unavailable Ink { ^QWARN : materials::UnknownTestFunc() file:///home/arhag/qml-material/modules/Material/Ink.qml:166:13: CircleMask is not a type CircleMask { ^QWARN : materials::tst_pagestack::compile() /home/arhag/qml-material/tests/tst_pagestack.qml produced 5 error(s): /home/arhag/qml-material/tests/tst_pagestack.qml:27,5: Type ApplicationWindow unavailable /home/arhag/qml-material/modules/Material/ApplicationWindow.qml:82,5: Type Toolbar unavailable /home/arhag/qml-material/modules/Material/Toolbar.qml:150,5: Type Tabs unavailable /home/arhag/qml-material/modules/Material/Tabs.qml:44,13: Type Ink unavailable /home/arhag/qml-material/modules/Material/Ink.qml:166,13: CircleMask is not a type Working directory: /home/arhag/qml-material/tests View: QQuickView, import paths: '/home/arhag/qml-material/modules' '/home/arhag/qml-material/tests' '/opt/Qt5.3.0/5.3/gcc_64/qml' Plugin paths: '.'FAIL! : materials::tst_pagestack::compile() Type ApplicationWindow unavailable Loc: [/home/arhag/qml-material/tests/tst_pagestack.qml(27)]Totals: 3 passed, 1 failed, 0 skipped********* Finished testing of materials *********
For the windows folks, I think I can get a binary for you
Great. I'll wait for the build instructions for Linux.Out of curiosity I attempted to build the light wallet a couple days ago and ran into some major problems trying to get it to work with Qt 5.3 (which is not installed by default on my Ubuntu 14.04 system) and qml-material. So, I hope you will have clear instructions on how to build from source on Ubuntu 14.04.