I'd rather pay with with utility isEvenCoins, rather than with USD.<p>Also, our entire stack is GraphQL-based, so we must have a GraphQL API according to this schema:<p><pre><code> schema {
query: Query
mutation: Mutation
subscription: Subscription
}
type Query {
balance: Int!
isEven(input: isEvenInput!): isEvenPayload!
}
type Mutation {
depositCoins(amount: Int!): DepositPayload!
withdrawCoins(amount: Int!): WithdrawPayload!
}
type Subscription {
coinsDeposited: Int!
coinsWithdrawn: Int!
coinsSpent: Int!
}
input isEvenInput {
number: Int!
gas: Int!
}
type isEvenPayload {
result: bool
balanceLeft: Int!
isError: bool!
errMsg: String
}
type DepositPayload {
newBalance: Int!
isError: bool!
errMsg: String
}
type WithdrawPayload {
newBalance: Int!
isError: bool!
errMsg: String
}</code></pre>
I think you need a dashboard with animated graphs (preferably in bright colors on a dark background with thin text that has just enough color contrast to indicate that there's text there at all) to help track KPIs. With push notifications if even/odd distributions veer outside of a user-defined threshold, which is cunningly defined as an index value with a more impressive sounding name and handy three letter abbreviation.<p>That should really help distinguish yourself in this hotly contested market space.
I got tired of seeing programmers struggle to tell if a given number is even, so I built this solution.<p>You can see an example here:
<a href="https://github.com/BraydonKains/is-even/blob/master/python.md#iseven-api" rel="nofollow">https://github.com/BraydonKains/is-even/blob/master/python.m...</a><p>I'll be around for questions!
It appears that the API is unversioned, which concerns me as my company is very future-looking and will need to support numbers as they modernize. How will you handle version migrations?