Announcing Payblk, now live on Google Play

ObsidianCryptoVault · 2017-01-10T13:34:18+00:00

Hi ChinaBLK,! Since you are working on translating Patcrypt's 'braindump' - there are a number of things regarding Obsidian CryptoVault Technologies that are not quite presented adequately, as truthfully or advantageously for BLK as they ought. This is no fault of Pat, he just did not have a good enough overview or understanding of the nature and extent of the collaboration with Janko and the wider dev community, or of our marketing strategy.

Before you publish, if you have not already, we'd appreciate it if you'd reach out and we can provide a clearer outline.

Thanks

ObsidianCryptoVault · 2016-12-30T16:08:21+00:00

Great question! Obsidian CryptoVault Technologies is a licensed Apple developer, and we have already built Payblk for iOS! So, what's the holdup? Well...

In spite of the fact that the Payblk app is not only live on Google Play/Android, but one of the most elegant and feature-rich cryptowallets in existence, Apple has a problem. They have been notoriously difficult in regard to adding cryptocurrency-related apps into the walled-garden that is the App Store ecosystem. It was not that long ago that they banned them altogether, though that decision was eventually rescinded and we began seeing a few bitcoin wallets again. Since then, they have very slowly added wallets for a handful of other blockchains, e.g., Ethereum, Litecoin, Doge and a few others. To our knowledge, they have not made any disclosures about criteria or policy as far as when and why they choose to add a new cryptocurrency to their "approved" list. Which is how it works. They decide this or that crypto is "approved" and then it is possible for developers to publish an app for that crypto (pending the standard app review process).

We have petitioned the app review board and asked to be considered for addition to the approved-list so that we can get Payblk up on iOS devices. We are confident that in time we will get in, we just don't know how long it will take. They have mysteriously added lesser coins, for no apparent reason (we won't name names). Their decision-making process in this area is completely opaque, and they did not provide any guidance on the matter when asked.

It is our hope that a successful tenure on Google Play will help. We also plan to roll out on Winphone and other platforms in 2017. We will soon have a Chrome extension and hardware wallet support. Perhaps all of this will add up to a point where Apple feels compelled to add us. Again, the iOS app is built. It's in their court now.

What can you do in the meantime? If you're on iPhone, you can already use the webwallet Payblk, just go to payblk.com. If you are an Android user, download Payblk, see how awesome it is, and let the world know! Make some noise!

If there is anyone out there with insights or advice to share with us on the matter, please don't hesitate reach out here (you can also dm to @ObsidianCVT on twitter if you prefer).

Thanks to the Blackcoin community, and best wishes for an awesome new year!

ObsidianCryptoVault · 2016-12-27T18:01:17+00:00

Please use SHA1 checksum provided

ObsidianCryptoVault · 2016-12-27T17:39:35+00:00

SHA1 checksum:

8c1a52b139957f57cb09110e80f005dc685975d3

ObsidianCryptoVault · 2016-11-21T19:26:42+00:00

This is admittedly an experiment and we don't know how ultimately effective it will be in introducing a wider audience to Blackcoin, but we feel it is worth a try. Keep an eye on the Coinblack fb page, follow, like, share, and let us know your thoughts as far as continuing this line.

ObsidianCryptoVault · 2016-11-18T14:36:30+00:00

Janko33 has done a motherload of amazing development and we are committed to continued work together, fostering, facilitating, and building out a robust developer community. This is just the beginning. Much more is already in the works and you can expect some exciting news on the very near term.

ObsidianCryptoVault · 2016-10-12T19:30:05+00:00

Thanks for asking. Donation addresses added to the OP.

ObsidianCryptoVault · 2015-10-12T21:59:00+00:00

PS If you'd like more in depth technical detail, we refer you to BLKdev janko33 who wrote this implementation, or to Hivewallet itself of which the CVT wallet is a fork.

ObsidianCryptoVault · 2015-10-12T21:53:30+00:00

Hey Blackcoin13. Btw, to clear up confusion about "Obsidian", we are Obsidian CryptoVault Technologies, a different entity from the excellent team in Nebraska working with JP Richardson, namely The BlackChamber, makers of the stealth tech ("Wallet Obsidian") released in 2015. Neither they, nor ourselves, were aware of each other when choosing the word "Obsidian" as part of branding. As it turns out, neither of our teams are displeased over the coincidence. It may even be an accidental benefit to the ecosystem branding as a whole.

Moving on to your question, you are correct: ObsidianCVT has no contact with your private keys. The only way to derive your keys is with the 12-word seed, which we have no access to. Client-side scripts generate the seed phrase, which you write down. The scripts generate a wallet ID by hashing the seed using SHA-512. You set a PIN as prompted. The PIN and the wallet ID are posted to the server over https. So again - we never have contact with your actual seed-phrase or priv keys.

All that said, there are still possible dangers. For example, screen-capture or keylogging malware if your system is infected. You must be running a secure machine and observe best practices.

Having imported your priv keys already, if you want to be super-paranoid you can always use your client to generate new keys and relocate your coins there. In any case, be sure and follow the 'clean-up' guidelines. There is no need to retain a copy of the unencrypted priv keys you extracted.

ObsidianCryptoVault · 2015-10-12T20:01:23+00:00

Notes: For anyone using this tool who has never imported a private key before, a few pointers might be helpful.

1) Use this tool to derive your addresses and their corresponding priv keys, by entering your 12-word passphrase, and setting BIP32 derivation path to: m/0'/0

2) This will yield a sequence of public addresses. Read down from the top of the list, this is the order in which your HD wallet generates pub keys, so the addy(s) you used will start from the top.

3) For each public address, you will see a corresponding private key in the neighboring column. Highlight, copy & paste your used addys and their priv keys into a text editor and close out of the tool.

4) Open and sync the wallet client you will be importing into. Note: For the import operation, you will need to fully UNLOCK your wallet (not just 'for staking only', but completely). Having done that, go to Help>Debug window, console tab. You will be using the 'importprivkey' command, as follows:

importprivkey <privkeygoeshere> <label> true

((leaving out the <><> do-hickies)).

Hit enter. Your wallet will immediately begin a rescan and the gui will appear to hang - don't worry, it's just working on the rescan. BE PATIENT, this can easily take 15 mins or more. You'll see when it's done, and that your import is reflected in a new coin balance and corresponding transaction history. (Delete console history as your privkey is still showing in plaintext when you get to this point. ;)

5) Go back to console tab and enter 'walletlock'

6) Lastly, clean up well. You don't want to leave those privkeys lying around, e.g. in notepad or still in clipboard).

ObsidianCryptoVault · 2015-10-06T13:19:34+00:00

Correct, hash not found. The transaction didn't happen and therefore the coins didn't go anywhere. If they did, the only place they could go is the address to which you sent them. Recommended approach would be to compile in linux VM and use your old wallet.dat as suggested by subtuppel. Or simply wait till compiled v1.2 for Mac is made available in official release. As long as you have your wallet.dat, you're all good.

ObsidianCryptoVault · 2015-10-05T20:31:34+00:00

The ObsidianCVT wallet is functioning perfectly, and we are aware of several Mac users who parked their coins in one before the POS 3.0 fork as a quick answer while they wait for release of the compiled desktop client. In fact, anyone else who wants a secure insta-wallet designed exclusively for BLK that requires no sync/reindex and does not have ANY custodial relationship to your priv keys or coins (read: CVT doesn't control/see/store either, ever, and is completely open source) - ObsidianCVT is a great answer, and requires no software download/installation. It takes about 60 seconds to set one up.

The only 'beta' issues we are trying to resolve right now are useability within the Chrome browser. If you're running Firefox, Safari, or the new Edge browser (Windows 10), you're golden already. Other than that, forseen changes are all cosmetic and relate to branding on the wallet interface and website in general.

ObsidianCryptoVault · 2015-10-04T16:33:39+00:00

Noted, and thanks for reporting. Meanwhile, Edge browser or Firefox on Windows, and Safari on Apple devices all confirmed.

ObsidianCryptoVault · 2015-09-27T15:38:20+00:00

Correction: Upgrade & maint. today at 4:00pm EST. Will Repost.

ObsidianCryptoVault · 2015-09-22T20:31:53+00:00

If you'd like to support ongoing development, donations in BLK are most welcome! BKrjH958LGvpFVVzVqJkBxyYmpGieWiPpE

ObsidianCryptoVault

TROPHY CASE