mirror of
https://github.com/seigler/dash-website
synced 2025-07-27 07:16:10 +00:00
Merge branch 'master' of https://github.com/tungfa/dash-website
# By tungfa # Via tungfa * 'master' of https://github.com/tungfa/dash-website: CoPay Pt New Post CoPay News Posting link fixed naming fixed image moved Test 2 - Written Story + Image Test Post - Ryan Video
This commit is contained in:
commit
7023b48e11
7 changed files with 184 additions and 0 deletions
76
_i18n/en/_posts/2017-01-31-TheDosandDonts.md
Normal file
76
_i18n/en/_posts/2017-01-31-TheDosandDonts.md
Normal file
|
@ -0,0 +1,76 @@
|
|||
---
|
||||
author: tungfa
|
||||
layout: post
|
||||
image: TheDosandDonts.jpg
|
||||
title: The Dos and Don'ts of Pushing Crypto: Evangelist John Bush
|
||||
---
|
||||
While Bitcoin value and use continue to grow year after year, cryptocurrency is still a far cry from total main street adoption.
|
||||
|
||||
While some online heavy hitters such as Overstock and Amazon through Purse.io significantly improve the usability of cryptocurrency, the average storefront business anywhere in the world will likely not accept digital currencies. CoinMap lists barely over 8,500 Bitcoin-accepting businesses worldwide. Cryptocurrency evangelists have their work cut out for them.
|
||||
|
||||
Cointelegraph spoke to John Bush, owner of Brave New Books and head of the Dash to Adoption project, about the dos and don’ts of the cryptocurrency adoption strategy that he learned during his push to get new businesses to accept Dash.
|
||||
|
||||
Knowing people
|
||||
|
||||
Cointelegraph: What were your goals coming into the adoption push?
|
||||
|
||||
John Bush: My goal was to help 100 businesses get set up to accept Dash within 100 days. I also wanted to study the ecosystem in order to determine best practices for furthering adoption
|
||||
|
||||
CT: How were your results?
|
||||
|
||||
JB: I ended up falling quite short of my goal. I was able to sign up 24 businesses with several others who committed but haven't finalized the setup. I am still working to complete the 100 businesses but it will take well more than 100 days. I'd be happy to reach 100 in 200 days. As I said before the campaign was approved, whether I make the goal or not, I will continue to work towards the original goal of 100.
|
||||
|
||||
CT: What was the main component of the project's success that you underestimated?
|
||||
|
||||
JB: Time. I was expecting a better closing rate than what I had. I reached out to thousands of businesses and only a small percentage of them responded and a smaller number responded with interest. More time would mean more potential businesses reached. I honestly thought it would be easier to reach businesses that already accept Bitcoin. Perhaps not having many Bitcoin customers led them to not be so excited about a new cryptocurrency.
|
||||
|
||||
CT: Which were the easiest businesses to reach?
|
||||
|
||||
JB: Businesses owned by people I know personally!
|
||||
|
||||
CT: And the most difficult?
|
||||
|
||||
JB: Businesses that did not accept cryptocurrency.
|
||||
|
||||
Gateway drug
|
||||
|
||||
CT: Then is it fair to say that Bitcoin is the "gateway drug" to other coins?
|
||||
|
||||
JB: I would like to think so. One of the hangups I had with Dash was the lack of a solid tool for utilizing InstantSend. One of the few ways to make this happen is to use the Core Client, but of course, customers aren't walking around with their laptop so there often wasn't a way for the customer to send using InstantSend.
|
||||
|
||||
CT: Have you had any success in taking businesses from zero to Dash, or is Bitcoin-first a must?
|
||||
|
||||
JB: I did have some success with crypto noobs.
|
||||
|
||||
"Many of my friends who are business owners setup Dash before ever accepting Bitcoin."
|
||||
|
||||
CT: So do you think other coins can gain direct public acceptance without having to field the "But what about Bitcoin" question?
|
||||
|
||||
JB: I do, once InstantSend is more widely available I think Dash will stand out as a cryptocurrency with great value for businesses.
|
||||
|
||||
CT: What proved to be a winning approach to get businesses on board?
|
||||
|
||||
JB: Start with people you know and work from there.
|
||||
|
||||
CT: How did you approach them? Email, call? What did you say?
|
||||
|
||||
JB: For businesses I knew or that were within my sphere of influence I gave a phone call. For businesses I was not familiar with, I sent an email that I would vary slightly depending on the industry.
|
||||
|
||||
"I related the benefits of Dash and the exposure the business would get for adding a new currency. I shared a YouTube video I produced to help explain the benefits. Then I followed up and engaged further if they were interested."
|
||||
|
||||
The biggest selling point
|
||||
|
||||
CT: What was your single biggest selling point? The one reason businesses should adopt cryptocurrency.
|
||||
|
||||
JB: The number one selling point for businesses to accept cryptocurrency is to be a pioneer in the space of digital currency and attract new clients to their businesses. A close runner-up is the ability to receive your money almost instantly instead of waiting days for credit card money to deposit.
|
||||
|
||||
CT: What was one approach/line that didn't work?
|
||||
|
||||
JB: The cold email was less effective than a phone call of course. There is an old adage in organizing and sales that one handshake is worth ten phone calls is worth 100 emails.
|
||||
|
||||
CT: How optimistic are you about cryptocurrency adoption among the general economy?
|
||||
|
||||
JB: I am optimistic that eventually, in the long run, cryptocurrency will be widely adopted. I think it is inevitable. In the short term, however, with entrepreneurs focused on short term goals and most always overloaded. I don't think the value proposition exists for mass adoption to come soon.
|
||||
|
||||
<https://cointelegraph.com/news/the-dos-and-donts-of-pushing-crypto-evangelist-john-bush>
|
||||
|
7
_i18n/en/_posts/2017-01-31-ryan-video.md
Normal file
7
_i18n/en/_posts/2017-01-31-ryan-video.md
Normal file
|
@ -0,0 +1,7 @@
|
|||
---
|
||||
author: tungfa
|
||||
layout: post
|
||||
image:
|
||||
title: Future of DASH Cryptocurrency : Ryan Taylor (Director of Finance)
|
||||
---
|
||||
<iframe width="560" height="315" src="https://www.youtube.com/embed/U7wv2zozTCY" frameborder="0" allowfullscreen></iframe>
|
31
_i18n/en/_posts/2017-02-01-copay.md
Normal file
31
_i18n/en/_posts/2017-02-01-copay.md
Normal file
|
@ -0,0 +1,31 @@
|
|||
---
|
||||
author: tungfa
|
||||
layout: post
|
||||
image: CoPayWalletcopy.jpg
|
||||
title: Copay-Dash Wallet (Testnet Only / RC 0.1)
|
||||
---
|
||||
I’m happy to announce a “Release Candidate” version of Copay-Dash, a variant of the Copay wallet which was originally developed by Bitpay.
|
||||
|
||||
Besides the usual characteristics of other wallets, this fully-featured app boasts:
|
||||
- The ability to access multiple Dash wallets within a single app
|
||||
- HD-Multisignature Wallet Derivation (BIP32/BIP44)
|
||||
- Exchange Rate Calculation (150+ currencies)
|
||||
- Multilanguage Support
|
||||
- Streamlined User Interface
|
||||
|
||||
Copay is available for all major operating systems, both desktop and mobile, however at the moment the Dash version will be made available only as a Chrome extension. This release has undergone preliminary testing but at this stage is intended only for Testnet. Once we’ve achieved 100% stability we plan on distributing builds supporting additional platforms.
|
||||
|
||||
You can read more about Copay at <https://copay.io>.
|
||||
|
||||
Backend Mechanics
|
||||
|
||||
This wallet is powered by Bitcore Wallet Service <https://github.com/dashpay/bitcore-wallet-service-dash> and uses a centralized server to do the heavy lifting. This server maintains a full copy of the blockchain and provides notifications to connected clients when transactions affecting their wallet occurs, similar to how an Electrum Server operates. It’s worth noting that despite this “client-server” relationship, your private keys are always held locally and are never revealed to the centralized server.
|
||||
|
||||
Copay-Dash is able to maintain this “untrusted” relationship with the wallet server through the use of Bitcore Wallet Client <https://github.com/dashpay/bitcore-wallet-client-dash>. This collection of client-side libraries allows for the signing of Transactions and creation of Wallets to occur via API.
|
||||
|
||||
|
||||
Installation Info
|
||||
Download Copay-Dash Chrome Extension
|
||||
<http://download.slayer.work/copay-dash-chrome-extension.zip>
|
||||
“How To” install Chrome Extensions
|
||||
<http://www.howtogeek.com/233355/how-to-install-extensions-from-outside-the-chrome-web-store-and-firefox-add-ons-gallery/>
|
25
_i18n/pt/_posts/2017-02-01-copaypt.md
Normal file
25
_i18n/pt/_posts/2017-02-01-copaypt.md
Normal file
|
@ -0,0 +1,25 @@
|
|||
---
|
||||
author: tungfa
|
||||
layout: post
|
||||
image: CoPayWalletcopy.jpg
|
||||
title: Copay-Dash Wallet (Testnet só / RC 0.1)
|
||||
---
|
||||
Estou feliz em anunciar uma versão “Release Candidate” da Copay-Dash, uma carteira Copay que foi desenvolvida pela Bitpay.
|
||||
Além das características habituais de outras carteiras, este aplicativo com todas as características possui:
|
||||
A capacidade de acessar várias carteiras do Dash dentro de um único aplicativo
|
||||
- HD-Multisignature Wallet (BIP32/BIP44)
|
||||
- Cálculo da taxa de câmbio (150 moedas)
|
||||
- Suporte a vários idiomas
|
||||
- Interface de usuário simplificada
|
||||
|
||||
O Copay está disponível para todos os principais sistemas operacionais, tanto para desktop quanto para mobile, no entanto, no momento em que a versão Dash será disponibilizada apenas como extensão do Chrome. Esta versão passou por testes preliminares, mas nesta fase destina-se somente para Testnet. Uma vez que atingimos 100% de estabilidade, planejamos distribuir versões que suportem plataformas adicionais.
|
||||
Você pode ler mais sobre Copay em <https://copay.io>.
|
||||
|
||||
Esta carteira é alimentada com Bitcore Wallet Service e usa um servidor centralizado para fazer o trabalho pesado. Esse servidor mantém uma cópia completa do blockchain e fornece notificações aos clientes conectados quando ocorrem transações que afetam sua carteira, semelhante à operação de um Servidor Eletrônico. Vale a pena notar que, apesar deste relacionamento “cliente-servidor”, suas chaves privadas sempre são mantidas localmente e nunca são reveladas ao servidor centralizado.
|
||||
Instalation Info
|
||||
|
||||
Installation Info
|
||||
Download Copay-Dash Chrome Extension
|
||||
<http://download.slayer.work/copay-dash-chrome-extension.zip>
|
||||
“How To” install Chrome Extensions
|
||||
<http://www.howtogeek.com/233355/how-to-install-extensions-from-outside-the-chrome-web-store-and-firefox-add-ons-gallery/>
|
BIN
assets/img/blog/CoPayWalletcopy.jpg
Normal file
BIN
assets/img/blog/CoPayWalletcopy.jpg
Normal file
Binary file not shown.
After Width: | Height: | Size: 240 KiB |
BIN
assets/img/blog/TheDosandDonts.jpg
Normal file
BIN
assets/img/blog/TheDosandDonts.jpg
Normal file
Binary file not shown.
After Width: | Height: | Size: 88 KiB |
45
npm-debug.log
Normal file
45
npm-debug.log
Normal file
|
@ -0,0 +1,45 @@
|
|||
0 info it worked if it ends with ok
|
||||
1 verbose cli [ '/usr/local/bin/node', '/usr/local/bin/npm', 'start' ]
|
||||
2 info using npm@3.10.10
|
||||
3 info using node@v6.9.4
|
||||
4 verbose run-script [ 'prestart', 'start', 'poststart' ]
|
||||
5 info lifecycle dash-website@1.0.0~prestart: dash-website@1.0.0
|
||||
6 silly lifecycle dash-website@1.0.0~prestart: no script for prestart, continuing
|
||||
7 info lifecycle dash-website@1.0.0~start: dash-website@1.0.0
|
||||
8 verbose lifecycle dash-website@1.0.0~start: unsafe-perm in lifecycle true
|
||||
9 verbose lifecycle dash-website@1.0.0~start: PATH: /usr/local/lib/node_modules/npm/bin/node-gyp-bin:/Users/jezuzjezuz/Desktop/dash-website - tungfa/node_modules/.bin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/opt/X11/bin:/usr/local/MacGPG2/bin
|
||||
10 verbose lifecycle dash-website@1.0.0~start: CWD: /Users/jezuzjezuz/Desktop/dash-website - tungfa
|
||||
11 silly lifecycle dash-website@1.0.0~start: Args: [ '-c', 'npm run build -s && npm run watch' ]
|
||||
12 silly lifecycle dash-website@1.0.0~start: Returned: code: 1 signal: null
|
||||
13 info lifecycle dash-website@1.0.0~start: Failed to exec start script
|
||||
14 verbose stack Error: dash-website@1.0.0 start: `npm run build -s && npm run watch`
|
||||
14 verbose stack Exit status 1
|
||||
14 verbose stack at EventEmitter.<anonymous> (/usr/local/lib/node_modules/npm/lib/utils/lifecycle.js:255:16)
|
||||
14 verbose stack at emitTwo (events.js:106:13)
|
||||
14 verbose stack at EventEmitter.emit (events.js:191:7)
|
||||
14 verbose stack at ChildProcess.<anonymous> (/usr/local/lib/node_modules/npm/lib/utils/spawn.js:40:14)
|
||||
14 verbose stack at emitTwo (events.js:106:13)
|
||||
14 verbose stack at ChildProcess.emit (events.js:191:7)
|
||||
14 verbose stack at maybeClose (internal/child_process.js:877:16)
|
||||
14 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:226:5)
|
||||
15 verbose pkgid dash-website@1.0.0
|
||||
16 verbose cwd /Users/jezuzjezuz/Desktop/dash-website - tungfa
|
||||
17 error Darwin 16.4.0
|
||||
18 error argv "/usr/local/bin/node" "/usr/local/bin/npm" "start"
|
||||
19 error node v6.9.4
|
||||
20 error npm v3.10.10
|
||||
21 error code ELIFECYCLE
|
||||
22 error dash-website@1.0.0 start: `npm run build -s && npm run watch`
|
||||
22 error Exit status 1
|
||||
23 error Failed at the dash-website@1.0.0 start script 'npm run build -s && npm run watch'.
|
||||
23 error Make sure you have the latest version of node.js and npm installed.
|
||||
23 error If you do, this is most likely a problem with the dash-website package,
|
||||
23 error not with npm itself.
|
||||
23 error Tell the author that this fails on your system:
|
||||
23 error npm run build -s && npm run watch
|
||||
23 error You can get information on how to open an issue for this project with:
|
||||
23 error npm bugs dash-website
|
||||
23 error Or if that isn't available, you can get their info via:
|
||||
23 error npm owner ls dash-website
|
||||
23 error There is likely additional logging output above.
|
||||
24 verbose exit [ 1, true ]
|
Loading…
Add table
Add a link
Reference in a new issue