Ternio is responsible for the development of Block Card™, a prepaid crypto debit card accepted anywhere that VISA is accepted. We are uniquely positioned as having been one of the first providers approved in the US. We offer a whitelabel, API based solution for third party partners to directly integrate our underlying technology and platform and provide fiat on and off ramps for the greater crypto community. Our newest product is a full fledged, US based checking account. We'll be international by end of Q4 with other fiat on and off ramps. We're profitable, growing rapidly, and get to tackle interesting problems bridging traditional banking and cryptocurrency.
## ROLES
We're looking for a variety of roles, including:
* Full stack generalists specializing in JavaScript (node.js, express.js, Typescript)
* A lead developer (US based only)
* A senior cloud ops engineering looking to wrangle our sysadmin needs (and have a say in devops procedures)
## STACK
You can find a healthy mix of Ubuntu, AWS, Typescript, express.js, node.js, Laravel, Vue.js, Postgres, Redis, websockets, core nodes, and third party APIs and SDKs.
Something that always bugged me with cardano's Ouroboros is the name. Ouroboros means eating (usually your own) tail, and the symbol that usually goes with it is a snake/dragon as a loop/circle.
Blockchain is basically an ever expanding chain (or tree if you include the shorter branches that didn't make it) so I can't understand the relation to ouroboros loop/circle.
I assume they have a different reason for naming it that but didn't ever find it.
The fact it's tied to a Keybase wallet is important because Stellar's path payments functionality was just launched on Keybase. To summarize, you can use Keybase to send someone any asset they'd like using any asset you're holding, all on Stellar's decentralized exchange. It happens transparently behind the scenes to convert assets: https://www.stellar.org/developers/horizon/reference/endpoin...
For those of you not on Keybase yet, here's the most important piece of information in the post:
"To qualify: you must have a Keybase account registered before this announcement OR if you're new to Keybase, you must connect your Keybase account to a GitHub or HackerNews account that was registered before this announcement. This is to prevent bot signups to Keybase."
It fails to mention that Github and HN accounts must be older than January 1, 2017. This is what I saw in the app when I tried to join the airdrop: https://i.imgur.com/ZOZ1rB7.png
I hope that's an accidental omission and not an intentional dark pattern.
Not a dark pattern, an accidental leftover string from our testing. Any account registered before today qualifies. I'll deploy a fix to that shortly. Update: deployed, although you may need to restart your app to update the text.
Sucks you had the sign up date prior to the announcement. When I read the announcement I immediately signed up for a keybase, HN and Github account and then find out I cant be included because I signed up on 9/9/2019. You would think that would be the incentive to at least give a little buffer for people to join in that were not aware.
I'm slightly concerned about routing my traffic through a non-major player in Anycast when I don't control the routing or software. I'd be worried it's quite an easy target for someone to do some DNS hijacking or packet sniffing.
There's a certain level of trust when I use 1.1.1.1 or 8.8.8.8. I'm unwilling to take the risk for this solution. I'm not sure what would help in the trust department to legitimize a solution like this.
I would bet on too much screen time for the whole family; seen it first hand. Parents sitting on their devices all evening and not interacting with their children. It's a missed opportunity for learning, especially at a young age.
That's a disturbing image I hadn't considered. The parents I know (mainly CS people) have talked for years about "limiting screen time" of the kids, but I didn't consider that some other parents might have too much screen time themselves, to the point of shortchanging child early development.
My two major gripes are that it's first hitting the UK market and it has liquidation fees associated.
I agree with the premise that we shouldn't need to convert to fiat but unfortunately we have to follow the pace of adoption. You could create a POS device tied to a service that accepts crypto-only via chip and pin or magnetic for the business. I'm doubtful many businesses are hearing from their customers that they want crypto only payments, however.
I lead the development of a crypto debit card in the US. If anyone has questions, shoot me a message.
https://github.com/cballou/Turntable.FM-Squared