hamingja
Project Ignite
[mail]projectignite23@gmail.com.
Traditional Loyalty Cards
Pros
⬇︎
easy
permissionless
less privacy problems
Cons
⬇︎
forgeable
fragile
expensive(printing cost)
nonportable
Traditional Loyalty Cards
Pros |
Cons |
|---|---|
|
|
Digital Loyalty Cards
Pros
⬇︎
portable
durable
reliable.
At least
It should be reliable.
Cons
⬇︎
permissioned
Not easy
Expensive
less privacy.
too much information to give
Digital Loyalty Cards
Pros |
Cons |
|---|---|
|
|
Solution
hamingja
SLP Loyalty Cards
Pros
⬇︎
easy
End users don't need to know about SLP or even BCH at all.
cheap
Cheaper altenative solution for merchants. It requires only fraction of BCH to create own SLP loyalty cards.
portable
durable
reliable
no privacy problems
You don't need to provide any personal informations
and
permissionless
Every one can create own loyalty cards.
SLP Tickets
⬇︎
We planed to integrate the SLP Ticket system in our app since the required technology is almost the same as our loyalty cards. Unfortunately, We're running out of time so this section is under construction.
DEMO
⬇︎
Creating stamp card in the hamingja admin app.
Receiving stamps from the hamingja admin app.
Sending a stamp to the hamingja (client) app.
Received a stamp in the hamingja (client) app.
Stamps Details.
Using Stamps, sending back stamps from the hamingja to the hamingja admin (token issuer).
How it works
⬇︎
- Bitcoin Cash
- SLP Tokens
- Spedn
- BIT BOX
- Angular JS
- Ionic
- Firebase
- Express Node.js
- Routing Controllers
Non Tradable SLP Tokens
This is important interms of mass adoption. Some business owners do not want their loyalty points to be tradable. To be able to limit SLP token's tradability, we utilizes verify coventants by using checkSig and checkDataSig. So end-user can only send back tokens to its issuer.
architecture
checkSig + checkDataSig = verify coventants
verify checkSig(sig, pk);
verify checkDataSig(toDataSig(sig), sha256(preimage), pk);CONSTRUCTING SLP OP_return
bin opReturn = 0x6a;
bin lokadId = 0x04534c5000;
bin tokenType = 0x0101;
bin txType = 0x0453454e44;
bin pushId = 0x20;
bin pushMax = 0x08;
bin pushOpReturn = 0x37;
// slp op_return
bin out0 = num2bin(0, 8) . pushOpReturn . opReturn . lokadId . tokenType . txType . pushId . tokenId . pushMax . maxValue;
CONSTRUCTING Slp Outputs
// p2pkh constants
bin opDup = 0x76;
bin opHash160 = 0xa9;
bin opEqual = 0x87;
bin pushHash = 0x14;
bin opEqualverify = 0x88;
bin opChecksig = 0xac;
bin pushP2pkh = 0x19;
// slp output
bin out1 = num2bin(546, 8) . pushP2pkh . opDup . opHash160 . pushHash . ownerPkh . opEqualverify . opChecksig;Verify Slp Outputs
// Verify Slp Outputs
verify hash256(out0 . out1 . changeOutput) == Sha256(hashOutput);Adoption
⬇︎
Merchants accept BCH
Merchants already accepting BCH can engage customers by providing loyalty services.
Events & Meet ups
Event organisers can issue Tickets by using SLP Tokens.
Market
⬇︎
Predicted 23.3% Compound annual growth rate.
The global loyalty management market was valued at USD 2617 million in 2018 , and is expected to reach a value of USD 9280 million by 2024, at a CAGR of 23.3% over the forecast period (2019-2024).
Business
⬇︎