[WTS] WIFI Bitcoin And Altcoin Price Ticker Screen - afkdata.com

[swordfish6975]

Hit a few snags with a payment provider — now waiting on KYB verification with a different one before I can send out the order email to the waitlist.

Good news is the new provider has already passed integration testing on the site, so fingers crossed it's sorted this week.

[DaveF]

Can't we just send you BTC?

-Dave

[swordfish6975]

We will be able to take Bitcoin, just not as a raw send to a random new wallet.

For a Pty Ltd it creates a few practical problems:

We need to match the payment to a specific invoice/customer.
We have to record the AUD value at the time of receipt for tax.
Company custody of keys, backups and access is a real operational issue, not just “here’s an address.”
Unscreened inbound coins can cause problems later if we need to convert or explain the funds.


Australia makes things hard unfortunately.

[Hhampuz]

Can't we just send you BTC?

-Dave

I would suggest getting a cc that you top up with btc instead as that combines the best of both worlds. More annoying than just sending BTC straight to an addy but as swordfish says, regulations and all that crap is really sucky whenever you do business and want to accept crypto.

[DaveF]

BTCPay server and https://plugin-builder.btcpayserver.org/public/plugins

But I get it, dealing with all the other stuff is probably not what you want to spend your day dealing with.
Not to mention keeping everything up and running and dealing with all the other issues around it.

The other side is the paranoid people who will not order from you if you only take CC.
Don't know if that would make a measurable difference in the number of sales you would make.

-Dave

[swordfish6975]

If you were on the waitlist you should have an email 

[MoparMiningLLC]

If you were on the waitlist you should have an email 

got the email but decided not to purchase - did not want to upload "identity papers" to use Bitcoin.

[swordfish6975]

got the email but decided not to purchase - did not want to upload "identity papers" to use Bitcoin.

Understandable — that's RelayPay's compliance step for converting crypto into AUD in our account, not something we're collecting or storing ourselves.

It's clearly costing us sales so I've pushed them on it and I'll post an update here once I hear back (expecting a response this week).

[DaveF]

got the email but decided not to purchase - did not want to upload "identity papers" to use Bitcoin.

Understandable — that's RelayPay's compliance step for converting crypto into AUD in our account, not something we're collecting or storing ourselves.

It's clearly costing us sales so I've pushed them on it and I'll post an update here once I hear back (expecting a response this week).

Not wanting to overstep but would you think it would be worth it to ship a bunch to someone here in the states who could accept personal P2P payments and then pass it to you.
The logistics would probably be a disaster, but it might be worth it if they will not relent on the compliance.

Becomes an is it worth it for how many additional sales.

-Dave

[swordfish6975]

Last time (10 years ago) the largest order was to the US for 11 devices I think, he was reselling them for sure.

[DaveF]

Last time (10 years ago) the largest order was to the US for 11 devices I think, he was reselling them for sure.

I did 4 last time.

Just did 2 now.

-Dave

[tweetious]

@swordfish6975 Which shipping method are you using to ship the devices to Europe (EU)?

When you say “Standard Shipping” does that mean Australia Post, or do you use a private courier such as UPS, DHL, or FedEx?

[swordfish6975]

@swordfish6975 Which shipping method are you using to ship the devices to Europe (EU)?

When you say “Standard Shipping” does that mean Australia Post, or do you use a private courier such as UPS, DHL, or FedEx?

Yep, Standard Australia Post.

For Aussies it usually works out to Express anyway since the price difference is small, but shipping to the rest of the world has gotten pretty pricey — the site pulls rates straight from the Auspost API.

https://auspost.com.au/parcels-mail/calculate-postage-delivery-times/option/international

If you want to double check the numbers yourself, use postcode 4000 (Brisbane City QLD) as the sending address.

| Devices in box | Weight | Length | Width | Height |
| 1 | 0.285 kg | 15.0 cm | 15.0 cm | 7.5 cm |
| 2 | 0.445 kg | 15.0 cm | 15.0 cm | 7.5 cm |

For orders over two, we just split it into multiple parcels, later on we will source some larger boxes.

Keeping it simple for now and sticking with Aus Post — might look at private couriers like UPS/DHL/FedEx down the line.

[MoparMiningLLC]

I am more than willing to handle reshipping to US customers and not so much opposed to you having my info as I am to your govt having copies of my identification

[swordfish6975]

I am more than willing to handle reshipping to US customers and not so much opposed to you having my info as I am to your govt having copies of my identification

Totally fair concern, and we don't take it lightly either. We're working together with our crypto payment processor to come to a solution on the KYC requirement — it's not something we're happy to have as a barrier and we're pushing to get it loosened or removed. Appreciate you flagging it, and we'll post an update here as soon as there's movement.

Quick update on US orders: we've had to pause new orders to the USA for the time being while we work through some added tariff/customs complexity on our end. For the two of you who already ordered from the US, we haven't forgotten about you — we're actively sorting out the tariff situation so we can get your devices shipped, and we'll be in touch directly as that resolves.

[swordfish6975]

Good news — all orders are open again, including the US. For US customers, tariffs will now be charged at checkout — not something we're happy about, but we've found no way around it on our end. Thanks for your patience while we sorted this out.

[swordfish6975]

We've had a response from our payment processor regarding the crypto KYC requirement — unfortunately it has to stay in place. It's a requirement imposed by the Australian government under AUSTRAC's Travel Rule, and as an Australian Pty Ltd, we're required to comply with it — it isn't something we or our processor have discretion over. We've worked with them to streamline the process as much as possible, but we understand it's still a hassle, and we appreciate your patience with it.

If you'd prefer to skip it entirely, card payment via Stripe remains available with no ID verification required. I know this isn't the answer people were hoping for, but it's out of our hands.

[swordfish6975]

That's the last of the orders shipped out
Big thank you to everyone who ordered — it's been great seeing these go out all over the world again, appreciate the support

Good to have the shop fully open with stock here ready for new orders

[swordfish6975]

Good to see from the tracking that some of the new kits are starting to arrive

I've also just pushed an update to the API. Previously, very low-value coins (PEPE, for example) were scaled to price-per-1000 and displayed as mAUD, mUSD etc — but anything below that range simply showed as 0.00 mUSD.

The API now supports the full range of SI prefixes:

×1,000 → m (milli)
×1,000,000 → µ (micro)
×1,000,000,000 → n (nano)
×1,000,000,000,000 → p (pico)

So even the smallest-value tokens will now display a meaningful price instead of rounding to zero.

The fix is server-side, so it applies to all devices — old and new. Nothing to update on your end.

[tweetious]

New ticker (on the right) has arrived! My old one (on the left) still works flawlessly after so many years.  

I’m having an issue updating the firmware to the latest version 1.08 (from 1.07). The update procedure is initiated on the device, everything goes smoothly, the update is finished, and the device is rebooted. However, the firmware still remains at 1.07 (at least that’s what I see on the configuration page). I have attempted to update the firmware three times now, but it still shows 1.07, and when I check for updates, version 1.08 is still available.

The process shows the following messages: "Updating, waiting for reboot" – "Firmware x% waiting for reboot" (at some point, it goes to 100%) – "Copying settings" – "Rebooting now"

Edit: Would it be possible (in a future update?) to indicate the exact cycle duration in seconds on the Cycle tab? I can see that I currently only have three predefined options: Fast, Medium, and Slow.





Edit 2: On the page tab (top left), I can see version 1.0.8, but on the configuration device section, it shows 'Current version: v1.0.7.'"