Since the release of Vessel 0.2.0, I've been busy talking to many of you and working hard to resolve the bugs you've encountered. The version now has jumped 3 revisions and is 0.2.3, with a few improvements and a number of bug fixes for various operating systems.
Before going too much further:
What is Vessel?
Vessel is a desktop wallet for the Steem blockchain, which can be downloaded and run on your computer. Vessel is free to use and open source, and is designed to be a way to help secure your account on the Steem blockchain. While using Vessel, your keys/password never leave the app, transactions are signed locally, and then broadcast to the network much like any other downloadable cryptocurrency wallet.
Here's a few of the other most recent updates, as well as the original announcement:
Download Vessel
Vessel is still beta software and it's recommended that you treat it as such. Before committing irreversible actions on your account (such as large outgoing transfers), please test with smaller amounts to ensure it's working properly on your computer.
Download available on github for macOS (.dmg file), Windows (.exe file) and Linux (.snap and .deb files).
- Releases: https://github.com/aaroncox/vessel/releases
- chainBB Forums: https://chainbb.com/f/vessel
- Bug Reports: https://github.com/aaroncox/vessel/issues
- Source Code: https://github.com/aaroncox/vessel
What's new in 0.2.1 through 0.2.3
- The delegation operation prompt will now display a notice if you have an existing delegation you are going to overwrite.
- Distribution of Vessel through Snapcraft (https://snapcraft.io/vessel/).
- Vessel will now prompt for operations if Vessel is not already open.
- Bug fixes to allow Linux/Windows users to be prompted via links.
- Removed the requirement of the
appdata portion of the URL (after the #)
Linux Users can now install via the Snap Store (or compatible application)
If you are using a Linux distribution that supports the Snap Store, it's incredibly easy to install Vessel now. Just search for vessel and it will appear and allow installation.
[IMAGE: https://steemdb.com/vessel/43.png]
If you're prefer to go about it from the command line, that's possible as well, simply by typing:
snap install vessel
Vessel will now be installed and available through your application launcher.
Delegation Operation Overwriting
[IMAGE: https://steemdb.com/vessel/44.png]
By the design of Steem's delegation system, you can only have a single delegation between your account and another. Everytime you change this, it's overwriting the value, as opposed to creating a new delegation. This is/was confusing depending on how the end user UI presents it before triggering a Vessel operation.
This new blue information window has been added to inform the user that an existing delegation is present, and informing them that they're altering the existing delegation rather than adding to it.
More 0.2.x releases
As we finish out this year and move into 2018 - you can expect a lot more of these minor releases as I continue to tweak what's possible with this custom protocol. This post itself isn't glamorous or exciting, but these bug fixes are critical for adoption.
Please continue to reach out as you're integrating Vessel into your projects. Let me know what problems you're running into, what could be better, and what it will take to help make your project successful.
Originally posted in the /f/vessel forum on chainBB.com (learn more).
Installing Vessel from Source on Linux
Trying to install Vessel by source. I had already checked out vessel from github to development/vessel and from time to time I update it with:
git fetch origin
git reset --hard origin/master
The checkout version I am using is e1e7bd7e016aa473d3473f6e8ff7de11820809d0 from Thu Dec 21 20:50:29 2017 -0500
Vessel doesn't have a "production" mode for install. That is to say, when you install it you also get the packages for developing for it. If you try to use the "--production" flag, the installation fails. So, omit that flag.
Installing 'developer' version:
development/vessel $ npm i
> rabin-bindings@1.7.4 install /home/alumno/development/vessel/node_modules/rabin-bindings
> prebuild-install || node-gyp rebuild
prebuild-install info begin Prebuild-install version 2.3.0
prebuild-install info looking for local prebuild @ prebuilds/rabin-bindings-v1.7.4-node-v57-linux-ia32.tar.gz
prebuild-install info found local prebuild
prebuild-install info unpacking @ prebuilds/rabin-bindings-v1.7.4-node-v57-linux-ia32.tar.gz
prebuild-install info unpack resolved to /home/alumno/development/vessel/node_modules/rabin-b
... much deleted ...
[0] !! No flow@v0.45.0-compatible libdefs found in flow-typed for the above untyped dependencies !!
[0]
[0] I've generated `any`-typed stubs for these packages, but consider submitting
[0] libdefs for them to https://github.com/flowtype/flow-typed/
[0]
[0] npm run flow-typed exited with code 0
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: 7zip-bin-mac@1.0.1 (node_modules/7zip-bin-mac):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for 7zip-bin-mac@1.0.1: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"ia32"})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@1.1.3 (node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.1.3: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"ia32"})
added 1547 packages in 577.689s
It looks like it worked.
Creating a Release
~/development/vessel $ npm run package-linux
> vessel@0.2.2 package-linux /home/alumno/development/vessel
> npm run build && build --linux
> vessel@0.2.2 build /home/alumno/development/vessel
> concurrently "npm run build-main" "npm run build-renderer"
[0]
[0] > vessel@0.2.2 build-main /home/alumno/development/vessel
[0] > cross-env NODE_ENV=production node --trace-warnings -r babel-register ./node_modules/webpack/bin/webpack --config webpack.config.main.prod.js --progress --profile --colors
[0]
[1]
[1] > vessel@0.2.2 build-renderer /home/alumno/development/vessel
[1] > cross-env NODE_ENV=production node --trace-warnings -r babel-register ./node_modules/webpack/bin/webpack --config webpack.config.renderer.prod.js --progress --profile --colors
[1]
[0] 10% building modules 1/1 modules 0 active 10% building modules 0/1 modules 1 active mult 10% building modules 1/2 modules 1 activ 10% building modules 1/2 modules 1 active ...e_modu 10% building modules 7/10 modules 3 active ...alumno/development/vessel/app/menu.js 10% buil 11% building modules 15/208 modules 193 active ...core-js/modules/core.regexp.escape.js 18% 12% building modules 17/208 modules 191 active ...core-js/modules/core.regexp.escape.js 18% 19% building modules 80/205 modules 125 active ...core-js/modules/core.regexp.escape.js 13% 19% building modules 82/205 modules 123 active ...core-js/modules/core.regexp.escape.js 13% 15% building modules 45/208 modules 163 active ...core-js/modules/core.regexp.escape.js 20% 16% building modules 50/208 modules 158 active ...core-js/modules/core.regexp.escape.js 21% 16% building modules 55/208 modules 153 active ...core-js/modules/core.regexp.escape.js 21% 22% building modules 104/205 modules 101 active
... much deleted ...
12ms advanced chunk optimization
360ms building modules
0ms module and chunk tree optimization
198ms module reviving
89ms module order optimization
109ms module id optimization
76ms chunk reviving
[1] 1ms chunk order optimization
135ms chunk id optimization
489ms hashing
8ms module assets processing
1231ms chunk assets processing
29ms additional chunk assets processing
6ms recording
91% additional asset processing
After four hours of waiting, I decided there is some kind of failure to exit some loop somewhere deep in the code that does this. I will try again tonight to see if we can get this installed again.
@gold84 | Dec. 29, 2017, 1:41 p.m. | Votes: 2 | [
VOTE ]
@jesta Happy Holidays! I am not sure if you ever read a post from me, but I really enjoy reading your posts and improvements to developments you continuously do. What you made with vessel is great, and it looks to me this is very related to the release or with the SMTs, because with vessel you let every website to connect to the steem blockchain, right? I saw @utopian-io from @elear already added vessel for their delegation function. I am their as a small sponsor by the way, and also contribute with ideas for the steemit front-end from time to time.
I also listened you in the panel held by @aggroed about the future of steemit, steem, and things to take care of now to achieve what we want to achieve for the technology. Amazing contributions from all of you: @jesta , @blocktrades, @lukestokes , @elear and @timcliff, as well as the others that were participating.
Thank you very much for all your contributions from the very beginning of the platform and the steem blockchain!
By the way, yesterday I published the 1st chapter of the Full Steemit Guide to help new visitors, new members, minnows and other steemians make their way easier on the platform. @lukestokes and @blocktrades deserve more than the simple thanks I gave them for their support on it. The same as them, by reading your posts, listening to the panel, reading the way you answer comments, it shows you really care about the platform and the steem blockchain and do everything you can to help everyone here.
I also just published Chapter 2.I mentioned you their and shared the link to a post you made explaing something important about the wallet.
I believe many more steemians will benefit from it on this new post too. Thanks for that great contribution too.
Here is the link to chapter 2 in case you would like to take a look:https://steemit.com/steem/@gold84/chapter-2-of-11-focusing-on-the-details-of-the-steem-wallet-to-learn-as-much-as-possible-how-to-use-it-transfer-steem-sbd
Looking forward to hear from you soon, and your thoughts on this new chapter.
Regards, @gold84