The Gridcoin community has begun customizing the Bitshares web
wallet, prioritizing OPEN.GRC as a featured asset & main trading
pair against many important BTS assets!
It only took a day of editing (and a day of messing with the build
environment) to get this far. It's not a live wallet for the public, but
still in development & open-source for anyone to run locally.
I might create a guide for setting up a similar build environment using Windows and Virtualbox if anyone's interested?
I hope to add in new drop-down menus to the right of
'Deposit/Withdraw', linking to the other web wallets (OpenLedger,
FreedomLedger, BTSABC, etc) and to BOINC/BTS/Gridcoin community links.
The *.JSX is a tad confusing though..
Some of the screenshots still show Open.BTC being used as the trading pair, this has been changed.
Here’s a little announcement for what's to come regarding Decred's design development.
Our goal was to create an engaging and recognisable identity and design direction to represent Decred across different platforms and contexts. We’ve worked out a common vision and a set of principles with Decred core team to bring longevity, togetherness, and representation for it both as a cryptocurrency and as a project in any environment.
The estimated launch for the new visual identity and design direction is February 2017.
What to expect:
- The new visual identity and design system
- New Decred main site
- New designs for the key platforms (docs, forum, social media, webwallet, decrediton, mainnet etc)
It is needed to make it easier to tell about Decred. For this we’ve created the visual communication toolkit. Anyone who wishes to represent Decred can use it. It contains a set of simple + practical tools and guides for different contexts – e.g. for creating marketing materials, information/communication design or application design.
The main site and key platforms received a design overhaul for a consistent and professional representation of Decred. The wider goal is the create international awareness and legitimacy. For new (and old) users the goal is to help with the on-boarding process, building understanding of Decred as well improving the general experience.
If anyone plans or is currently creating new graphical content, I recommend not to use any pre-released, copied or re-drawn logos and symbols you might have already seen. Instead use “Decred" logotype (without symbol) or “DCR" in a simple, clean and bold textual form (e.g. typeface: Montserrat Bold) until the appropriate files and the toolkit is released. This will help avoid wrong first impressions and any possible confusion.
Stratis Platform Showcased At The Blockchain Expo in London, U.K.
Press Release: LONDON, Jan .23, 2017 / (Stratis Comms)
This coming week, companies and developers attending the Blockchain Expo in London,
U.K. (Jan 23-24, 2017) will have the opportunity to learn how to
develop, test and deploy decentralized blockchain apps using the Stratis Platform.
The team behind the
Stratis Platform will be presenting their breakthrough development: a
proven, secure and scalable end-to-end solution for C# / .Net
decentralized blockchain applications.
Dubbed as the “Blockchain for Business” company, Stratis promises to
accelerate and make more efficient the process of blockchain development
and deployment by offering:
Seamless development, integration and distribution of blockchain solutions on Microsoft’s .Net framework
Fully certified, proven and security compliant data management
Rapid acceleration for your blockchain project development
One-click provisioning of blockchain solutions on Azure BaaS and Cloud Stratis
Professional support throughout the development process
In the words of Chris Trew, CEO and Founder of Stratis Ltd:
“The Stratis Platform marks the
next step in the evolution of Bitcoin, by facilitating adoption among C#
and .Net developers, while integrating the latest technological
improvements to the original Bitcoin protocol. “
Stratis blockchain solutions combine the robustness of the Bitcoin
consensus model with a set of familiar tools, programming languages and
business infrastructure used by large and medium sized companies
Based on an original rewrite of the Bitcoin protocol in C#
(NBitcoin), by famed Bitcoin core developer Nicolas Dorier, the nStratis
Development Framework (SDF) allows companies to easily develop, test
and deploy blockchain applications without the hassle of maintaining a
complex infrastructure or having to learn complex programming languages
used in other solutions.
To facilitate testing and deployment, Stratis offers the option of
one-click provisioning of blockchains, sidechains and private blockchain
projects. Earlier last year, the company announced the deployment of
Stratis solutions on Microsoft’s Azure Blockchain as a Service (BaaS).
In addition, the company offers its own Blockchain hosting solution –
Cloud Stratis, which is specifically suited for customized projects
including private and side blockchains.
Stratis solutions can be applied to solving the most daring
challenges in the online world nowadays, such as establishing and
protecting Internet identity and trust among parties, maintaining
immutable ledgers and in IoT solutions that require a reliable and low
cost system for reporting and processing of micro-payments.
Additionally, the platform can be used to create and manage all type of
assets, support crowfunding campaigns and promotions.
The Stratis Platform also includes a publicly traded token $STRAT,
which is the result of a full rewrite in C# of Bitcoin’s proven
architecture and consensus mechanism. It was one of the best performers
among cryptocurrencies in 2016 in terms of financial returns to its
To assist development, the company offers tools, code sample and technical support via Stratis Academy.
This initiative seeks to initiate C#developers from all over the world
into this novel technology, by offering incentives and opportunities to
compete and showcase their abilities in hackathons and other activities.
We invite you to stop by booth #321 at the Expo for a demonstration
of the many capabilities of the Stratis Platform, and the opportunity to
evaluate your project together with Stratis experts led by its CEO and
Founder Chris Trew.
You can learn more about Stratis and its projects at our website : (www.stratisplatform.com)
Stratis Group Ltd., is the source of this content. Virtual currency
is not legal tender, is not backed by the government, and accounts and
value balances are not subject to consumer protections. This press
release is for informational purposes only. The information does not
constitute investment advice or an offer to invest.
It’s time for our weekly update and we have some more great news for
you this week. We are really starting to gather some momentum as we work
towards some of our goals and also add some new capabilities to the
We are also aware of the syncing issues that everyone is having with the latest wallet and we are working to resolve that issue.
Dedicated Nav Coin Community Site
We have put together a community site dedicated to Nav Coin with the
main feature being the forum. The main advantage is having topics split
up so information is easier to find. With a 1000+ page long thread here
the useful information gets quickly buried. It also has much better
capabilities than bitcointalk and should enable everyone to submit
richer post content.
There is also a chat room, calendar and staff directory. http://forum.navcoin.org/
From today onwards, our official forum is going to be our main forum
for information, news, troubleshooting etc.. so please sign up and head
on over there. Don’t forget we are also available on Slack, Telegram,
Reddit, Twitter and Facebook too.
Craig MacGregor speaking at AML Summit
Craig MacGregor has been asked to speak amongst International Keynote
Speakers and local industry leaders at a financial consultancy summit
in Auckland, New Zealand. There he will be educating local financial
industry members on the benefits of blockchain technology and will be
acting as an ambassador to promote Nav Coin.
The conference takes place on the 9th of March 2017. Registration is now open. http://www.amlsolutions.co.nz/... http://forum.navcoin.org/index...
New Team Members
Michael Douranos, Victor Jones & David Quick.
Michael is coming onboard as our latest Community Manager. He has
worked alongside Petros in the past and together they have a proven
track record to create brand awareness and help communities grow.
Victor is a Senior Software Developer from Auckland and is a talented
developer. He is coming on board firstly to help finish the unit
testing and optimization of NavTech and then is going to review and
analyze the system to give his recommendations on improvements.
David is a Senior Interactive Designer also from Auckland. He is
going to firstly help us bring a fresh design to the Nav Coin website
focusing on User Experience and Search Engine Optimization.
Our team is growing quite nicely, we now have 11 members. You can keep up to date with our team on the website http://www.navcoin.org/foundat...
We are still looking for more intermediate – senior developers to
come onboard and help with our development projects. Primary required
are looking at ways to raise some venture capital and the positions
will hopefully turn into contract work at industry rates.
Contact us if you think you fit the bill!
Nav Coin Core Upgrade
Craig, Soopy and Alex are working to get the Nav Coin Core up to date
with the Bitcoin 13.0 source. This will increase Nav Coin’s stability,
capabilities and ability to integrate with other services. By updating
to 13.0 we will get some great technical benefits including the
capability to have a Nav Coin Insight API and Segregated Witness.
With the advent of the Insight API we will be able to be added to
many more platforms including the KeepKey hardware wallet and various
credit card issuers.
This project has been given priority for our core team because it is
currently blocking some of the other projects we want to start.
Once we have upgraded the Nav Core to reflect Bitcoin 13.0 we will
begin work on forking Bitpay’s Copay wallet for use with Nav Coin. It is
It is capable of running on Android, iOS and as a Web Wallet on any
We have consolidated some of our existing projects for mobile wallets
under this banner as it has proven to be the best way to move forward. https://copay.io/
The current Web Wallet project remains and we are still hopeful to
get this out to you all soon. Our third party contractor is having some
delays with the project. I will let you know more information as it
We have also updated the website with the latest projects:
That is our report for the week. Lots going on, lots of momentum building. See you all on the new forum!
WAVES Weekly No.26
The recent interview with Lootz on Core Media Radio gives a large amount of up-to-date information about Waves’ tech, developments and timelines.
Conferences and Meet-ups
As the Waves platform nears a state of readiness for mass-user adoption and mainstream business applications, we are broadly switching the focus from tech to business development. Although development will of course continue, the key elements of the platform are now almost complete, which allows us to concentrate more on business relationships.
We are also gaining attention through conferences and other events. The coming week will see another Moscow blockchain developers meet-up, hosted on 20 January at the Digital October Center, where Waves has its offices. Later in the month, there will be a ‘State of Bitcoin’ conference in Moscow with a number of major banks and other institutions.
Waves will have a presence at Blockchain Expo, a convention of more than 1,500 people active in the cryptocurrency world at London’s Olympia, to be held on 23–24 January. Sasha and members of the team will attend to network with some of the biggest names and projects in the blockchain and payments processing world. This will be part of the larger London Blockchain Week, in which Sasha will be participating in panel discussions and other activities.
DEX and Gateways
Waves’ decentralised exchange (DEX) is functional and being tested. Buy/sell orders can be created and placed in the OrderBook via the API on testnet. The backend is essentially ready now, with only a few minor known bugs to be fixed to improve the API. As ever, community members are invited to help with testing and bounties are available for successful bug hunters. The priority now is to create a user-friendly frontend for integration into the lite client.
Alongside this, the first gateways are being created. The bitcoin gateway will be first (via Coinomat), with current estimates being launch at the end of the month or beginning of February. After this will be a Euro gateway through a payments partner. These will allow users to swap BTC and Euros for secure tokens that are 100% backed by their respective currencies, which can then be traded on Waves DEX. USD come by further down the line. Once we have established the proof of concept and tested it thoroughly, responsibility for fiat gateways can be outsourced to larger financial organisations.
Additionally, work is continuing on LPoS, Waves’ leased proof-of-stake algorithm. As well as being able to lease WAVES, it will ultimately be possible to lease CATs too. In the future, Waves will implement smart contracts. Every mainstream blockchain platform needs some form of smart contracts, but Ethereum has taught us that caution is necessary. Likely Waves will use some form of non-Turing-complete scripting.
You can find out more about our first scaling strategy and coming tech updates in this post.
The first tranche of Waves Community Tokens (WCT) was distributed to WAVES holders on Monday. You can find out more about WCT here. Please remember for future (monthly) distributions that only WAVES held off-exchange are eligible. Ownership of WCT will be the basis for the coming BTC distribution from the Byteball windfall. These bitcoin tokens will be withdrawable as BTC through the coming bitcoin gateway.
Our Waves challenge is still running. We have a first prize of 1,000 WAVES, plus Waves t-shirts and stickers for runners-up. Read this post for more details.
Waves Nodes and Lite Client Reminders
If you would like to run a full node, please download the latest releases at https://github.com/wavesplatform/Waves/releases/. Anyone can run a node, but you will need at least 10,000 WAVES to generate blocks. You can read the installation guide here.
For regular users the Lite client can be downloaded from https://wavesplatform.com. Do not download the client from other sources for security reasons. (Please be aware that there have been issues with fake github repositories, as well as fake Twitter accounts and Slack identities.) Alternatively, the standalone Chrome app will automatically update as new versions are released.
Waves Weekly Crypto Round-up
We’re back with Grace Watson for episode #14. This week, we’ve got our usual round-up of the global markets, Brian gives a great overview of the long-term picture for bitcoin, we have a segment with Sasha from the Waves offices in Moscow, and an interview with Michael and Gabriel from the Tokes platform.
Reward system: 180Min PPLNS Commission: 0% on the start Regular payouts Min XMR to payout: 1 XMR Supported clients: Claymore, tsiv, Wolf Support SSL connections Supported mining directly to exchange wallet Efficient, optimized backend Detailed per worker statistics Rigs monitoring by email notifications Usefull API
Coming soon: Zcash (“MagicBean”) 1.0.5
Folks, you can see our development process in action here: zcash/zcash
For example, if you click on the "1.0.5" Milestone, you'll see this:
From this page you can tell when 1.0.5 is due to be released (January
23!) and what bugfixes and improvements are going to be included in it.
You can also see which patches are already written (in case you want to
beta-test specific fixes), if users have been making requests or
reporting bugs, etc.
One thing you can't see from that is what's the "summary" or
"the general idea" of the release. For 1.0.5, I'm not sure what the
"general idea" is. Maybe it is just "various bugfixes and usability
improvements suggested by the feedback we're getting from users".
The rippled team has released version 0.40.1, which increases SQLite database limits in all rippled full-history servers. Ripple recommends upgrading to 0.40.1 only if server operators are running rippled servers with full-history of the ledger. There are no new or updated features in the 0.40.1 release.
If you operate a rippled server and have full-history of the ledger, then you should upgrade to 0.40.1 immediately.
Impact of Not Upgrading
If you operate a rippled server and have full-history of the ledger, but don’t upgrade to version 0.40.1, then your server may crash when restarted.
Tom Kysar This past week we addressed many bug fixes and tweaks around the app, along with improved unit testing and the near completion of a new system for transaction relaying. A large part of the user actions within the UI have been simplified and refactored, removing nearly 15,000 lines of code. This will be pushed within the next day, and then it’s onto skinning the remaining pages within the front-end. Joey is working on three remaining tasks before security audits: the contract updating functionality, a new trading system that handles worst case loss appropriately, and changing the system to allow event creation during forks. Progress is continuing to be made, and if you’d like a real time day by day of what we’re working on, come join us in Slack January 10, 2017
Added an optional “trade-group ID” parameter to all
on-contract trading functions: buy, sell, short_sell, shortAsk, and
trade, as well as the log_add_tx, log_fill_tx, and
log_short_fill_tx events. Also added support for trade group ID in
augur.js and the front-end. Trade group ID is a UUID assigned to
each trade by the front-end, and is used to track (after-the-fact)
which trades were placed as part of the same trade group or “meta-trade”
in the UI.
Updated reveal-reports, load-reports, commit-report,
logout, place-trade, short-sell, and trade tests. All previously
existing tests have now been updated for the transaction changes!
Refactored place-trade: the “taker actions” (placeBuy,
placeSell, and placeShortSell) are now in a separate file,
Added Buffer support to the serialize utility in augur.js.
The unit test suite for augur.js has been significantly expanded.
Added loginWithMasterKey to augur.js accounts unit tests.
Renamed the “web” submodule of augur.js to “accounts”. The old reference will continue to work for the time being.
January 9, 2017
Added unit tests for the new winning-positions selector.
Updated price-time-series and claim-proceeds unit tests.
Changed scrollbars to auto-display when needed.
Adjusted tooltip padding.
January 8, 2017
The cash contract now fires a sentCash event when the send or sendFrom functions complete successfully. Supporting code has been added to the front-end listeners, the filters event formatter, and the transaction relay to listen for, parse, and automatically show on the transactions page.
In-progress transaction messaging for closing out complete sets, “send” funds transactions (ether, real ether, and reputation), and initial order book generation is now handled entirely by the transaction relayer. (Note: initial order book generation is currently not exposed in the UI.)
Simplified the transactions module by removing two unnecessary methods (updateExistingTransaction and processTransactions).
January 7, 2017
Removed extraneous description fields from augur.js wrapper functions. Descriptions are now handled by the relayer.
Added isShortAsk parameter to on-contract sell function and its associated log_add_tx event. The log_add_tx and log_short_fill_tx filters in augur.js autoconvert isShortAsk to a boolean value.
Fixed final numMarketsToLoad value for descending loadMarkets.
Added always-in-progress flag to relayed commitTrade transactions.
Removed duplicate trading fees display in bid/ask/shortAsk transactions.
Added isShortAsk field to relayed shortAsk transactions.
Fixed short sell and short ask messaging. Added log_short_fill_tx as a separate relayed transaction label.
Simplified trade simulation setup by inlining the trade and short sell “transaction” objects. Removed unused add-short-sell-transaction and add-trade-transaction files.
January 6, 2017
The Transaction component no longer has separate commit-to-buy/sell types. These types now simply use the trade type the user is committing to.
The transaction relayer now automatically fills in all fields for commit-trade, trade, and short-sell transactions by using the new, more detailed trade info fields attached to the tradeCommitment data store.
Default “scaffolding” transaction updates have been removed from the relayer.
Fixed in-progress vs completed messages for log_fill_tx.
Assignment to the gasFees field now works correctly for relayed and logged trading transactions.
Removed unnecessary dispatches from placeTrade and its subroutines.
Added trade arguments and orders to the tradeCommitment datastore.
The initial funding transaction log is now loaded alongside the registration timestamp transaction log.
Replaced the ugly monster header with a “regular” header in the transactions view.
January 5, 2017
The messaging for trade, short_sell, and commitTrade transactions is now handled by the transaction relayer. Deprecated manual transsaction messaging for these functions have been removed.
Refactored place-trade: removed dispatcher from placeAsk, placeBid, placeShortAsk, and parametrizeOrder functions, and moved these functions to trade/actions/make-order.
Simplified the selectScalarMinimum function and moved it to market/selectors/market.
January 4, 2017
Replaced manual transaction processors for trades (buy/sell); refactored and simplified placeTrade.
Simplified default message generator in registerTransactionRelay.
Removed unused disableAutoMessage transaction property.
Fixed bond object in constructMarketCreatedTransaction; fixed constructMarketTransaction parameters; moved marketCreated label out of constructMarketTransaction group.
Consolidated create market actions into submitNewMarket; removed manual create market transaction updates.
Fixed adjusted-maker-fee calculation in constructLogAddTxTransaction.
Added gasFees field to trading transactions in constructRelayTransaction.
Added missing arguments to cancel in contructRelayTransaction.
Discussion with Colu on Lightning network compatibilityUpdates for Omni portImproving external communicationsDEx volume and automationDEx tutorialCore.ID discussion / protocol needs
Omniwallet SupportStarting to look into multisig/hardware wallets
Reviewed and merged fee related pull requests from Zathras:
https://github.com/OmniLayer/o...https://github.com/OmniLayer/o...Sanitized RPC responses to replace non-UTF-8 compliant characters:
https://github.com/OmniLayer/o...Reviewed backports of fixes and performance improvements for 0.0.11.3 from Zathras:
https://github.com/OmniLayer/o...Ported code base to Bitcoin Core 0.13.2:
Recovered from another OC node failureAdded token distribution statistics feature as requested (just choose ‘Click to view statistics’ when viewing any property)
Still trying to pin down exact circumstances that trigger node crash, still difficulty replicating, moved testing to Windows OSBackported several fixes back to 0.0.11 for point release (https://github.com/OmniLayer/omnicore/pull/449)Further progress on Omni Core port
requests increasing, likely due to increasing usage of Omni Layer
technologies (transaction vol has almost doubled in last month alone)Investigating Sean/Adam’s new ideas around DEx1 (CSV, CLTV etc)
Bug fixes, code cleanup for upcoming 0.2.2 release
Big fixes, code cleanup for upcoming 0.5.1 release0.5.1 will also have optimized Omniwallet REST balance queries
Bug fixes and updates for upcoming 0.1.2 release0.1.2 release will use OmniJ 0.5.1 and bitcoinj-addons 0.2.2
Ongoing Communication with projects
2016 was a great year for OKCash, and 2017 OKCash will continue making history :) For that we got alot of things ins store. Besides the great development progress at the different projects like OK Embassy and OKMap there are some other goals to achieve. For that we will have to work together and try to collect as many donations as possible to make it happen 8) We will need to collect around 5 BTC to get integrated in the following projects and to get things done:
Bitcoin: 1K9EX4UqVo8yeADRoaYTH5DHvvLjRHes1M [/b]
[b]Thank you very much for every donation and for you beeing a part of the OKcash community[/b] ;)